Win95 won't forget old IP address

Mark Sirota <msirota@isc.upenn.edu> Tue, 11 June 1996 20:29 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27637; 11 Jun 96 16:29 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27633; 11 Jun 96 16:28 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa19435; 11 Jun 96 16:29 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA24602; Tue, 11 Jun 1996 16:22:05 -0400
Date: Tue, 11 Jun 1996 16:22:05 -0400
Message-Id: <31BDCE63.FF6@isc.upenn.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Sirota <msirota@isc.upenn.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Win95 won't forget old IP address
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: Mozilla 3.0b2 (X11; I; OSF1 V3.2 alpha)

I've got a Windows 95/Plus client which is booting via DHCP.  If I move
the machine to another subnet, it requests (via DHCPREQUEST) the IP address
it had before.

The daemon refuses (DHCPNAK), since the request is coming from a different
subnet.  The client REQUESTs again immediately, and again the server NAKs.

And that's it.  The Win95 client doesn't then request a new address on its
new subnet or anything.  So I tried to make the Win95 machine forget about
its old address.

I can't seem to do that.  I delete the TCP/IP protocol and add it again, I
search the whole disk for files containing the old subnet string, nothing.
I can't figure out how to make it forget the old IP address so it won't
just request it again.

Questions:
(1) How can I make the 95 machine automagically request a new address on the
	new subnet?
(2) How can I make the 95 machine forget its old IP address?

Question (1) is vital for laptops that might be carried from subnet to subnet.
Question (2), if easy, would work for desktop machines that switch subnets.

Thanks for any help you can provide.
-- 
Mark Sirota, Network Systems Engineer
University of Pennsylvania, Information Systems and Computing
msirota@isc.upenn.edu, 215/573-7214