Can't always connect to Terminal Server

[ABCRich]

We are attempting to connect 10 locations and have them run terminal server. We are using DSL in all locations. We first establish a VPN connection to the Main Location Server which is running Server 2000. We then attempt to start a terminal services session to the same server.

We can connect all locations through the VPN at the same time with no problem. We can get all of the locations to run Terminal Services at the same time as well. (This leads me to believe that we are not having a license issue.)

However, 1 out of 3 tries (approx) we will get a message "The client could not connect to the terminal server. The server may be too busy. Please try connection later."

I can't figure out why we are getting this or what is causing it. I can get it with the first connection or any other one for no rhyme or reason. The server is dedicated to run just this and I know its not overloaded so I can't believe it is busy. We have plenty of bandwith so I don't think that is the problem.

Many times we can restart the client machines (which are running 2000pro) and then they will start TS immediately.

Any ideas what is causing this intermittent error.

Thanks!

 

[CitrixEngineer]

This looks to be an ISP problem - I've seen similar situations in some of the Citrix MetaFrame setups I've worked on. Check what timeouts your ISP has set for you - and have a look here;

http://cable-dsl.home.att.net/,

and there is useful stuff here;

http://www.speedguide.net/.

I hope this helps

 

[Cryptospy]

A couple things to check:
1) Licensing - Make sure you have adequet CALS's
2) D-Link Router 704 needs the latest Firmware (Trust me)
3) You have a static address right?

Cryptospy

 

[ABCRich]

Just in case anyone else is having this problem, what we did to fix it was run terminal services without the VPN. We are still looking into how secure it is this way, but it runs much better. We just had to forward a port on our router and perfection. Thanks for the help.