Can't connect to Terminal Server over VPN from Windows 2000 clients, Only XP Professional
Posted on 2004-09-27
We have 2 servers. One is the PDC running SBS 2000 Server and the 2nd is a BDC setup as a VPN/Terminal Server.
The VPN server has only one network card and we are passing port 1723 through a 3com Officeconnect Firewall to the internal IP address of the VPN server.
Any remote client CAN successfully connect and authenticate to the VPN Server regardless of OS.
The problem is that only XP Professional remote pc's can connect to the VPN/TS via it's internal ip address. Windows 2000 Professional clients cannot connect to the Terminal Server and also cannot ping it by IP address.
Since Terminal Services and VPN Services are setup properly, what is different between Win 2000 Pro and XP Pro which is preventing some clients from hitting the TS.
I have tried 2 different Win 2000 Pro clients on different remote networks and neither can ping the TS while an XP Pro client on the same remote network has no problem whatsoever. I have setup all pc's to use the default gateway setting in the VPN client.