Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hey Guys,
Here is my problem: I ordered a Dell 400SC Small business server with 2k3 and it came pre-configured out of the box so I went through the "To do list" and setup the domain name I wanted and setup one user with the "power user template" and added them to the server via users and groups. Everthing seemed to be ok at that point. With the exception of when I setup the IP for internet etc.. it mentioned that im using a routable IP and to use a private one but it still let me continue.
Now when I try and have the user change from a workgroup to join the domain. I get an error immediately that says it can't find the server. Im not super familiar with AD or 2003 server for that matter so is there step that I missed that is preventing the client computer from finding and attaching to the domain? I thought it would be just like a NT4 server or win2k server with AD disabled where you just promote the system to BDC choose the domain name and clients would be able to see and attach to it automatically. Hints on what im doign wrong?? :)
Thanks guys,
Mac
sounds like DNS issue. can you ping the server?
For more tips or information, go to http://www.ChicagoTech.net
Robert, MS-MVP/MCSE and CNE
Windows & Network Support, Tips and FAQs on
http://www.ChicagoTech.net
0 
Just change the dns of the pc trying to join the domain to the IP of the server. Make sure AD and DNS or installed on the server too.
0
Thanks guys,
Now how do I confirm that AD and DNS are installed? I assume that they are but dont know for sure? How can I determine that.
And also on the client side when you say change the DNS to the IP how exactly do I do that. Im not super familiar with DNS and AD.
Thx,
Mac
0
I think it's a DNS issue, too. My guess is that you're experiencing this problem exclusively with XP clients.
Here's an example for setting up a small domain with local DNS service:
1. Install AD on the server to make it a domain controller. Pick a snazzy name for your domain.
2. Server's network card properties:
IP Address: 192.168.1.10
Subnet: 255.255.255.0
Gateway: 192.168.1.1 (your router's LAN IP)DNS Server: 127.0.0.1 (yes, it's pointing to itself, but you'll see why later)
3. Open the DNS plugin. if there's a scope called . (just a period), delete it. This will let your server know that it isn't the end-all and be-all of domain name resolution.
4. Still in the DNS plugin, right-click Properties and click the Forwarders tab. Enter your ISP's DNS server's IP address as a forwarder. This will let the server know where to direct client computers that want domain name resolution for an external domain.
5. Client computer's network settings:
IP Address: 192.168.1.37
Subnet: 255.255.255.0
Gateway: 192.168.1.1 (router's LAN IP)DNS Server: 192.168.1.10 (server's IP)
This way your client computer will know exactly where to go when it has network "questions."
Okay, that's about it. You've setup the domain controller to provide DNS service for your domain, and it will let your ISP's DNS server handle the external stuff.
You might want to setup a DHCP server on the domain controller to automatically assign compatible IP addresses and network settings to client machines. If a client machine NEEDS to have a certain IP address, just create a reservation for it in the DHCP scope.
0
There is some issues with clients not being able to log on.
By default a proper user can add I think up to ten computers. It would be much better for you to add them in first to ensure GPO.
From the 70-290 book, troubleshooting computer accounts.
If comp exists in AD it must be reset.
If the comp is missing you must create.
If comp belongs to domain then remove by changing to workgroup.
Rejoin to domain.
0
If you have only one server and it is a domain controller than you would not have the Local User and Groups options since there are no local accounts on domain controllers. I'm guessing you don't have a domain. On the server, at the Run command type DCPROMO and see if it attempts to create a domain or if it comes back and tells you that if you continue it will DEmote the server. If it attempts to create than the server is not a DC, if it attempts to demote, than it is a DC (domain controller). Cancel the process either way. If it is not a dc, then you'll need to create the domain by continuing with the dcpromo utility. If it is already a DC then you'll need to make sure DNS is installed and make sure the client machines have the IP of the server in their Preferred DNS settings in the Properties of TCP/IP.
By the way, the ability to ping the server is no indication that it can find it during the process of adding the computer to the domain. Jefros advice from the previous post is a bit confusing If the computer account exists in AD, then you are all set. It more than likely will not exist. If it does not, it will create automatically assuming you have the proper permissions to do so. If the computer belongs to domain already (unlikely) then you can add it to a workgroup, any name will do, then reboot, add it to the domain, and reboot again. The key here is this - make sure the server is a DC. Make sure the server has DNS configured and make sure the clients have the abiltity to find the DNS server. This is done by having the Properties of TCP/IP point to the server as their Preferred DNS server on each client.
Good luck.
0
Yes thats a DNS problem, you will want to make sure you have the right DNS server inputted in, and make sure that all the host files, and alias's for AD setup to run inputted correctly.
I didn't understand exactly what you are trying to do and had done.
Did you just create a new domain and not able to access ad-users and computers
or
Add it to an exsisting domain and not able to access users and groups?
or
Can you not even dcpromo it?
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
