Limited Or No Connectivity Message...
Posted on 2006-03-26
I'm having the strangest DHCP problem and it's driving me mad!!
I have two domains located on the same network segment.
Domain1 is an NT 4.0 domain - let's call the domain ABC.
Domain2 is a Windows Server 2003 domain - let's call it abc123.local.
There is a two-way trust between the domains.
Each domain now has a DHCP server. The DHCP server in domain ABC serves a scope of 10.1.4.x while the DHCP server in domain abc123.local serves the scope 10.1.8.x.
The NT domain, ABC, is really the domain with active users. I'm in the middle of a domain migration project and I'm still just testing things on the Windows Server 2003 domain.
Users logging into the NT domain may get either a 10.1.4.x or a 10.1.8.x IP address depending on which DHCP server responds first.
The problem is this:
I'm testing 2 computers on the Windows Server 2003 domain. When I boot these computers, they both will USUALLY come up with an APIPA address (with Limited Or No Connectivity shown in the icon tray). Usually, but not always. Sometimes they get a 10.1.8.x IP address as I would expect.
Maybe 80% of the time, they boot with an APIPA address. If I run a packet trace on these machines while in this state, I see DHCP Discover packets going out at about 5 minute intervals (this is how DHCP should behave) but I see no other DHCP packets (no Offer, Request, ACK packets). All of this leads me to believe that the computer cannot find a DHCP server. That would make sense except for the fact that after a few reboots it generally DOES find a DHCP server and it gets an IP address.
The network setup is very simple. Cabling runs from each office into a patch panel in the server room and then into a series of Bay Networks switches. The cabling from the servers runs directly into the same switches.
I cannot seem to find anything that sheds light on this subject. Anyone with insight into this problem will have my eternal gratitude!!