windows 10 PRO edition is not listening on port 3389 for RDP connections.

After those adjustments, please see if reboot helps

Are you trying to connect with a computer on the same network or outside the network (ie. over the internet).

If you right-click "This PC", choose Properties then click Remote Settings.  Make sure "Allow remote connections to this computer" is ticked.  If it isn't, tick it and restart the PC.

Hi, thank you for responses. Yes i have did the basics and had no luck.
My pcs are on the workgroup not domain. I am trying to access on LaN and next step will be connecting from outside.

What if you change the RDP port to a different number (eg. 3390) via the registry.  (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber).
Allow this port (in and out) in Windows Firewall > Advanced settings.
Restart the computer.

Try connecting to the PC from the other PC via LAN_IP:3390 (don't use the computer name)

Also check if Network Discovery is ON, that WORKGROUP is the same on both / all machines, and that the Network Card is set to Private (not Public).

Is your Router forwarding Port 3389 to the specific PC? That's needed.

Is remote administration enabled on the system, properties of computer, advanced system settings,
Check the firewall settings to make sure RDP are permitted through the type of network you have set in the network and Internet sharing center.
I.e. If the workgroup reflects that the system is on a public network, the majority of services on the system will be blocked by the firewall on the incoming side.

You should check if the port is really open with something listening on it, e.g. with
  netstat -an | find "3389"
in a cmd prompt. Because of your portqry and local telnet attempts I don't think so.

basics:
right click computer - properties - remote

in the lower part (remote desktop) either choose the second option or the third one. if the second one do not work, click the third option and in the select user type everyone and test.

Hi,

I have tried and checked what has suggested here but had no luck. Lastly tried it with port 3390 instead and created a port rule for it both for inbound and outbound but still cannot see port 3390 is listed when i do netstat -an

please see the firewall rule attached. any more ideas please?

it might be denied by GPO.

Machines are on workgroup and there is no domain gpo

What about network and Internet center, in which type of network, private/home, work, public is this system being reflected?

netstat -an | find ":3389"
Or test for 3390 and see if there is a listen live for either.

Can you confirm that the Remote Desktop service is actually running? Check in task manager - its startup type may be set to disabled.

@arnold    netstat -an | find ":3389"

returns an emty line not sure what that means?

@Perarduaadastra  services was running but was set to manual and I set it up to auto start.

thanks for responses. I am running out ideas?

Run this command:

netstat -a -p tcp

and wait a few seconds for it to complete. The list is organised by IP address and port number, so scroll up to the top and look for a line that reads:

TCP    0.0.0.0:3389    <name_of_your_computer>:0        LISTENING

If there is no such line then nothing is listening on that port, which means that either the service isn't running or that it's listening on a different port. When you changed the port to 3990, did you do this in decimal or hex? The edit window defaults to hex even though the port number is in decimal so it's easy to enter a decimal value in hex without realising it, in which case you would have told the RDP service to listen on port 13200 decimal! Likewise, if you repeated the error when changing it back to 3389 you would have told the service to listen on port 13193 decimal.
You don't say one way or the other in your posts, but when you change the RDP listening port in Windows you have to reboot the machine before the new setting takes effect.

@Perarduaadastra

run the command and I cannot see the line we are after

also, curent port number in registry is set to listen on 3390 and it is in Hex. format.

I changed it normal 3389 and rebooted the machine. I will run the same command again will post the result here.
thank you.

OK- this is very strange to me..

when I run this command netstat -a -p tcp  I had no port 3389 or 3390 ( manual change) was showing in the list.

I noticed from the GUI ( screenshots are attached) RDP is listening on different port.

I checked the registry and PortNumber is set to 3389 !  

when I do telnet localhost 13193 it returns no errors and logs in fine. how is this possible and where is this info saved in registry?
Capture.PNG
Capture2.PNG

This is exactly what was setup on the machine, great explanation. Thank you. It all works fine.