Cannot Remote Desktop Anymore

  • Thread starter Thread starter elziko
  • Start date Start date
E

elziko

I'm trying to remote desktop FROM my work computer to my HOME computer which
used to work.

I can ping my home computer.

I can telnet to my home computer on port 80 where I am running a web server
and I can view the web site it hosts.

I am *unable* to telent to my home computer on port 3389 where its is
expecting the remote desktop connection.

I have rung home and got someone to check that remote desktop is enabled and
that the port is open on the firewall.

I admit it looks like port 3389 isn't forwarded from my router to my home
machine but I have a few questions:

1) Are there any known issues that can occur with remote desktop after IIS
is installed?

2) Are there any other tests that I can carry out remotely to confirm the
problem?

3) Could it be another problem that I haven't thought of?

TIA
 
I'm trying to remote desktop FROM my work computer to my HOME computer
which
used to work.

I can ping my home computer.

I can telnet to my home computer on port 80 where I am running a web server
and I can view the web site it hosts.

I am *unable* to telent to my home computer on port 3389 where its is
expecting the remote desktop connection.

I have rung home and got someone to check that remote desktop is enabled and
that the port is open on the firewall.

I admit it looks like port 3389 isn't forwarded from my router to my home
machine but I have a few questions:

1) Are there any known issues that can occur with remote desktop after IIS
is installed?

2) Are there any other tests that I can carry out remotely to confirm the
problem?

3) Could it be another problem that I haven't thought of?

TIA
Click to expand...

Maybe your work finally blocked port 3389.
 
Maybe your work finally blocked port 3389.

I work for a small company and we're all open about this sort of thing. They
know I use remote desktop and they'd tell me if they intended to block the
port.

I did have to forward port 80 from my router to my home machine when I set
up IIS but I'm convinced I didn't 'unforward' the RDP port in the process. I
really can't think of anything else that may have changed!
 
Well if your trying to use the web based Remote Desktop method you need both
TCP Port 80 (IIS) and TCP Port 3389 (RDP) open on your home firewall. Also
be aware your personal home ISP may block TCP Port 80 because running a web
server violates the terms of service you agreed to when you signed up with
them.

Why even use the web based method if the normal RD method was working for
you?

--

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...
 
Well if your trying to use the web based Remote Desktop method you need
both TCP Port 80 (IIS) and TCP Port 3389 (RDP) open on your home firewall.
Also be aware your personal home ISP may block TCP Port 80 because running
a web server violates the terms of service you agreed to when you signed
up with them.
Click to expand...

I seem to be able to run a web server no problems!
Why even use the web based method if the normal RD method was working for
you?
Click to expand...

I'm not using the web based method. I have just set up a web server though.
The only reason I did a telnet to port 80 was because its the first time
I've tried a telnet and wanted to see a successful connection before I
tested the RDP port! Sorry for any confusion.

TIA
 
I work for a small company and we're all open about this sort of thing.
They
know I use remote desktop and they'd tell me if they intended to block the
port.

I did have to forward port 80 from my router to my home machine when I set
up IIS but I'm convinced I didn't 'unforward' the RDP port in the process. I
really can't think of anything else that may have changed!
Click to expand...

Convinced is one thing, sure (after checking) is another.
I would reboot home router and check port forwarding again.
 
Run the http://www.canyouseeme.org test at home from the PC you want to
access with RDP. If TCP Port 3389 is open on your firewall the test will
pass. If not the test will fail.

Also, have you tested this over your home LAN, ie. call from another PC
using the private LAN IP of the PC you want to remotely access?

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

More troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

--

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...
 
Run the http://www.canyouseeme.org test at home from the PC you want to
access with RDP. If TCP Port 3389 is open on your firewall the test will
pass. If not the test will fail.
Click to expand...

Thanks for the link it looks really useful!
Also, have you tested this over your home LAN, ie. call from another PC
using the private LAN IP of the PC you want to remotely access?

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

More troubleshooting help...

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
Click to expand...

I only have one PC on my home network (I have other devices connected but
nothing capable of runing Remote Desktop). But thanks for the other links,
I'll take a look.
 
Convinced is one thing, sure (after checking) is another.
I would reboot home router and check port forwarding again.
Click to expand...

Sure, thats my plan. But it'll have to wait until home time. Thanks for the
help.
 
Back
Top