Technical article 118226

My Windows 95 Computer is not picking up a new DHCP address when I move between networks.

OpenServer 5.0.5

Written · Last revised

Problem

The DHCP does not correctly update the DHCP client on a Microsoft Windows 95 machine when the client is new to the Network.

If a Windows 95 client is moved to a new network that is using Openserver DHCP, and is still holding a valid IP address that was obtained from a DHCP provider on the previous network, then the IP address will not be correctly updated for the new network.

This problem does not occur if the Windows 95 client does not hold a valid DHCP obtained IP address.

This problem can also occur if the IP address of the DHCP server is changed and the DHCP AAS pools are updated to match.

This does not appear to affect Hewlett Packard Jet Direct printers, nor Microsoft NT 4.0 server and workstations.

Cause

When "booting" a Windows 95 pc client, during the boot procedure
the DHCP client will make a "boot" request, asking for the current
IP address to be renewed.  Because it does not receive a valid
answer, the client continues to use the same address.

Lease times settings for the DHCP client have no effect on this problem.

Solution

A work around for this problem is to use the "Winipcfg" utility. To use this utility, proceed as follows.

Click on "Start" then "Run".  Another window will appear.

Type "command" in the white box, and then press "Enter"

Another window should appear, with a "C:\>" prompt.

Type in "winipcfg", the "winipcfg" utility will now
be the focussed window.  The current (invalid ) IP address
and netmask details should be listed.

At the bottom of the winipcfg window, click on "Release All"

Now click on "Renew All", the IP address displayed should now be the correct one for the current network.

Click on "OK" to close the window.

The tcp/ip can be tested to ensure that everything is working. In the "command" window, (opened earlier ) type:

ping <name of known server >
There should be a sequence of three packet returns.  This shows
that the tcp/ip function is working fine.  Close this "command"
window by typing "exit".  The window should close.

The pc is now ready to use.

This has been reported to SCO Engineering.

See also

tcp(ADMN), Openserver 5.0.5 networking Guide Microsoft Windows 95 Documentation.

From the Xinuos technical article database, record 118226. Reproduced with permission. The original is at www.sco.com/ta/118226, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.