F5F Stay Refreshed Power Users Networks Issue with RDP client outside network range

Issue with RDP client outside network range

Issue with RDP client outside network range

A
Agman10
Senior Member
690
12-23-2016, 11:55 PM
#1
You're facing an issue with accessing your home server from outside the network, specifically receiving an error code 0x00005f. It sounds like the problem might be related to port forwarding or network configuration. Double-check that your port forward rules are correctly set up for port 3389 and ensure your gateway connection is functioning properly. Also, verify that your Android tablet is using the correct IP address and that the firewall on your device isn't blocking the connection. If needed, try restarting both your server and tablet to clear any temporary glitches.
A
Agman10
12-23-2016, 11:55 PM #1

You're facing an issue with accessing your home server from outside the network, specifically receiving an error code 0x00005f. It sounds like the problem might be related to port forwarding or network configuration. Double-check that your port forward rules are correctly set up for port 3389 and ensure your gateway connection is functioning properly. Also, verify that your Android tablet is using the correct IP address and that the firewall on your device isn't blocking the connection. If needed, try restarting both your server and tablet to clear any temporary glitches.

I
IMayBeDead
Senior Member
696
12-24-2016, 10:29 AM
#2
Begin by not forwarding any of the most exposed and frequently targeted ports online. Then verify whether your setup is protected by CG-NAT.
I
IMayBeDead
12-24-2016, 10:29 AM #2

Begin by not forwarding any of the most exposed and frequently targeted ports online. Then verify whether your setup is protected by CG-NAT.

S
SportsBoy12
Member
59
12-25-2016, 04:22 PM
#3
It's likely your public IP isn't accurate or your ISP is blocking it. As noted by Luricks, exposing ports 3389 openly is a serious issue. It usually requires a few minutes for attackers to locate it and launch attacks. Even then, they might be focused on outdated log4j vulnerabilities. If you must proceed, turn off admin RDP access and limit login to one user with a very long, complicated name and password. 3389 can also be forwarded to a less obvious port. I'm not promoting this, but it's better to have alternatives than to keep arguing.
S
SportsBoy12
12-25-2016, 04:22 PM #3

It's likely your public IP isn't accurate or your ISP is blocking it. As noted by Luricks, exposing ports 3389 openly is a serious issue. It usually requires a few minutes for attackers to locate it and launch attacks. Even then, they might be focused on outdated log4j vulnerabilities. If you must proceed, turn off admin RDP access and limit login to one user with a very long, complicated name and password. 3389 can also be forwarded to a less obvious port. I'm not promoting this, but it's better to have alternatives than to keep arguing.

I
Im_a_potato
Junior Member
23
01-13-2017, 05:20 AM
#4
I’d support discussing RPC, yet avoid RDP. Before making RDP accessible over the internet, implement a password lockout system to deter attacks—such as locking out after 30 minutes of ten failed attempts within ten minutes. Restrict RDP access only to accounts with robust passwords; otherwise, it shouldn’t be considered suspicious. For potential issues, verify the Windows Firewall settings so the RDP rule permits edge traffic (this is usually the main reason LAN works but not WAN).
I
Im_a_potato
01-13-2017, 05:20 AM #4

I’d support discussing RPC, yet avoid RDP. Before making RDP accessible over the internet, implement a password lockout system to deter attacks—such as locking out after 30 minutes of ten failed attempts within ten minutes. Restrict RDP access only to accounts with robust passwords; otherwise, it shouldn’t be considered suspicious. For potential issues, verify the Windows Firewall settings so the RDP rule permits edge traffic (this is usually the main reason LAN works but not WAN).