Remote Desktop Web Connection through the internet

[Guest]

I have Windows Vista Ultimate at home connected to the internet via a Linksys
WAG354G router (wired). I am running IIS with tsweb installed. The router
is 192.168.1.1 and the PC is 192.168.1.2 (allocated via DHCP from the router)

I am trying to connect to the PC using my work laptop (a Dell D620). Within
the network I can access the Remote Desktop connection by using
http://external IP address/twseb. Typing in 192.168.1.2 will then bring up
the remote login screen for the PC.

However, outside the network, I still get the Remote Desktop login screen,
but when I type in 192.168.1.2 I get the following message:-

"The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connection again later. If the problem continues to
occur, contact your administrator."

I have set the router to forward the following applications and ports:-

IIS 80 192.168.1.2
RDP 3389 192.168.1.2

I also tried forwarding both HTTP 80 and HTTP 3389 to 192.168.1.2 but this
also did not work.

I though that this might be because the work network is blocking ports, but
I have now tried it from 2 alternative locations and had the same problem.

Something is obviously wrong but I cannot find any answer as to what is
causing it. As I can connect from inside the network, the problem cannot be
authentication on TS or IIS, and since I can see the Remote Desktop login
screen from outside the network, both IIS and TS are obviously working
correctly and my connection is being routed properly through the router.

Can anyone advise?

 

[Sooner Al [MVP]]

I have Windows Vista Ultimate at home connected to the internet via a
Linksys
WAG354G router (wired). I am running IIS with tsweb installed. The
router
is 192.168.1.1 and the PC is 192.168.1.2 (allocated via DHCP from the
router)

I am trying to connect to the PC using my work laptop (a Dell D620).
Within
the network I can access the Remote Desktop connection by using
http://external IP address/twseb. Typing in 192.168.1.2 will then bring
up
the remote login screen for the PC.

However, outside the network, I still get the Remote Desktop login screen,
but when I type in 192.168.1.2 I get the following message:-

"The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connection again later. If the problem continues to
occur, contact your administrator."

I have set the router to forward the following applications and ports:-

IIS 80 192.168.1.2
RDP 3389 192.168.1.2

I also tried forwarding both HTTP 80 and HTTP 3389 to 192.168.1.2 but this
also did not work.

I though that this might be because the work network is blocking ports,
but
I have now tried it from 2 alternative locations and had the same problem.

Something is obviously wrong but I cannot find any answer as to what is
causing it. As I can connect from inside the network, the problem cannot
be
authentication on TS or IIS, and since I can see the Remote Desktop login
screen from outside the network, both IIS and TS are obviously working
correctly and my connection is being routed properly through the router.

Can anyone advise?

You need to use the public IP of your router, ie. the IP assigned by your
ISP.

Also note that some ISP block TCP Port 80 (IIS) if your on a residential
account because running a web server violates the terms of service for
non-business accounts.

Personally I see no need to use the web based method particularly from your
own laptop. I use Remote Desktop (non web based method) through a SSH
tunnel.

--

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

 

[Guest]

Thanks, but that doesn't answer the question.

I can access the IIS Remote Desktop login page through the internet, so I
guess this means that port 80 IS accessible?

And the reason for wanting to do this in the first place is that Remote
Desktop is deactivated and blocked on my laptop through my employer's
policies.

Chris St Clair

 

[Sooner Al [MVP]]

Thanks, but that doesn't answer the question.

I can access the IIS Remote Desktop login page through the internet, so I
guess this means that port 80 IS accessible?

And the reason for wanting to do this in the first place is that Remote
Desktop is deactivated and blocked on my laptop through my employer's
policies.

Chris St Clair

I misread the post, sorry...

Its still possible they block TCP Port 3389 outbound. Have you tried from
another location other than your work? Keep in mind there may be policies
against connecting your untrusted home system to your trusted work system.


--

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

 

[Guest]

No probs Al - this one is driving me nuts as I thought I'd got it licked!

Just to clarify - I've tried through the network at work, through the
network at home (VPN'ing into work then back again), and I've also tried 2
alternative locations, one being a Tmobile wireless access point.

All will allow access to the Remote Desktop Web login screen but no further.
My knowledge of networking isn't brilliant, but I guess it must be either a
port issue, or something to do with IIS/TS refusing logins which are not
within the network?

Thanks for your help so far - figuring out what ISN'T causing the problem
should eventually get us to what IS!!!

Chris

 

[Sooner Al [MVP]]

No probs Al - this one is driving me nuts as I thought I'd got it licked!

Just to clarify - I've tried through the network at work, through the
network at home (VPN'ing into work then back again), and I've also tried 2
alternative locations, one being a Tmobile wireless access point.

All will allow access to the Remote Desktop Web login screen but no
further.
My knowledge of networking isn't brilliant, but I guess it must be either
a
port issue, or something to do with IIS/TS refusing logins which are not
within the network?

Thanks for your help so far - figuring out what ISN'T causing the problem
should eventually get us to what IS!!!

Chris

Well, I don't know what to say if you tried it from another location than
work and the same thing happens. I don't use the web based method at all so
I am out of ideas.

From a remote location other than work can you connect to the home PC using
the regular Remote Desktop method, ie. not the web based method, as a test.
That will verify whether or not port forwarding through the router is
working correctly for TCP Port 3389.

Are you running a software firewall or other similar software on the home PC
that may be blocking TCP Port 3389 traffic from a remote IP versus the local
subnet?

--

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

 

[Guest]

Hi Al,

Some progress...

I tried it from my partner's PC at her house... and was able to successfully
connect using Remote Desktop. However Remote Deskop Web Connection would
still not connect...

Any ideas?

Chris

 

[Sooner Al [MVP]]

Hi Al,

Some progress...

I tried it from my partner's PC at her house... and was able to
successfully
connect using Remote Desktop. However Remote Deskop Web Connection would
still not connect...

Any ideas?

Chris

No ideas other than checking the logs on the home Remote Desktop host PC
running IIS. You may find a clue.

Also, have you installed the newest RDP 6 client software? That includes a
new ActiveX component. Its possible that may be the issue, ie. you need the
new ActiveX component, since your trying to connect to a Vista box. You
might try that from your partners PC. If that is in fact the case then you
may have issues at work where I presume you do not have admin privileges on
your workstation or laptop. Note this is built-in to Vista but if your
running XP you need to download and install it.

http://support.microsoft.com/kb/925876

Sorry I can't be of more help...

--

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