DHCP Issue...

codeman0013

codeman0013

Active Member
All,

Anyone that can help me i would greatly appreciate... I have an older windows 2000 server at a remote location i want to turn off but when i try to turn the dhcp off and its on at the new 2003 server at my other location the dhcp doesnt fail over and i have no idea why... I have Done lots of things here maybe someone can help me on this one on what it will take to get the dhcp over to my current location and away from the older one that i need to turn off...
 
So you want to turn dhcp off on one pc? If so then type in services.msc in the run box and scroll down and find dhcp and right click and push properties and click startup type and select disable. Then it should stop the service but if not then cancel it in task manager!
 
nah i have an old server 2000 that is being shut down but when i shut the dhcp down for the server its not going to the backup server at this location like it should be.. all pc's at that location loose connection instead of failing to the new server we are using here...
 
this is hard to help without looking at the setting you have. Is the other server working? alos double check the settins on the computers, make sure they are set to the new server.
 
Yes the other server the new one works its our main domain controller we have now... I have done ipconfig /release and /renew on several machines but none are failing over they just say they cannot contact the dhp cserver...
 
May be obvious, but under the network connection TCP/IP properties for each machine, have you set the IP address and DNS servers manually?
 
yep they are all set to automatically obtain they should pick up their ip from our local servers but they just are not coming across for some reason just timing out when trying to renew with the new server
 
if i demote this server how do its clients know to come back to my location and grab the same ip addresses? Just due to a reservation by the ip i would assume?

also this server isnt an AD server anymore it was demoted a few months back from that duty due to speed..
 
Sounds like a DNS issue. The clients probably have cached DNS to your old server and keep trying to go back to it.

I would suggest you configure your new server with the same IP ranges and subnets and then reboot your clients. During the boot strap windows will search out any DHCP/DNS servers and pull down information from them.

As for where the DNS cache is held in windows I can't remember, let me try my google fu....

....

try ipconif /flushdns on your clients and then see if they can pick up the new server. You could create a batch file and send it out to all your clients and do this, or possibly through some network policy.

Unfortunately, I am more of a Unix guy than windows when it comes to server side technology, but there has to be a way through the GUI to do so since it is windows.
 
You must log in or register to reply here.
Back
Top