Remote Desktop won't connect to Terminal Server across Internet.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to connect to a Terminal Server across the Internet from a
Windows XP computer on a LAN that is behind a Win 2000 SBS installation of
ISA.

I can connect to another computer across the Internet. The only difference
we are aware of is that the "problem" Terminal Server is using a different
port than the standard port of 3389.

We have configured an additional ISA filter to allow TCP communications via
the non-standard port, but it still won’t work.
 
Allen said:
I am trying to connect to a Terminal Server across the Internet from a
Windows XP computer on a LAN that is behind a Win 2000 SBS installation of
ISA.

I can connect to another computer across the Internet. The only difference
we are aware of is that the "problem" Terminal Server is using a different
port than the standard port of 3389.

We have configured an additional ISA filter to allow TCP communications
via
the non-standard port, but it still won’t work.
Click to expand...

You need to use the address form using a fully qualified domain name or
public IP of the server...

remote.terminalserver.address:portNumber

Examples:

12.34.56.78:9000

allens.terminalserver.address:9000

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304304

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
 
We already are.

Sorry I did not mention, but I guess I considered that obvious given the
rest of my post.
 
Allen said:
We already are.

Sorry I did not mention, but I guess I considered that obvious given the
rest of my post.
Click to expand...

Can you connect to the problematic Terminal Server from another Remote
Desktop client PC, ie. is the problem limited to one PC or all PCs that try
to connect to the TS?

Have you verified port forwarding is setup correctly on any firewall/router
the problematic TS is behind?

If you suspect an ISA issue I suggest posting to the microsoft.public.isa
news group.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
 
Can you connect to the problematic Terminal Server from another Remote
Desktop client PC, ie. is the problem limited to one PC or all PCs that try
to connect to the TS?
Click to expand...

So far, just the ones behind in the LAN behind ISA as I described in my
original post, but even those work when using the standard port.
Have you verified port forwarding is setup correctly on any firewall/router
the problematic TS is behind?
Click to expand...

It works for other RD clients so I guess so, although I have no control over
the problem TS network environment.
 
Back
Top