Results 1 to 14 of 14

Thread: remote desktop + adsl router = huh

  1. #1
    cat /dev/null streetster's Avatar
    Join Date
    Jul 2003
    Location
    London
    Posts
    4,138
    Thanks
    119
    Thanked
    100 times in 82 posts
    • streetster's system
      • Motherboard:
      • Asus P7P55D-E
      • CPU:
      • Intel i5 750 2.67 @ 4.0Ghz
      • Memory:
      • 4GB Corsair XMS DDR3
      • Storage:
      • 2x1TB Drives [RAID0]
      • Graphics card(s):
      • 2xSapphire HD 4870 512MB CrossFireX
      • PSU:
      • Corsair HX520W
      • Case:
      • Coolermaster Black Widow
      • Operating System:
      • Windows 7 x64
      • Monitor(s):
      • DELL U2311
      • Internet:
      • Virgin 50Mb

    remote desktop + adsl router = huh

    hey guys,

    What do i need to do on my router so that I can remote desktop in from outside?

    Google suggests that Windows uses port 3389, so i added the following setting to my router (conexant origo crappy thing):

    Code:
    ID 	Public Port - Start 	Public Port - End 	Private Port 	Port Type 	Host IP Address
    1 	3388 	3390 	3389 	UDP 	192.168.0.250
    in the 'virtual server' section - I couldnt see an explicit 'port forwarding' section... should this work, and how can i test this internally?

  2. #2
    Senior Member
    Join Date
    Feb 2005
    Posts
    530
    Thanks
    23
    Thanked
    5 times in 5 posts
    • Neo_VR's system
      • Motherboard:
      • DFI X48L2R
      • CPU:
      • QX9450@3.2gig
      • Memory:
      • 4gb Corsair
      • Storage:
      • 2x36gb raptors striped 640gb AAKS
      • Graphics card(s):
      • Gainward 8800gt
      • PSU:
      • Enermax Liberty 600
      • Case:
      • Antec P182
      • Operating System:
      • Vista Ultimate
      • Monitor(s):
      • Dell 22" wfp
      • Internet:
      • BT 8meg
    I really would avoid exposing RDP to the outside... its one of the "known ports" that are scanned when you get portscanned..

    im pretty sure theres a way to change the port rdp goes over.. ill have a look around

  3. #3
    Administrator Moby-Dick's Avatar
    Join Date
    Jul 2003
    Location
    There's no place like ::1 (IPv6 version)
    Posts
    10,665
    Thanks
    53
    Thanked
    385 times in 314 posts
    I think its TCP , not UDP that you want to forward.

    Having aN RDP port open is the worst thign in the world , but ensure that any account that has remote access has a very strong password + change the port if possible
    my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net

  4. #4
    cat /dev/null streetster's Avatar
    Join Date
    Jul 2003
    Location
    London
    Posts
    4,138
    Thanks
    119
    Thanked
    100 times in 82 posts
    • streetster's system
      • Motherboard:
      • Asus P7P55D-E
      • CPU:
      • Intel i5 750 2.67 @ 4.0Ghz
      • Memory:
      • 4GB Corsair XMS DDR3
      • Storage:
      • 2x1TB Drives [RAID0]
      • Graphics card(s):
      • 2xSapphire HD 4870 512MB CrossFireX
      • PSU:
      • Corsair HX520W
      • Case:
      • Coolermaster Black Widow
      • Operating System:
      • Windows 7 x64
      • Monitor(s):
      • DELL U2311
      • Internet:
      • Virgin 50Mb
    Quote Originally Posted by microsoft.com
    Q. What port does Remote Desktop use? Does everything go over port 3389?
    A.

    Port 3389 is the only port you need to open. Windows will attempt to stream sound through User Datagram Protocol (UDP) first. If no port is available for UDP, sound will stream through a virtual channel in Remote Desktop Protocol, which uses port 3389.

    I realise port 3389 is a bad choice, but I thought I'd try it just to get it working, before changing to a random number and adding a nice strong password to the account It was mostly for my exam in the morning (so I can remote desktop in from uni if I need anything, or if the uni computers start playing up), but looks like i'll have to cross my fingers instead...

  5. #5
    Today is Tuesday
    Join Date
    Oct 2004
    Location
    London
    Posts
    441
    Thanks
    7
    Thanked
    4 times in 4 posts
    I am curious as to why you have a range of public ports but only a single private one. I would set the public port boxes to 3389 (not 3388-3390) to ensure it will work, and it will definitely work.

    However, as recommended, I would definitely change the public port to 13389 or something similar (again in both boxes). It will not affect RDC working (I can guarantee that), but will be much stronger. When connecting to your home computer you just add ':13389' at the end of your computers IP address.

  6. #6
    Jay
    Jay is offline
    Gentlemen.. we're history Jay's Avatar
    Join Date
    Aug 2006
    Location
    Jita
    Posts
    8,365
    Thanks
    304
    Thanked
    568 times in 409 posts
    setup a VPN if you can

  7. #7
    cat /dev/null streetster's Avatar
    Join Date
    Jul 2003
    Location
    London
    Posts
    4,138
    Thanks
    119
    Thanked
    100 times in 82 posts
    • streetster's system
      • Motherboard:
      • Asus P7P55D-E
      • CPU:
      • Intel i5 750 2.67 @ 4.0Ghz
      • Memory:
      • 4GB Corsair XMS DDR3
      • Storage:
      • 2x1TB Drives [RAID0]
      • Graphics card(s):
      • 2xSapphire HD 4870 512MB CrossFireX
      • PSU:
      • Corsair HX520W
      • Case:
      • Coolermaster Black Widow
      • Operating System:
      • Windows 7 x64
      • Monitor(s):
      • DELL U2311
      • Internet:
      • Virgin 50Mb
    Quote Originally Posted by explicitlyrics View Post
    I am curious as to why you have a range of public ports but only a single private one. I would set the public port boxes to 3389 (not 3388-3390) to ensure it will work, and it will definitely work.

    However, as recommended, I would definitely change the public port to 13389 or something similar (again in both boxes). It will not affect RDC working (I can guarantee that), but will be much stronger. When connecting to your home computer you just add ':13389' at the end of your computers IP address.
    heh, I tried setting up 3389 to 3389 initially and it didnt even show up in the list... so I had to do 3388 to 3390 (ie a range) just to get it in the list. like i said, this router is really crap...

    ok it worked for 13389->13389, changed the rdp port in the registry, lets reboot and see if it'll work


    right if i do:

    myhostname:13389 it connects, if i do myexternalip:13389, it wont.

    any ideas guys?
    Last edited by streetster; 22-01-2007 at 09:22 AM.

  8. #8
    Administrator Moby-Dick's Avatar
    Join Date
    Jul 2003
    Location
    There's no place like ::1 (IPv6 version)
    Posts
    10,665
    Thanks
    53
    Thanked
    385 times in 314 posts
    read your quote again

    Windows will attempt to stream sound through User Datagram Protocol (UDP) first
    try forwarding TCP3389.
    my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net

  9. #9
    Lovely chap dangel's Avatar
    Join Date
    Aug 2005
    Location
    Cambridge, UK
    Posts
    8,398
    Thanks
    412
    Thanked
    459 times in 334 posts
    • dangel's system
      • Motherboard:
      • See My Sig
      • CPU:
      • See My Sig
      • Memory:
      • See My Sig
      • Storage:
      • See My Sig
      • Graphics card(s):
      • See My Sig
      • PSU:
      • See My Sig
      • Case:
      • See My Sig
      • Operating System:
      • Windows 10
      • Monitor(s):
      • See My Sig
      • Internet:
      • 60mbit Sky LLU
    Much easier way to do it (and secure) - download hamachi. With it you can setup a vitual network with a few clicks - then any other PC can also run hamachi and join said network. Remote desktop then 'just works' (as does everything else). I use it this way all the time to access my server at home
    Crosshair VIII Hero (WIFI), 3900x, 32GB DDR4, Many SSDs, EVGA FTW3 3090, Ethoo 719


  10. #10
    Splash
    Guest
    Quote Originally Posted by streetster View Post
    heh, I tried setting up 3389 to 3389 initially and it didnt even show up in the list... so I had to do 3388 to 3390 (ie a range) just to get it in the list. like i said, this router is really crap...

    ok it worked for 13389->13389, changed the rdp port in the registry, lets reboot and see if it'll work


    right if i do:

    myhostname:13389 it connects, if i do myexternalip:13389, it wont.

    any ideas guys?
    A lot of routers don't support loopback, so this wouldn't work. Also be aware that if you're trying to access your home network from work you'll probably find that it won't work due to network configuration (if your network admins are worth their salt, anyways...)

  11. #11
    cat /dev/null streetster's Avatar
    Join Date
    Jul 2003
    Location
    London
    Posts
    4,138
    Thanks
    119
    Thanked
    100 times in 82 posts
    • streetster's system
      • Motherboard:
      • Asus P7P55D-E
      • CPU:
      • Intel i5 750 2.67 @ 4.0Ghz
      • Memory:
      • 4GB Corsair XMS DDR3
      • Storage:
      • 2x1TB Drives [RAID0]
      • Graphics card(s):
      • 2xSapphire HD 4870 512MB CrossFireX
      • PSU:
      • Corsair HX520W
      • Case:
      • Coolermaster Black Widow
      • Operating System:
      • Windows 7 x64
      • Monitor(s):
      • DELL U2311
      • Internet:
      • Virgin 50Mb
    @Moby - right, i'll learn to read will change it to TCP rather than UDP (or add both)...

    @Splash, i will get someone external to try the remote desktop connection to rule out the loopback issue.. and some other people were accessing their machines from the uni labs, so hopefully i'll be able to do it from here (here meaning im now in the labs lol)

  12. #12
    Administrator Moby-Dick's Avatar
    Join Date
    Jul 2003
    Location
    There's no place like ::1 (IPv6 version)
    Posts
    10,665
    Thanks
    53
    Thanked
    385 times in 314 posts
    other way of accessing your machine are available

    I use www.logmein.com
    my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net

  13. #13
    cat /dev/null streetster's Avatar
    Join Date
    Jul 2003
    Location
    London
    Posts
    4,138
    Thanks
    119
    Thanked
    100 times in 82 posts
    • streetster's system
      • Motherboard:
      • Asus P7P55D-E
      • CPU:
      • Intel i5 750 2.67 @ 4.0Ghz
      • Memory:
      • 4GB Corsair XMS DDR3
      • Storage:
      • 2x1TB Drives [RAID0]
      • Graphics card(s):
      • 2xSapphire HD 4870 512MB CrossFireX
      • PSU:
      • Corsair HX520W
      • Case:
      • Coolermaster Black Widow
      • Operating System:
      • Windows 7 x64
      • Monitor(s):
      • DELL U2311
      • Internet:
      • Virgin 50Mb
    right, tried from my gf's house, worked fine next step is to try from uni next time im in...

    thanks for the help guys

  14. #14
    Registered+
    Join Date
    Dec 2006
    Posts
    31
    Thanks
    0
    Thanked
    0 times in 0 posts
    Streetster - if thats doesn't work then it's most likely security on the Uni network...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Draytek Vigor 2800G mini-review
    By Taz in forum Networking and Broadband
    Replies: 13
    Last Post: 05-09-2020, 08:28 PM
  2. Remote desktop to a PC on ADSL
    By KW1816 in forum Networking and Broadband
    Replies: 3
    Last Post: 27-03-2006, 06:01 PM
  3. Replies: 9
    Last Post: 09-03-2006, 04:54 PM
  4. Remote Desktop help with IP address
    By Proplus in forum Networking and Broadband
    Replies: 3
    Last Post: 28-03-2004, 05:28 PM
  5. lan adsl router thingy
    By SilentDeath in forum Networking and Broadband
    Replies: 9
    Last Post: 23-08-2003, 07:24 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •