DHCP client that is set on the workstation. 1

[Maximus7]

I sit with a DHCP server win 2000 working nice and all, some times we have power failures and the server is down but the clients is stil up and can not receive ip's from the server.

Is there some sort of client file that is stored on the workstation that it can use in case the DHCP server is down.

Thanks.

 

[deeno]

I'm not an expert on this, but I'm pretty sure the anser is no. I'll be interested to see what people recommend for this. Personally, I'm pretty sure that a DHCP server will be required to assign the address. If you have a local file on the machine that assigns the last address that the client had, and if the client has been off for any length of time, how would you be certain that the address is still available? I just see a lot of problems with this. Like I said, I'll be interested to see what others recommend for this.

Just a question - If you can configure a local file on each machine with the address settings, why not just use static addresses in the first place???

One other question. Assuming the clients are at the same location as the DHCP server, they would need power to come back on (unless of course they are a laptop or something). If the power is back on, why isn't the server coming back on as well?

Just a couple things to consider...

Backup DHCP server
Sufficient Battery Backup

Best of luck with the problem. I do think you can resolve it without resorting to a method like the one you are asking about if such a method does in fact exist.

deeno

 

[Maximus7]

Thanks

A few months ago I read something like this on the windows 2000 recource kit, but do you think I can find it now. no way.
The file that the client make use of willbe a sort of a cache form. But yes I can not find it now, so I am asking.

 

[rwullems]

there is a kind of cache, when a windows client is normally booting up and he has it previous ip address still cached (the lease is not expired yet), it will ask the DHCP server permission, using a normaly DORA sequense, to use the same ip address again.

When your DHCP server is down, and a client does not get any response, he does not care if his ip address is still cached or not, he is not going to use it and will fall back to an APIPA address (169.254.x.x). Mainwhile he will still try to reach the DHCP server.

To be fauld tollerant here, be sure you have two physical DHCP severs or that a router is passing the DHCP massages (called IPhelper or DHCP relay agent) to another segment if nessecary.
regards,
robert

 

[jfk8680]

If you're using Windows XP you can give each workstation an 'alternate configuration'. Open the TCP/IP properties and go to the tab with this name. Whenever a DHCP server is unavailable, the machine uses these IP settings.

Jeffrey Kusters

MCSA, MCSE, CCNA

 

[GlenJohnson]

Try setting your ttl in the server to a longer time frame. If the server is down, and the clients don't need to get a renew because of a re-boot or something like that, the same ip will be used until the ttl is up. If your server is down for 3 hours a day, set the ttl to 200, (3 hours plus 20 minutes), so the client won't need a renew till the server is backup. Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

"Many receive advice, only the wise profit from it."
Harper Lee (1926-; US novelist.