Question

Locked

Setting up windows server 2003 question

By panupatc ·
I've been following this guide here.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/directory/activedirectory/stepbystep/domcntrl.mspx

My situation is that I want my router to handle the DHCP, so I skip the part about DHCP in that article. When I do so, non of the other computer (XP) were able to see/join the domain. nslookup, ping to the server, nothing.

Setting up as workgroup has no problem.

This is the first time I've ever used windows servers. I really don't know if the DHCP is the cause of the problem. Can anyone give me some suggestion please?

The router is assigning a static IP 192.168.1.64 to my server.

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

DHCP

by p.j.hutchison In reply to Setting up windows server ...

No you should NOT use the router as DHCP in a domain. As by default it will assume it will be the DNS server for the network as well. For a domain to work, servers and clients should point to a Windows DNS server, to do that you need to configure your own Windows DHCP server with the correct DNS server IP address sent to the clients.

Then you can configure forwarders on the Windows DNS to point to the router for internet DNS.

Back to Networks Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums