Problems When a Connection over an ISDN Bridge Is Not Closed
Article ID: 183812
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
This article was previously published under Q183812
SYMPTOMS
When a client application connected to a remote host over an ISDN bridge
closes the connection, one or more of the following may occur:
- If keep-alives are enabled, the ISDN connection is not permitted to
timeout.
- NETSTAT shows CloseSocket() as established. You must restart the
computer to recover from this condition.
- Without keep-alives, eventually all of the user ports become permanently
exhausted. This renders the computer inoperative on the network.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords: kbbug kbfix KB183812