March 20, 2010

DHCP -- a technical question

If a client computer has been assigned an IP by DHCP and has several days left to run on its lease, and that computer reboots, when it comes back up does it do a new DHCP request, or keep using the previous lease? (This would be WinXP and Win7, two computers.)

UPDATE: OK, this shouldn't affect any of you in any way. I just redeployed my LAN so that everything is in the 169.254.*.* block instead of 192.168.1.*. That included changing the IP of one of the ethernet interfaces on the Qube, the one connecting to my LAN.

Also, now both Arcturus and Alcyone are using DHCP instead of having their IP's manually set.

UPDATE: There was a small problem that required rebooting the server.

Posted by: Steven Den Beste in Computers at 07:05 PM | Comments (5) | Add Comment
Post contains 130 words, total size 1 kb.

1 Windows always renews when it brings up the interface, at least in my practice it does. Linux does it too. The overhead is not considered prohibitive. And the primary function of the lease is to weed out dead clients, not to save on DHCP traffic.

Posted by: Pete Zaitcev at March 20, 2010 07:28 PM (/ppBw)

2

It makes sense that it would, since when the computer comes up it doesn't know whether it's connected to the same network it was on before. Thus the previous IP might not work.

OK, great! Thanks a lot!

Posted by: Steven Den Beste at March 20, 2010 07:32 PM (+rSRq)

3 I've run into situations where a reboot or even a hard power off doesn't reset the IP and you have to force it on the command line.  However, that's always been in enterprise shops, so I'd bet on it being something that happens when a machine is joined to a domain, or that it's something you can configure on the DHCP server that tells a client to keep the lease until it expires.

Posted by: David at March 20, 2010 09:11 PM (rlE2m)

4 169.254/16 block is used for link-local communication when DHCP is not available. A renumbering of a real network into that block is probably a bad idea. I saw devices that confugured aliases in that range automatically, in order to support exotics such as Multicast DNS and Apple Randevous. That said, at worst you'll hit a conflict and renumber again, so suit yourself.

Posted by: Pete Zaitcev at March 20, 2010 09:25 PM (/ppBw)

5

That's precisely the reason I wanted to use it. When I want to restore a computer from backup, the boot disk to connect to Deneb allocates itself an IP in that block, which means Deneb has to be in that block or else the computer being restored can't find it.

I ran into that a couple of weeks ago when I wanted to restore Alcyone from backup. It didn't work.

Tomorrow I'm going to try the process again, at least to the point where I know that Alcyone and Deneb are talking, so that in future if I really do need to restore, I'll know it works.

It looks as if it chooses an IP at random. Since I only have four computers, and it's a 16-bit address space, and I can if necessary turn off two of them during the restore process, the chance of an IP collision is really low.

Posted by: Steven Den Beste at March 20, 2010 09:40 PM (+rSRq)

Hide Comments | Add Comment

Enclose all spoilers in spoiler tags:
      [spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)

At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.

How to put links in your comment

Comments are disabled. Post is locked.
8kb generated in CPU 0.0119, elapsed 0.0224 seconds.
20 queries taking 0.0143 seconds, 22 records returned.
Powered by Minx 1.1.6c-pink.