I have three locations – PDX SFO LAX. WAN connected by FR – 256 CIR.
In PDX there is an existing NT4 domain that will eventually be removed. It is running DHCP currently and servicing all three locations.
Also in PDX there is a new domain running on Win2k. There is no trust between the two domains – no need since NT4 will be removed. This W2k server is running DHCP as well – different scope address range than the NT4 DHCP.
I turn off the DHCP service on the NT4 machine so the only DHCP server out there is sitting on Win2k. Users in PDX have no trouble at all gaining a lease from the W2K DHCP service on the new domain. Unfortunately, the remote sites of SFO and LAX do not have the same luck. They are met with the dreaded “nodomain server…” when attempting to log on to the new domain. Yes, I did release their IP information before rebooting the remote PC.
If I use static IP information on the remote site PCs, no problem logging on. If I turn on the NT4 DHCP server and have them log onto that old domain using DHCP, there is no trouble.
Since the local PCs are capable of gaining a lease, the scope and DHCP server are working just fine (assumption). Yes, I have a scope set up for the other two locations. And since the remote PCs are capable of gaining a lease on the NT4 domain, I can only imagine that there isn’t an issue with routing.
Is there some DHCP ACK command that needs to be run on the remote machines?
Anything, please.