TCP/IP socket connection in a Java Virtual Machine closes after the local clock time on your Windows 2000-based computer changes (884199)


The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional

SYMPTOMS

On a Microsoft Windows 2000-based client computer, you run a Java Virtual Machine session that opens a TCP/IP socket connection to a server. If the local clock time of the computer is changed, the TCP/IP socket connection to the server closes.

You may receive an error message that states that the connection is no longer available. The exact error message that you receive depends on the particular operation that you are performing. For example, you may receive an error message that is similar to the following:
System error 64 has occurred.
The specified network name is no longer available.

CAUSE

This behavior occurs if the following conditions are true:
  • When the connection is open, your computer synchronizes with a time server or you manually change the local clock time of your computer
  • The local clock time of your computer is changed to a time that is ahead of the connection timeout time.
For example, this behavior occurs if the TCP/IP socket connection is set to time out after 60 seconds, and the local clock time on your computer is changed to a time that is 2 minutes later than the current local clock time of your computer. Because the timeout of the TCP/IP socket connection depends on the current local clock time of the client computer, the connection closes.

STATUS

This behavior is by design.
Modification Type:MajorLast Reviewed:11/12/2004
Keywords:kbwinservnetwork kbnetwork kbinfo kbtshoot KB884199 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.