Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DHCP Error stumped everyone! 1

Status
Not open for further replies.

qae

Technical User
May 24, 2002
19
GB
Morning Guys!

The problem i have has stumped everyone! And i am hoping this is the place to solve it! I run 2 NT servers and a novell netware server, On tuesday the NT server no2 Crashed, this is the PDC as well as the DHCP manager machine, Once the server was rebooted All the machines came up with the Error of No Domain Controller found I looked in the Events viewer and was coming up with an Error for the RIP for NWlink, Although the funny thing was that, If the machines had an assigned IP they could see the Sever which crashed although they could not see the server which had not crashed, If the were assigned a Dhcp Lookup for IP, the could not see the servers although they could see our mail server!

I have been to an DHcp machine and Released the ip and tried to renew the ip and it comes up saying it can't find the DHCP server, So Firstly i deleted the scope and recreated it, no luck then as a case of desperation i removed the service and added the service, the recreated the Scope once again, No luck athough i was now getting ip conflicts, which can be sorted out as soon as to get the Dhcp working, this did not help, I was still getting the no Dmaon conrtoller error and no DHcp server found, So i thought It was a Protocal i ended up removing all my protocals and re-installing them as i know that DHCP works around TCP, Lastly still no luck, My reasoning is that it is either TCP-ip or Dhcp, Does anyone know aht i am doing wrong?? and suggestions please guys??

Thanks your assistance is appreciated!
 
First of all check to make sure the server that crashed is still the PDC, check in server manager.

Go into winipcfg or ipconfig and release the IP address but dont renew. Reboot the PC and see if it gets an IP address

Does the other NT server have a DHCP scope? if so just stop the DHCP service thats running. Cold boot the PC and see if it gets an address. release and renew to see if that works.
 
Thanks AndyKG

I have attempted to do what you suggested, Although on th cold boot it gives me a IP, but that comes on the adapter, when releasing it and then Renewing it, it comes up with the error of DHCP server unavailable.

The machine i attemp this on is a Win 98.

The server is still the PDC!!

Thanks for the help Andy!
 
Are your clients getting any authentication and able to see network resources? When you are at a client and get the IP info, is it pointing to the correct server? Can you ping the IP of the DHCP server from the client? Our set up is that a BDC is the DHCP, not the PDC. You could install DHCP on your BDC, delete it off your PDC, then go to a client, release the IP as previously suggested, and see what happens. Just a few thoughts, may be helpful, maybe not.
 
When you define your scope do you also set clients to receive autoconfiguration of wins.Try pinging your PDC with both host name and ip address.
 
When you define your scope do you also set clients to receive autoconfiguration of wins.Try pinging your PDC with both host name and ip address.
 
1. I'll assume the second NT server is a BDC if it is have you rebooted it since all this happened.
2. IP conflicts are BAD very bad actually the server will on stop responding to IP if that is the problem.

Here's my suggestion. Shut the bdc off (leave it off) reboot the PDC wait 5 minutes (this is the time it takes for a windows network (servers and clients) to perform a browse master lookup) at which point the PDC will realize for absolute sure it is the PDC then release the ip from the client and reboot it. If it does get the IP back which it should if the NT server DHCP service is configured correctly (if you haven't already before the reboot of the PDC reapply the service packs up to 6a (when you removed and reinstalled the service/protocol you negated the previous service pack install)).

If it does get the IP your BDC needs better configuration, when the primary failed its flawed configuration screwed your network up.

If it does not get the IP address take a hard look at the event viewer on the PDC, and post the additional protocols your running and a rought topology of your network

Hope that helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top