RAS Server Assigns Cached IP Addresses to RAS Clients

Last reviewed: March 25, 1997
Article ID: Q124358

The information in this article applies to:
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Workstation version 4.0

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 ntras ntregistry NTSrvWkst nttcp
Version : 3.5 3.51 4.0
Platform : WinNT


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.