The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Remote Desktop Help!

    Discussion in 'Windows OS and Software' started by Dspr_02, Oct 14, 2010.

  1. Dspr_02

    Dspr_02 Notebook Evangelist

    Reputations:
    93
    Messages:
    529
    Likes Received:
    0
    Trophy Points:
    30
    I have been having some remote desktop issues with my desktop...

    From all devices, I cannot connect to it.

    This started about a two days ago. Up until then I was able to use remote desktop.

    The IP is a static IP, reserved in the router's DHCP list.
    The proper ports (3390) are forwarded to the PC in the router.
    The PC is always on with working internet connection.
    My external (ISP) IP Address has not changed.
    Firewall is off (host and client pc)
    No updates in the past month (host or client pc).

    I can connect if I type in the local IP ( 192.168.0.xxx) or the pc name however, I cannot do "12.345.678.90:3390" (not my actual IP :p) and connect.
    I can also connect to any other PC in the house (setup for remote desktop) by using the external IP and proper ports...

    Everything is setup right and it was working for weeks before hand, nothing has changed and no updates have been done.

    Please help!
     
    Dspr_02, Oct 14, 2010
    #1
  2. mfractal

    mfractal T|I

    Reputations:
    1,948
    Messages:
    2,890
    Likes Received:
    1
    Trophy Points:
    55
    Does telnet to your external ip and port work ?
     
    mfractal, Oct 14, 2010
    #2
  3. Primes

    Primes Notebook Deity

    Reputations:
    919
    Messages:
    1,736
    Likes Received:
    718
    Trophy Points:
    131
    I thought the default port was 3389.
     
    Primes, Oct 14, 2010
    #3
  4. DetlevCM

    DetlevCM Notebook Nobel Laureate

    Reputations:
    4,843
    Messages:
    8,389
    Likes Received:
    1
    Trophy Points:
    205
    Blocked port somewhere is my guess.

    The Easiest choice for you would really be to switch to teamviewer (it can load before the log in) and use that - just uses the plain port 80 and works from pretty much anyplace with web access.

    I know it's not quite what you want - but it solves your issue.
     
    DetlevCM, Oct 15, 2010
    #4
  5. wave

    wave Notebook Virtuoso

    Reputations:
    813
    Messages:
    2,563
    Likes Received:
    0
    Trophy Points:
    55
    You could try changing the listener port using the registry:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

    Then update the port forward and see if it works.
     
    wave, Oct 15, 2010
    #5
  6. Dspr_02

    Dspr_02 Notebook Evangelist

    Reputations:
    93
    Messages:
    529
    Likes Received:
    0
    Trophy Points:
    30
    The port is forwarded to 3390 (as is my router - forwarding any and all incoming connections to my PC on port 3390).

    I know for a fact that my ISP, Shaw Cable-systems, blocks port 80, along with Telus and I suspect Rogers.
     
    Dspr_02, Oct 15, 2010
    #6
  7. DetlevCM

    DetlevCM Notebook Nobel Laureate

    Reputations:
    4,843
    Messages:
    8,389
    Likes Received:
    1
    Trophy Points:
    205
    But that's the standard HTTP port? I.e. standard web access... how do you go online then?

    And TeamViewer can use proxies.
     
    DetlevCM, Oct 16, 2010
    #7
  8. mfractal

    mfractal T|I

    Reputations:
    1,948
    Messages:
    2,890
    Likes Received:
    1
    Trophy Points:
    55
    Did you try to telnet to make sure the port is actually open??
     
    mfractal, Oct 16, 2010
    #8
  9. Dspr_02

    Dspr_02 Notebook Evangelist

    Reputations:
    93
    Messages:
    529
    Likes Received:
    0
    Trophy Points:
    30
    Port 80 is closed on xxx.xxx.xxx.xxx .

    Microsoft Telnet> o 192.168.0.100 [3390]
    Connecting To 192.168.0.100...Could not open connection to the host, on port [33
    90]: Connect failed

    I'll try restarting the router (DIR-615 ughhh).

    If that doesn't work, I will just reinstall windows since the pc acts as a media server and I have nothing on my SSD besides the OS and two media players (all media etc is on other HDD's).
     
    Dspr_02, Oct 16, 2010
    #9
  10. mfractal

    mfractal T|I

    Reputations:
    1,948
    Messages:
    2,890
    Likes Received:
    1
    Trophy Points:
    55
    Local port 80 only needs to be open if you are hosting a website or anything else o port 80 that needs to be accessed from outside. Lots of ISPs block it to keep you from running websites. It doesn't have anything to do with the ability to surf as it is outgoing port 80 requests that are used to surf.
     
    mfractal, Oct 16, 2010
    #10
  11. Alex

    Alex Super Moderator

    Reputations:
    4,081
    Messages:
    4,293
    Likes Received:
    10
    Trophy Points:
    106
    Closed as per OP request
     
    Alex, Nov 5, 2010
    #11