terminal service connection problem

[cmalmstrom]

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

[[WindowsForumz.com editor: this is a repost, since the original post
was erased from our system due to a tech. glitch. Thanks and sorry
for the repost!]]

 

[Steven L Umbach]

I don't know what the exact problem is but here are some things to consider or try.

-- If you have not done so, try using the public IP address of your main site to
connect to the Terminal Services instead of a fully qualified domain name.

-- Check any and all firewalls, including the built in XP ICF firewall or other
personal firewalls/protection applications on the problem computers. The error
message you get is a generic error meaning "no one is answering or found". Hardware
firewalls at the remote site which sounds like a main suspect since access works over
a different connection [outbound traffic]or the main site [inbound traffic]could be
blocking access and allowing only certain IP address to use port 3389 TCP which is
the default port for TS. If you are going in through a vpn, check your firewall vpn
configuration and any packet filters on the external adapter on your vpn server etc.
The Terminal Servers themselves may be using a software firewall or an ipsec
filtering policy to manage access. Check your firewall logs for packets dropped or
blocked access attempts on port 3389. Using telnet into port 3389 tcp, a port scanner
such as the free Superscan, or even Ethereal packet sniffer can help determine what
is going on with traffic to and from the TS server.

-- Make sure there are no ipsec filtering polices on the problem computers [look in
Local Security Policy] which they would not have by default unless you applied a
security template after the install or otherwise modified security options. If the
remote computers are in a domain, see if they are in the same container such as
Organizational Unit. If they are not in the same container, they may have different
security policy applied to then which may be a factor. Good luck. --- Steve

-- Put the problem computers on the same exact network cable as a computer that does
not have the problem and temporally give it the same IP address and other tcp/ip
configuration [dns, etc] after taking the working computer offline and try again. If
still no joy, try booting into safe mode with networking and try again. If still no
good take the network adapter out of the good machine, put it in the problem machine
and try again.

-- Contact the satellite ISP and see if they can be any help explaining that the
connection works through an alternate connection. --- Steve

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

[[WindowsForumz.com editor: this is a repost, since the original post
was erased from our system due to a tech. glitch. Thanks and sorry
for the repost!]]

--
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/Networking-terminal-service-connection-problem-ftopict584316.html
Visit Topic URL to contact author (reg. req'd). Report abuse:

http://www.WindowsForumz.com/eform.php?p=2459655