Connection Fails Over IPX with Duplicate SPX Connection ID This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article was previously published under Q159959 SYMPTOMS
When you are using Windows Sockets to provide stream-type connections over
IPX, or when you are running another program that uses the SPX protocol
over IPX, a connection to a remote node may intermittently fail to be
established.
Using Windows Sockets, error 10054 (WSAECONNRESET) may be returned. CAUSE
Under certain circumstances, it may be possible for the same SPX
Connection ID to be assigned to more than one active SPX connection.
This is a problem with the IPX/SPX-compatible protocol (NWLINK) included with Windows 95. STATUS
This problem no longer occurs in Windows 98. To resolve this problem, install the current version of Windows. For information about the current version of Windows, visit http://www.microsoft.com/windows (http://www.microsoft.com/windows).
MORE INFORMATION
The SPX Connection ID uniquely identifies each active SPX connection on a
given node running the IPX/SPX protocol. SPX keeps track of the status of
each connection by its Connection ID. If duplicate Connection IDs are
assigned, SPX cannot correctly track the status of the connection and
cannot respond correctly to received packets.
This symptom, although rare, is more likely to occur when a program is creating many SPX connections very rapidly.
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
