Microsoft KB Archive/124358

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 15:12, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


RAS Server Assigns Cached IP Addresses to RAS Clients

Article ID: 124358

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition



This article was previously published under Q124358

SYMPTOMS

When a Windows NT version 3.5 or 3.51 Remote Access Service (RAS) server uses dynamic host configuration protocol (DHCP) servers to assign remote TCP/IP client addresses, the range of IP addresses that the RAS server receives is cached in the registry. If you reconfigure the DHCP server to allocate and provide IP addresses from a different address pool, the RAS server still assigns IP addresses from the original RAS client address pool.

CAUSE

The RAS Server does not query the DHCP server for new IP addresses until the original address leases (cached in the Registry) expire.

RESOLUTION

To force the RAS server to use the new IP addresses provided by the DHCP server:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

  1. Run Registry Editor (REGEDT32.EXE).
  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

    \SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters\Ip

  3. Remove the DhcpAddresses subkey.
  4. Close Registry Editor.
  5. Shutdown and restart Windows NT.



Additional query words: prodnt ras tcpip

Keywords: kbnetwork KB124358