Problem connecting to a Windows 2003 Terminal Server through a VPN

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rey - 26 Nov 2003 16:02 GMT

I have a Remote Server running a Windows 2003 Terminal Server.

I am connecting via an Internet connection through a VPN using
NetScreen Remote from my Windows XP Professional laptop.

I can connect from my laptop using my dial-up Internet connections. I
can also connect to the terminal server from our high-speed DSL
connection in our office. But if I tried to connect from my home's
high-speed DSL connection (using the same laptop), it wouldn't connect
at all even though I could PING the Terminal Server (gives a message
about unable to establish network connection). I checked the Terminal
Server error logs, but there's nothing in it. I tried connecting with
the Windows XP Firewall on and off - and the same results.

Can anyone suggests some troubleshooting steps I could go through to
find out what the problem is?

Reply to this Message

Marc Reynolds [MSFT] - 26 Nov 2003 16:52 GMT

It could be the VPN endpoint is not allowing TCP port 3389 traffic. When
connected to the VPN can you telnet from the client to port 3389 on the
Terminal Server?

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

> I have a Remote Server running a Windows 2003 Terminal Server.
>
[quoted text clipped - 12 lines]
> Can anyone suggests some troubleshooting steps I could go through to
> find out what the problem is?

Reply to this Message

Rey - 27 Nov 2003 03:40 GMT

Thanks for the reply, Marc. What is the telnet command to try port
3389? is it:

telnet <server ip address> 3389

I tried that and it gave me a blank screen for a few seconds and then
ended up on a DOS prompt.

I think port 3389 is open though because, using the same laptop, I can
connect to the Terminal Server using a dial-up internet connection--
or from my office's broadband connection. Its with my home's
broadband connection which is I'm having problem. The exact error
message I am getting when i tried to connect is:

"The connection to the remote computer was broken. This may have been
caused by a network error. Please try connecting to the remote
computer again."

I tried several times but that message keeps on coming after trying to
connect for about a minute.

any other troubleshooting suggestions?

=========================

> It could be the VPN endpoint is not allowing TCP port 3389 traffic. When
> connected to the VPN can you telnet from the client to port 3389 on the
[quoted text clipped - 22 lines]
> > Can anyone suggests some troubleshooting steps I could go through to
> > find out what the problem is?

Reply to this Message

Jeffrey Randow (MVP) - 27 Nov 2003 09:49 GMT

Yes, that is the telnet command....

What type of router/firewall do you have? If it is a Linksys, there
are known issues with certain firmware releases. Check the Linksys
forum at http://www.dslreports.com for more informaiton.

Jeffrey Randow (Windows MVP - Networking & Smart Display)
winxp@longhornconsulting.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Wiki -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

>Thanks for the reply, Marc. What is the telnet command to try port
>3389? is it:
[quoted text clipped - 47 lines]
>> > Can anyone suggests some troubleshooting steps I could go through to
>> > find out what the problem is?

Reply to this Message

Rey - 27 Nov 2003 19:05 GMT

The Terminal Server is using Netscreen for their router/firewall. I
have Netscreen Remote on my laptop.

I can ping the Terminal Server. I can even map a drive letter to a
shared network drive. But I can't run REMOTE DESKTOP. It tried for
about a minute and ended up with this error message:

REMOTE DESKTOP DICONNECTED:

The connection to the remote computer was broken. This may have been
caused by a network error. Please try connecting to the remote
computer again.

No error log is being registered in the Terminal Server.

=======================================================

> Yes, that is the telnet command....
>
[quoted text clipped - 65 lines]
> >> > Can anyone suggests some troubleshooting steps I could go through to
> >> > find out what the problem is?

Reply to this Message