Virtual private networking clients
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Virtual private networking clients
Virtual private networking clients that connect to Routing and Remote Access can be computers running a member of the Windows Server 2003 family, Windows XP, Windows 2000, Windows NT 4.0, Windows 95, Windows 98, or Windows Millennium Edition. The client must be able to send TCP/IP packets to the remote access server over the Internet. Therefore, either a network adapter or modem with an analog telephone line or other WAN connection to the Internet is required.
Tunneling protocols for Microsoft virtual private network clients
Support for tunneling protocols by Microsoft virtual private networking clients is outlined in the following table.
| Virtual private networking client | Supported tunneling protocols | Unsupported tunneling protocols |
|---|---|---|
Windows Server 2003 family, Windows 2000, and Windows XP |
Point-to-Point Tunneling Protocol (PPTP) and Layer Two Tunneling Protocol (L2TP) |
|
Windows NT version 4.0 |
PPTP |
L2TP |
Windows Millennium Edition and Windows 98 |
PPTP |
L2TP |
Windows 95 with the Windows Dial-Up Networking 1.3 Performance & Security Upgrade for Windows 95 |
PPTP |
L2TP |
Windows Millennium Edition, Windows 98, Windows NT 4.0 Workstation, and Windows 95 with Microsoft L2TP/IPSec VPN Client installed |
L2TP |
Notes
Windows NT version 3.5x does not support either PPTP or L2TP.
For more information about virtual private networks, Microsoft L2TP/IPSec VPN Client, and networking upgrades, see the Microsoft Web site.
Authentication for Microsoft virtual private network clients
Support for authentication protocols by Microsoft virtual private networking clients is outlined in the following table.
| Virtual private networking client | Supported remote access authentication protocols | Unsupported remote access authentication protocols |
|---|---|---|
Windows Server 2003 family, Windows XP, and Windows 2000 |
Microsoft Challenge Handshake Authentication Protocol (MS-CHAP), Challenge Handshake Authentication Protocol (CHAP), Shiva Password Authentication Protocol (SPAP), Password Authentication Protocol (PAP), MS-CHAP version 2 (MS-CHAP v2), and Extensible Authentication Protocol (EAP) |
|
Windows NT version 4.0 |
MS-CHAP, CHAP, SPAP, PAP, and MS-CHAP v2 (with the Windows NT 4.0 Service Pack 4 and later) |
EAP |
Windows 98 |
MS-CHAP, CHAP, SPAP, PAP, and MS-CHAP v2 (with the Windows 98 Service Pack 1 and later) |
EAP |
Windows 95 |
MS-CHAP, CHAP, SPAP, PAP, and MS-CHAP v2 (with the Dial-Up Networking 1.4 Upgrade) |
EAP |
Note
- Windows 95 with the Dial-Up Networking 1.4 Upgrade supports MS-CHAP v2 over virtual private network (VPN) connections but not over dial-up connections. For more information about virtual private networks and networking upgrades, see the Microsoft Web site .
Other virtual private network (VPN) clients
Other virtual private network clients that use PPTP or L2TP with Internet Protocol security (IPSec) can access a server running Routing and Remote Access. However, if you want secure VPN connections, you must make sure that clients support the proper encryption. For PPTP, Microsoft Point-to-Point Encryption (MPPE) must be supported. For L2TP, IPSec encryption must be supported.
For more information, see the documentation provided with the virtual private network client.