Incoming connection clients

Windows XP supports incoming connections from clients running Windows XP, Windows 2000, and the following operating systems:

Windows NT version 4.0 clients

Windows NT version 4.0 clients can take full advantage of all incoming connection features except dynamic allocation of multilinked lines, Extensible Authentication Protocol (EAP), IPSec client to server data security, and L2TP for tunneling across intervening networks.

Windows NT version 3.1, 3.5, and 3.51 clients

Windows NT version 3.5x clients can take full advantage of incoming connection features, except for Multilink functionality. Windows NT 3.5x clients negotiate the logon process and authentication with the incoming connection. You can also configure these clients to use scripts that completely automate the logon process.

Windows NT version 3.1 clients do not support the Point-to-Point Protocol (PPP) introduced in Windows NT 3.5. Only Windows NT 3.5x or other PPP clients provide the support necessary to run TCP/IP or IPX programs on clients that directly communicate with servers on the LAN by using TCP/IP or IPX.

Windows Millennium Edition clients

Windows Millennium Edition clients can take full advantage of incoming connection features, except dynamic allocation of multilinked lines and the Extensible Authentication Protocol. Windows Millennium Edition clients negotiate the logon process and authentication with the server. You can also configure these clients to use scripts that completely automate the logon process.

Windows 98 clients

Windows 98 clients can take full advantage of incoming connection features, except dynamic allocation of multilinked lines and the Extensible Authentication Protocol. Windows 98 clients negotiate the logon process and authentication with the server. You can also configure these clients to use scripts that completely automate the logon process.

Windows 95 clients

Windows 95 clients can take full advantage of incoming connection features, except the use of Multilink, dynamic allocation of multilinked lines, and Extensible Authentication Protocol. Windows 95 clients negotiate the logon process and authentication with the server. You can also configure these clients to use scripts that completely automate the logon process.

Windows For Workgroups, MS-DOS, and LAN Manager clients

Windows 2000 Server or later provides a Microsoft Network Client version 3.0 for MS-DOS and a Windows for Workgroups client that provide remote access. Separately purchased Windows for Workgroups and LAN Manager Network Connections clients can also connect to an incoming connection.

You must set up the Microsoft Network Client 3.0 for MS-DOS to use the full redirector (the default setting). If the basic redirector is used, the remote access program Rasphone cannot start, and an incoming connection cannot be reached.

Windows for Workgroups, MS-DOS, and LAN Manager clients can use the remote access NetBIOS gateway to access NetBIOS servers running TCP/IP or IPX but these clients cannot run programs that must use TCP/IP or IPX on the client.

These clients also do not support the PPP protocol introduced in Windows NT 3.5.

PPP clients

Non-Microsoft PPP clients that use TCP/IP or IPX can access an incoming connection. The incoming connection automatically negotiates authentication with PPP clients; special configuration for non-Microsoft PPP clients is not required.

For more information about your PPP client, see the software documentation for your PPP client.

The IPX/SPX protocol is not available on Windows XP 64-Bit Edition.

Incoming connections

Grant incoming connection access rights to your computer

Make an incoming network connection

Configure callback for incoming connections

Incoming connections and IP addresses

Configure an incoming connection to use TCP/IP

Configure a default gateway


Top of pageTop of page