RRAS Does Not Release IP Addresses for Incoming Connections (294953)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q294953 SYMPTOMS
Under the following conditions, RRAS may not release IP addresses for incoming connections:
- On your DHCP server, you enabled the 002 microsoft release dhcp lease on shutdown option, and you set 1 for the data length.
- On your client computer, you enabled the Accept incoming Connection option and chose all of the default settings.
- You ran the ipconfig /release command, and then ran the ipconfig /renew command.
- On your DHCP server (under Lease addresses) there were three addresses for the client. You shutdown the client, but did not restart it.
CAUSE
The problem can occur because the DHCP client service releases the IP address for the network adapter on shutdown before the Remote Access service has a chance to release the IP addresses for the incoming connections. In normal circumstances (when the server option is not set), the DHCP client service doesn't release the address, and because of this, the Remote Access service can release the IP addresses for the incoming connections.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
WORKAROUND
To work around this problem, use either of the following methods:
- Assign a static address to the RRAS server.
- Shut down the computer through a script by first stopping the Remote Access service and then the DHCP Client service.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type: | Major | Last Reviewed: | 12/4/2003 |
---|
Keywords: | kbbug kbenv kbfix kbnetwork kbWin2000PreSP3Fix kbWin2000sp3fix KB294953 |
---|
|