F5F Stay Refreshed Power Users Networks Problem with RDP forwarding on a Linux server.

Problem with RDP forwarding on a Linux server.

Problem with RDP forwarding on a Linux server.

Pages (2): 1 2 Next
D
DylanFett9
Member
62
11-09-2025, 12:01 PM
#1
Hey everyone, I'm trying to set up a RDC from my office to my home PC. I have a Tenda F3 router and used the port forwarding section to expose my IPv4 address on port 3389. That works fine for remote connections, but when I try connecting from another network using my public IP, I get an error. Am I making a mistake somewhere?
D
DylanFett9
11-09-2025, 12:01 PM #1

Hey everyone, I'm trying to set up a RDC from my office to my home PC. I have a Tenda F3 router and used the port forwarding section to expose my IPv4 address on port 3389. That works fine for remote connections, but when I try connecting from another network using my public IP, I get an error. Am I making a mistake somewhere?

O
ovcoming
Member
229
11-22-2025, 05:34 AM
#2
Google and Teamviewer provide methods to connect remotely without needing to open ports. Are there any policies in your office about using third-party software?
O
ovcoming
11-22-2025, 05:34 AM #2

Google and Teamviewer provide methods to connect remotely without needing to open ports. Are there any policies in your office about using third-party software?

K
Krisdamme135
Junior Member
41
11-22-2025, 05:43 AM
#3
Exactly what the issue is, before they decide to renew the team viewer subscription or whatever it is, I need to rely on this one.
K
Krisdamme135
11-22-2025, 05:43 AM #3

Exactly what the issue is, before they decide to renew the team viewer subscription or whatever it is, I need to rely on this one.

M
MechanoidBlue
Member
62
11-28-2025, 03:43 AM
#4
Which Windows version are you running? For Windows 10 Pro, enable RDP connections. Navigate to Control Panel ---> System. On the left, click Remote settings, then open the box at the bottom. Make sure the option says "Allow remote connections to this computer" is checked and the box next to it is unchecked. If RDP isn't available for Windows 10, use the guide for Windows 10 Pro instead.
M
MechanoidBlue
11-28-2025, 03:43 AM #4

Which Windows version are you running? For Windows 10 Pro, enable RDP connections. Navigate to Control Panel ---> System. On the left, click Remote settings, then open the box at the bottom. Make sure the option says "Allow remote connections to this computer" is checked and the box next to it is unchecked. If RDP isn't available for Windows 10, use the guide for Windows 10 Pro instead.

E
Estampy
Junior Member
49
12-02-2025, 07:52 PM
#5
I've already checked that. I'm using Windows Pro 10, and the online IP check shows port 3389 is closed, even though it's enabled in the router settings.
E
Estampy
12-02-2025, 07:52 PM #5

I've already checked that. I'm using Windows Pro 10, and the online IP check shows port 3389 is closed, even though it's enabled in the router settings.

P
P0ku7a
Junior Member
35
12-03-2025, 05:35 PM
#6
You specify the IP address or hostname when attempting to connect via RDP. It's important to note that RDP operates over UDP rather than TCP.
P
P0ku7a
12-03-2025, 05:35 PM #6

You specify the IP address or hostname when attempting to connect via RDP. It's important to note that RDP operates over UDP rather than TCP.

T
Takeo_Player
Member
177
12-03-2025, 08:50 PM
#7
Your public IP, along with your IP and port attempts, should match consistently.
T
Takeo_Player
12-03-2025, 08:50 PM #7

Your public IP, along with your IP and port attempts, should match consistently.

O
Olewww123
Senior Member
255
12-25-2025, 02:39 AM
#8
UDP is used for RDP. Verify your firewall on the target PC allows RDP traffic.
O
Olewww123
12-25-2025, 02:39 AM #8

UDP is used for RDP. Verify your firewall on the target PC allows RDP traffic.

C
chenglee1998
Member
147
12-25-2025, 06:58 AM
#9
Confirm the details are correct. Ensure inbound port 3389 is allowed in both Windows firewall and any relevant router firewall.
C
chenglee1998
12-25-2025, 06:58 AM #9

Confirm the details are correct. Ensure inbound port 3389 is allowed in both Windows firewall and any relevant router firewall.

D
dani97
Junior Member
2
12-25-2025, 08:47 AM
#10
Updated the setting entirely; fully disabled the firewall to avoid that problem. When I attempt to verify the port number on my IP, it shows Port 3389 is closed.
D
dani97
12-25-2025, 08:47 AM #10

Updated the setting entirely; fully disabled the firewall to avoid that problem. When I attempt to verify the port number on my IP, it shows Port 3389 is closed.

Pages (2): 1 2 Next