BUG: Winsock App Over IPX/SPX Over RAS Fails to Connect (140019)
The information in this article applies to:
- Microsoft Win32 Software Development Kit (SDK) 3.5
- Microsoft Win32 Software Development Kit (SDK) 3.51
This article was previously published under Q140019 SYMPTOMS
A Windows NT client makes a PPP (point-to-point protocol) RAS (remote
access server) connection to a Windows NT RAS server with support for
IPX/SPX protocols enabled. A user on a Windows NT RAS client runs a Winsock
application that binds to the RAS adapter and listens for connections over
SPX or SPXII protocol sequences. Another user on the Windows NT RAS server
runs a Winsock application that binds to the RAS adapter on the server and
tries to call connect() to connect to the application on the RAS client. A
call to connect() in this scenario fails with SOCKET_ERROR and
WSAGetLastError() returns WSAENETUNREACH(10051).
RESOLUTION
The RAS server administrator must configure the RAS server so that it
assigns different network numbers to all RAS clients. This can be done by
clearing the "Assign same network number to all IPX clients" check box. On
the Control menu, click Network. Then click RemoteAccessService, click
Network, and click IPX.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes
available
Modification Type: | Major | Last Reviewed: | 11/3/2003 |
---|
Keywords: | kbAPI kbBug kbnetwork kbWinsock KB140019 |
---|
|