Windows Forum

Ask something
Discussion Locked

Windows 2000 terminal services

0 helpful
5 replies

by dmcconnell

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a main office running a windows 2000 server, and were connecting to this from a branch office using a windows vpn and terminal services through the internet. Everything was working ok until one day last week. Suddenly our windows 95 machines can no longer connect to the terminal server. The virtual private network connects fine, but when we try to connect to the terminal server, we get a message saying "The connection to the server has timed out. Try connecting to the Terminal Server again." We also have a windows 2000 pro machine at the branch office that can connect just fine. Why are we suddenly having problems?

5 replies

by ian mclaws

Just a thought. Have you confirmed that the system time has not been changed on either the server or the 95 clients? (Or that it is in sync.) Terminal services is fairly time sensitive in 2K; out of sync times can cause this error.

Good luck,

Ian

by mckaytech

This is all a Microsoft plot to force you to upgrade your Win95 machines to W2K...

Actually, we've seen this problem occasionally when accessing our Terminal Server over a Cisco 3000 VPN system and we haven't quite figured it out yet. I like theanswer above and we will certainly be looking at the time sync but we think we're looking at either a domain issue (because our W2K machines are joined to the domain while our Win95 machines are not) or a WINS issue.

I would be interested in knowing whether pinging the Terminal Server from within the VPN session makes any difference. In our case, if we would ping the server first, the connection will then establish normally. At that point, it starts sounding like an ARP issue.

paul

by dmcconnell

Thanks for your reply. The interesting thing was we could ping after setting up the virtual private network. In fact, we never had a problem setting up the vpn, even though the same server did both. It looks now like it was a problem with the dslline.

This discussion is closed to new replies.