We have recently created a new DHCP server on a Windows 2003 AD server. We deactivated its predecessor, Windows 2000 server. It appears to be setup correctly and authenticated. But it is not giving out IP addresses. What could be the cause?
I take it that you authorized the server.
DNS dynamic updates on, DNS servers are listed, scope is correct. DNS domain name is correct.
Does the server show in DNS and name servers?
If you release and renew clients, any errors.
Yes, DHCP is authorized, DNS is dynamic and listed, and scope is correct. And yes the server shows in the DNS correctly. When we release/renew the clients are getting DHCP unavailable error.
We have checked the ensure that the DHCP service is running and the scope is activated. There are no errors in the event logs. We have even gone as far as connecting a PC directly to the server via a cross connect and are still not getting an IP address.
And in reference to Titlest reply, the server is in a different subnet and vlan than the workstations, but the mask is 24 bit and should be able to assign addresses to the workstations. Also with the cross connect test we have eliminated the switches. But that was a good idea.
have you tried patching a client onto the same VLAN as the DHCP server? By default, client DHCP broadcasts won't traverse VLANs. This needs to be allowed/specified at the switch level.
If your switch gear is Cisco, this is done using "ip helper" addresses, plenty of info on this on google
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.