Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Why Can't I RDP from outside my network?


  • Please log in to reply
4 replies to this topic

#1 gib65

gib65

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Local time:05:36 AM

Posted 05 March 2017 - 04:21 PM

Hello,
 
I have a router in my home network and it is setup to port forward RDP requests to my server. I'm able to remote desktop into my server from within my home network, but not outside. Whenever I tried to connect from outside, it tells me it cannot make the connection.
 
Internally, I connect using the name of my server. From outside, I have to use my WAN IP address, which I get from whatismyip.com.
 
Can anyone suggest what else besides the port forwarding (in the attached image) I can do to remote desktop from outside my home network?
 
Attached File  RDP port forwarding.png   29.59KB   0 downloads


BC AdBot (Login to Remove)

 


#2 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,082 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:10:36 AM

Posted 05 March 2017 - 05:40 PM

Hi,

 

RDP uses TCP not UDP! for safety you should use a different port for RDP instead of the default 3389.


• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#3 ItsAllGeekToMe

ItsAllGeekToMe

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:36 AM

Posted 06 March 2017 - 12:26 PM

The port forward should do it.  What make/model of firewall are you using?  You may have already did this, but I would double check that the server IP has not changed.  I would also check to make sure that the public IP has not changed.  If this is a residential setup, your public IP could possibly change periodically.  Some businesses can be like that too unless a static IP was ordered.



#4 toofarnorth

toofarnorth

  • Members
  • 391 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:36 AM

Posted 06 March 2017 - 04:11 PM

Hi,

 

RDP uses TCP not UDP! for safety you should use a different port for RDP instead of the default 3389.

+1 for the use of a different port

You will get hammered by people with no good intentions if you leave port 3389 open

This is an old post but still valid:
https://nakedsecurity.sophos.com/2012/09/07/microsoft-rdp-remote-desktop-protocol-or-routine-darkside-probe/

tfn



#5 gib65

gib65
  • Topic Starter

  • Members
  • 162 posts
  • OFFLINE
  •  
  • Local time:05:36 AM

Posted 06 March 2017 - 09:29 PM

Thanks for the advice everyone. TCP worked. I've changed the port # it connects on, at least for public.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users