new 2003 server, clients not seeing domain

[350ztn]

I have a new 2003 server, and changing a small business from a workgroup to a domain. The server is plugged into a DSL 4 port router and 3 PC's are plugged into it as well. I gave the server the gateway address of the router and can access internet. I've tried on the clients to assign the IPs static and leave them dynamic but neither way works when I try to change them to a domain, it just tells me it can't find the domain that it doesn't exist. all clients are XP Pro. IP Scheme is 192.168.2.x Thanks for the help and suggestions

 

[ShackDaddy]

The clients all need to be pointed at the server for their DNS. The server can be pointed at itself, but in the server's DNS management, it should be configured to forward queries to your ISP's DNS servers. Until the clients are pointed at your local server for DNS, they won't be able to find the domain.

ShackDaddy

 

[350ztn]

when I do an ipconfig on a client PC it shows my server ip address as the DNS and DHCP server, the router as the gateway and it is getting the proper connection specific-DNS suffix which is the full server name "server.local"
Still trying to join the domain and it now prompts for a username and password but it still tells me domain not found on network. any other suggestions?

 

[Saugilsr]

If you do an NSLOOKUP for your new domain.

ie nslookup domain.com

What result does it give you? If it doesn't return the IP of you local server that may be the cause of the problem.

Do the logs on the server report anything wierd?

 

[350ztn]

the nslookup of server.local returned 127.0.0.1 and then server not found.

would puting a switch between the server and the 4 port dsl router help at all?

 

[ShackDaddy]

Your problem MAY stem from using the domain name ".local" instead of using a standard name that would be more like "domain.local". This is known to cause problems. Take the exact message (or part of it) that the client gives you when you run the /connectcomputer wizard and pop it into a TechNet.com search. Then look for articles related to problems in a .local environment. I believe there is a patch or service pack for that. My general rule is to a voice a single-suffix domain.

ShackDaddy

 

[350ztn]

so use a .com domain would be better? my client doesn't have a web address will this present a problem?

 

[Saugilsr]

I would have to agrea. Giving it a logical domain name. It will just make life easier when it comes to planning. Especialy if the domain is going to grow.

It doesn't matter that they dont have a registered name (website). Because all of you communication is internal. You wont be able to access the domain (using its name) from the outside world by defualt. Id make sure it's a name that not already taken and reserve it anyway.

Redoing the server will probably clear up what problem you were having.

When you have your server back up. Make sure everyclient can ping it and vice versa. Then make sure DNS looks like its running ok.

 

[4nd7]

If you run nslookup and the server is unknown in the result, you need a pointer entry in DNS -> Reverse Lookup Zone. Select the server from the list that will apear.
This may be the solution to your problem.

Cheers,
Andy.

 

[ShackDaddy]

You can use a .local domain name, but the domain name shouldn't just be ".local" any more than you'd just use ".com" as a domain name. If you call your company Herzomatic Supplies, your internal domain name might be "herzomatic.local" while you might use "herzomatic.com" on the outside. Several of the networks I set up, I used "name.com" both inside and outside without any consequences. If you have a decent workign understanding of DNS, using a .com address on your internal network is not a problem.

ShackDaddy

 

[350ztn]

well that I think is the issue is my limited understanding of DNS. I have ther server named server.com after removing AD, DNS and DHCP. Then I redid it all and following instructions from microsofts website. I can now do a dns lookup on server.com and get a proper reply of my server name and IP address. I added a switch in the equation between the router and the gateway. the router ip is 192.168.0.1, server is 192.168.0.2 so I have the server networking as subnetted to 255.255.255.0, gateway, 192.169.0.1 DNS of 127.0.0.1
I can't get to any websites. the server DHCP rance is from .10-.255 and my clients can't obtain an IP address from the server or attach to the domain. I figure once I get it to get an ip address I'll be able to attach to the domain. I think all of this is revolving around DNS and my lack of grasping that concept. I have a 2003 book and have read the DNS section a couple times but can;t get it. any other suggestions to try before I shoot this thing!

 

[Teknoratti]

More than likely this is a DNS error somewhere on your network. If you have not configured DNS already I would suggest starting over from Scratch. DC promo your server down and then back up again, then let the Wiz configure DNS for you, that way you'll have it right. Then you need to associate the DNS suffix of the domain in the clients NIC connections. from this point the clients will query the DNS server of "yourdomain.com"

Once this is found you'll get prompted for a user with authorative rights to join the clients to the domain. You should be fine from that point.

 

[350ztn]

When I do a simple DNS test it passes, when I do a recursive test it fails. what does the recursive test do that the simple test doesn't do? Also I have removed active directory and went back through dcpromo and let the server setup DNS and I think I have answered the questions correctly. Should I leave my nic connections on the server to auto instead of static while I'm doing the dcpromo? I haven't tried that yet. Man I'm starting to wig out...I need a Coke!

 

[350ztn]

Alright so here is where I'm at...this might be a little long but the more info I give the easier it is for some help.
I have a Microsoft router that has DHCP enabled. The LAN port goes to a switch where the server and PC are plugged into. AD is installed on the server. DNS is also installed (unsure if it is right).From the server I can ping my workstation name and IP address. From teh server I can get to the internet and from the server when I do a NSlookup from a command line I get a response of my server name and IP address. DNS is setup with a Forwarder to the Local IP address of the router. Now from the PC, I have a static IP address assigned on the same network as the router and server. 192.168.1.1 for router, 192.168.1.2 for server and 192.168.1.3 for the PC. The PC can get to the internet, but it can't ping the server name, but can ping the IP address. It doesn't connect to the domain, giving an error of "Windows cannot find the network path, verify network path is correct and destination computer is not busy or turned off" It isn't busy or turned off. Please help I need this server functional next week!

 

[comtec17]

Add the server name into the PC's lmhosts file located in C:\windows\system32\drivers\etc.

 

[350ztn]

Same error: I put entries in both the host and lmhost file neither worked.
lmhost file entry was 192.168.2.2 servername.com #PRE
and then saved as the lmhost file.

host file entry was 192.168.2.2 servername.com
and saved as the host file.