Discussion Locked

98 client can't connect to TS via VPN

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a Win 2000 server running Terminal Services at our main office. We have multiple remote offices that have Win 98 clients that cannot connect to the Terminal Server through the VPN they create through the DSL connection to the Internet. Theclients were connecting fine via dial-up to the Internet and then connected via VPN and then launched their Terminal Session without any problems. We have since put these PCs on a LAN and have a broadband connection to the Internet VIA a DSL conection and when the 98 clients create an individual VPN connection to our VPN server and launch the Terninal Server Cleint, they get this error "The connection to the server has timed out. Try connecting to the terminal server again." I can then dial up to the Internet and create a VPN connection and launch the Terminal Server CLient and connect fine. I can use a Win 2000 Pro or XP Pro client and create a VPN connection over the LAN and launch the Terninal Server client and connect just fine. The Win98, 2000, and XP Pro clients all have the same network settings. I can ping the terminal server when the VPN connection is made through the LAN. All that has changed is that I connect to the Internet through the LAN and not through dial-up. The DSL router is running NAT.
Any help on this would be great!

7 replies

by lampi

The error is probably due to some of the network IP ports not being open on the Win98 clients when going over the LAN, especially of the Win98 clients are not running with the Second Edition updates.

There are some Microsoft Knowledge Base articles describing some of the Win98 IP networking issues that you might wish to peruse.

by brian

It is a Win98 SE Client and I have updated to DUN 1.4. It is not a prot problem because I can connect to my office via VPN to a NT 4.0 with RRAS which has a router to router VPN connection to the Terminal Server and it works fine.

by jon pratt

If the DSL router is doing the NAT'ng then it's probably not a port problem, otherwise it would be consistent with all of your workstations regardless of the OS. There's an easy way to confirm this, simply telnet into port 3389 (unless you've changed the default RDP port) and if it says connection failed then you've got a port problem if it connects then it's not a port problem. Assuming NAT is fowarding all of the necesary ports I would go to name resolution. If you haven't already tried going straight to the IP address of the Terminal Server instead of the name then I suggest giving that a try. If name resolution isn't your problem and port translation isn't your problem then the Terminal Server itself should have your answer. If you can make the connection to the RDP port and you can resolve the server name then when you try to connect to the Terminal Server you must actually be hitting the box and there should be a log event created explaining the reason for not accepting theconnection. You'll most likely find your answer under the system log in the event viewer, which will say, "Bad protocol stream","Unsupported Encryption", or any number of errors that might prevent a client from connecting to RDP. My guess is that it's either name resolution or a port problem. Hope this helps. Buena Suerte!

by brian

Your answer helpped, the resolution was a hot fix for Service Pack 2. Here is the Q article that explaines it in detail, Q301337.

by georgyporgy

like the 1st answer you for, what i suspect is that you have some closed ports/ have a look at what ports you need to have open, and last of all have a look at the settings on the terminal server; it could also be something to do with your ras. check them all and tell me how you get on.

This discussion is closed to new replies.