asked on

Remote Desktop Port Forwarding and Opening

Hello,

I am having trouble getting some ports open on my server. I have done a port scan and it keeps timing out on port 3392. I have opened the port on the windows firewall on the inbound settings, as well as our main firewall that we have.

I am using port 3392 because I have a domain and I getting people to access their work stations remotely via RDP. I have two users setup currently from a previous configuration that another tech implemented.

Where else would I have to add port 3392 to get this working and open on the server or network.

Thanks in advance!

jprlopes

Normally, RDP uses port 3389.

Maybe you have another setup you need to do in your router?
Or the only firewall you have its the one you configured already?

clockwatcher

RDP typically runs over 3389. Have you changed the port to 3392?

clockwatcher

Sorry... didn't see jprlopes comment when I posted.

Directtechit

ASKER

I know remote desktop normally uses port 3389. I have different ports being directed to different computers on the network.

Example: I have one port I have on the firewall is 3390, and that is going to 192.168.1.21
Another computer is on port 3391, and that is going to 192.168.1.22

These are already setup and are working. I am trying to setup Port 3392 on the windows firewall for 192.168.1.23 to use and I can't get port 3392 to open all the way on the server and on the firewall. I do a port scan and it still isn't saying it isn't open, or it will time out.

Thanks in advance!

jprlopes

Have you changed the default RDP port in Registry machine, from default 3389 to 3392 port?

By default, all clients are listening RDP from 3389.

In registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber

Change from 3389 to 3392.

Directtechit

ASKER

I have already done that. It still isn't connecting properly at the moment. For some reason the computer isn't accepting that port and I've changed the listening port already.

I have changed the listening port from 3389 to 3392

Even though I have gone through the windows firewall and opened up the ports as well. It still isn't working right.

Any other suggestions?

Directtechit

ASKER

Would anyone think that it is AVG possibly blocking this from happening?

jprlopes

Could be, but normally he dont.

Directtechit

ASKER

Is there a reason why the computers listening port wouldn't change or register?

Thanks again

jprlopes

But the Registry made in port number mantains?
Or changed to 3389 again, after you changed to 3392?

ASKER CERTIFIED SOLUTION

jprlopes

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Directtechit

ASKER

That is the idea of what I am trying to do. I appreciate all the comments guys.

I have an idea, let's start from the beginning. The port 3392 isn't open on my server. I have tried to open it many times, but it is not opening properly. Any ideas?