Jump to content
Posted 27 February 2012 - 12:50 AM
Posted 27 February 2012 - 01:27 PM
Posted 28 February 2012 - 01:21 PM
Posted 04 March 2012 - 12:02 PM
Posted 28 November 2012 - 06:42 AM
Posted 01 December 2012 - 07:47 PM
In order to have remote desktop connection outside your network, you need to use remote support services such as logmeinrescue, gosupportnow, gotomypc etc. and connect over internet. Both the computers need to be on same network if you want to internally establish remote connection without using 3rd party remote services.
Posted 12 November 2013 - 11:18 AM
Your router must use
ip nat inside source static tcp 192.168.x.x 3389 123.250.x.x 3389 extendable
Starbucks must allow/open port 3389 in their router / Firewall
Also may you need to check your firewall setting to allow outside home network to connect to your system.
Posted 09 December 2013 - 10:03 PM
A shot in the dark here, you mentioned you used a computer on the internal network and it worked then went to Starbucks and it didn't. So you are using 2 separate computers? Is it possible that one has IE 9 (the one that connected) and the other has IE10 installed? Sometimes...I emphasize sometimes there are issues using remote desktop and being able to successfully connect when IE 10 is installed, though this should give you an error if this is the case
Posted 10 December 2013 - 02:11 AM
Second is the firewall on the server. If RDP is not enabled on both the incoming and outbound filters. ...
Technically the above is slightly incorrect. I'll come back to tthat in a mo....
Reading the thread, the obvious thing not attended to is the local Windows Firewall on the server (additionally there is no mention that the servers default gateway is set to the router, but I assume it is).
The correct firewall setting is "Remote Desktop (TCP-in)" "Enabled" for "ALL" profiles (set in "Windows firewall with Advanced Security" (wf.msc)
The slight issue with the original suggestion is that we are only worried about inbound (OK, allowing outbound isn't an issue, but it is not the subject of what we are trying to achieve. - I offten see the opposite [which is much more dangerous] - someone doing outbound access, hitting issues they do not understand and setting the firewall to allow inbound as well out of desparation - the blunderbus method of firewall configuratiion is a poor one!).
Additionally once you get it working, if you have the opportunity to set a differennt external port on your router port forwarding rule, try to use that (so the router listens on a differenf port - say 47816 or something like that , and forwards that to 3389 on the server.
There are miscreants to scan the internet for open RDP ports and try to log in. If not maybe change the administrator usernme on the server and definitely use a very strong password.
Posted 16 December 2013 - 09:31 PM
like x64 said, having an open port 3389 is dangerous and not to emntion you subject your self to token kidnapping which if i where to obtain would get acess with out authorization. Anyway who, all i will say is, no NOT have direct RDP access to a server, creat a free VPN (IPCop for instance with OpenVPN, make sure you enable GREPPTP(Port 47 on the router to point to red interface in IPCop) which acts as the gateway and proxy filter if need be.
0 members, 0 guests, 0 anonymous users