On Fri, 7 Jan 2000 [EMAIL PROTECTED] wrote:
> The disadvantage ( of win9x client saving the dhcp supplied IP ) is when
> there is trouble on the dhcp server
> ( I have seen this on NT server) or network, that you have to somehow clear
> the IP address from the win9x client
> so it can get a new IP, but because it tries to renew the same address (
> which has now been assigned
> to a different machine by the server ), you have a conflict.
You didn't read my post carefully, did you? :-)
I said, Windows machines *ask* for the same IP address. If it is not
available, the server sends a negative acknowledge packet, and then the
workstation asks for *AN* ip address. It does NOT insists on getting the
same one over and over again.
Case at hand:
I have a laptop. I plug it in into our network. I gets an IP. I turn it
off, take it home, and plug it into my network at home. It asks for the
last IP address. The server rejects the request. The laptop gets an IP
from the server.
The above scenario works perfectly whether I run Linux or Windows.
Boothing Windows generates a couple of more packets on the network (asking
for the old one, and the NACK from the server). But I think it is worth
it; one might argue otherwise. If you have a valid argument against what
I described, I am eager to hear it.
cheers,
Hossein
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
