Really strange TS connection problem

I have a set of workstations at a remote job site trying to connect to
terminal servers at our main office. The remote job site uses a
satellite internet connection and Linksys router. There are two
servers at the main site - server1 is the ts licensing server and
server2 is the application server. Here’s my problem:

Several workstations at the remote site can’t connect to server2; they
get this error:

The client could not establish a connection to the remote computer.
The most likely causes for this are:

1) Remote connections might not be enabled at the remote computer
2) The maximum number of connections was exceeded at the remote
computer
3) A network error occurred while establishing the connection

I’ve tried just about everything. I’ve used both the XP and 2003
remote desktop clients, I’ve rebooted all networking hardware, taken
all other computers off the remote network, swapped out cables,
reloaded the OS. Other machines are able to make the connection just
fine, and some of the problem workstations can make a connection to
server1, just not server2. At the same time those workstations can
make a connection to server2 when using another internet connection
like a cable modem.

At this point I just can’t make any sense out of this. Doing away
with the satellite internet is not an option, but I don’t think that’s
really the problem since other clients are able to use it
successfully. I really need some help with this. Does anyone have
any ideas?

Thanks

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Network...ict581767.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=2452602

Satelite connections have a heavey "lag" that may make it unsuitable for
what you want to do.

One car traveling at 20mph has 50 feet to go
Another car traveling at 300mph has 5 miles to go

The second one is faster (high bandwidth/throughput), but the first one will
still get there first (lowest "travel-time" lag).

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"cmalmstrom" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have a set of workstations at a remote job site trying to connect to
> terminal servers at our main office. The remote job site uses a
> satellite internet connection and Linksys router. There are two
> servers at the main site - server1 is the ts licensing server and
> server2 is the application server. Here's my problem:
>
> Several workstations at the remote site can't connect to server2; they
> get this error:
>
> The client could not establish a connection to the remote computer.
> The most likely causes for this are:
>
> 1) Remote connections might not be enabled at the remote computer
> 2) The maximum number of connections was exceeded at the remote
> computer
> 3) A network error occurred while establishing the connection
>
> I've tried just about everything. I've used both the XP and 2003
> remote desktop clients, I've rebooted all networking hardware, taken
> all other computers off the remote network, swapped out cables,
> reloaded the OS. Other machines are able to make the connection just
> fine, and some of the problem workstations can make a connection to
> server1, just not server2. At the same time those workstations can
> make a connection to server2 when using another internet connection
> like a cable modem.
>
> At this point I just can't make any sense out of this. Doing away
> with the satellite internet is not an option, but I don't think that's
> really the problem since other clients are able to use it
> successfully. I really need some help with this. Does anyone have
> any ideas?
>
> Thanks
>
> --
> http://www.WindowsForumz.com/ This article was posted by author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
http://www.WindowsForumz.com/Network...ict581767.html
> Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.WindowsForumz.com/eform.php?p=2452602

"cmalmstrom" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> At this point I just can't make any sense out of this. Doing away
> with the satellite internet is not an option, but I don't think that's
> really the problem since other clients are able to use it
> successfully. I really need some help with this. Does anyone have
> any ideas?

What other clients? What type of stuff you actually do makes a difference
on whether the Sat-link will work with it or not. Life just isn't that
simple with this stuff...

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The other workstations at the remote site are Windows 2000, using the
2003 remote desktop client. The server is Windows 2000. To recap, I
can take one of the problem machines home and connect to server2 over
my cable modem just fine, but when I pack up that machine and take it
to the remote site I get the error I listed above. The machine
sitting right next to it has never had a problem connecting to
server2. I don’t think it’s a bandwidth issue, because we can get
multiple machines connected. Any more specific info that would be
helpul?

--
http://www.WindowsForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.WindowsForumz.com/Network...ict581767.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.WindowsForumz.com/eform.php?p=2453363