Does anyone have a workaround for Windows 95 not asking for new ip when booting?
cpeters2 <carolyn_petersen@wausau.com> Wed, 11 September 1996 16:49 UTC
Received: from ietf.org by ietf.org id aa27787; 11 Sep 96 12:49 EDT
Received: from cnri by ietf.org id aa27783; 11 Sep 96 12:49 EDT
Received: from marge.bucknell.edu by CNRI.Reston.VA.US id aa10257;
11 Sep 96 12:49 EDT
Received: from reef.bucknell.edu by mail.bucknell.edu;
(5.65v3.2/1.1.8.2/17Jul96-0109PM)
id AA05834; Wed, 11 Sep 1996 12:45:26 -0400
Date: Wed, 11 Sep 1996 12:45:26 -0400
Message-Id: <32370303.448@wausau.com>
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.org
From: cpeters2 <carolyn_petersen@wausau.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Does anyone have a workaround for Windows 95 not asking for new ip
when booting?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: Mozilla 2.02 (Win16; I)
Hello everybody - I have an interesting situation. I am setting up DHCP to support many PCs that will move from office to office with sales people, and management. My goal is to have NO configuration required to plug the PC into any of our network ports. This is where DHCP is wonderful!! Unfortunately, Windows 95 does not look for a new IP address when booting if its license has not expired. This is a problem if while down the user moved to a different subnet. Does anyone have a workaround for this? Our user base is not technically literate. They will not accept a solution like 1. run winipcfg 2. release address 3. renew. This will all have to be hidden from them. Any help you could give would be much appreciated, Carolyn