Helpful Links

Firewall Pinhole created - but no access via RDP?

Contributor

Firewall Pinhole created - but no access via RDP?

I'm 3 days into my new Uverse service. One of my primary needs is to be able to remote into my home PC from the road.

 

This was possible with my old ADSL service from AT&T but for all I have in me, I can't seem to make it happen with the new 3800hgv gateway. I have created a "pinhole" successfully (per the firewall page on the gateway).

 

Is TCP 3389 and/or Remote Desktop blocked at the ISP-level on Uverse? If so, how can I have this - and any other blocked ports - opened up?

 

Thanks!

 

Cheers,

Mike

 

Tags (1)
1,761 Views
Message 1 of 3
Anonymous
N/A

Re: Firewall Pinhole created - but no access via RDP?

Only thing that is blocked is Port 25. I use Teamviewer to connect via remotely to my machines, and those I support, since it is a lot more secure than RDP.
Message 2 of 3
Expert

Re: Firewall Pinhole created - but no access via RDP?

RDP (TCP/3389) should not be blocked. Check your firewall settings carefully and make sure you're remoting into the correct outside IP address from an outside source.

You can also investigate alternatives to RDP if you want, I personally use LogMeIn.

Older versions of RDP such as those that shipped with Windows 2000, Windows XP, and Windows 2003 are indeed less secure than some other methods. However, RDP v6 which shipped with Windows Vista, 7, and Server 2008 and 2008R2 is much more secure.
Tags (1)
Message 3 of 3
Share this topic
Announcements

Welcome to the internet boards! Check out our troubleshooting articles below and don’t forget to search the forums - your question may have been answered already!

Service acting up? Click here to troubleshoot now!

For DSL related issues. We highly recommend chatting with our teams to address this as quickly as possible.

Additional Support