Active3 months ago
![Tcp Tcp](/uploads/1/3/4/0/134037703/288040521.jpg)
As you remember, if you try to connect to a Windows 10 computer using RDP, the session of a user working locally is knocked out (even if you enable multiple concurrent RDP sessions in Windows 10). However, you can connect to a console user session directly without locking it.
- Security through Obscurity: Changing the Default RDP Port. Then right-click on “Inbound Rules” and choose “New Rule.” The “New Inbound Rule Wizard” will pop up, select Port and click next. On the next screen, make sure TCP is selected and then enter the port number you chose earlier, and then click next.
- This works on our windows 10 machines: HKEYLOCALMACHINE SYSTEM CurrentControlSet Control TerminalServer WinStations RDP-Tcp. Change: SecurityLayer From: 2 To: 0. Reboot (Should only use for internal / segregated machines for security reasons).
- Since updating to Windows 10 build 1809 on both RDP client and server, I'm seeing a black screen after the initial logon sequence completes when connecting over a link with a smaller-than-ethernet MTU, and when UDP transport is enabled. These scenarios work as expected: LAN link, MTU 1500 bytes, both TCP and UDP transports enabled.
I have two computers that came with Windows 8.1. I recently upgraded them to Windows 10. I've been trying to configure the machines for remote access but am having limited/no luck.
The RDP connection fails when specifying either the hostname or the IP of the target machine.
I have tried the following to attempt to solve the issue:
- Checked that the target PC has Remote Desktop enabled. The
Allow this computer to be controlled remotely
checkbox underThis PC
->Properties
->Remote Settings
->Advanced
is indeed checked. - Disabled Windows Firewall in case this is causing connection issues.
- Use a wired, rather than wireless, connection.
- Verified that both machines could ping each other successfully (they could).
- Verified that Remote Desktop is attempting to listen on port 3389 by checking the registry value at
ComputerHKLMSystemCurrentControlSetControlTerminal ServerWinStationsRDP-TCPPortNumber
(this value is indeed correct). As it turns out, Remote Desktop is actually NOT listening on this port (or apparently any port). I was able to find this information by runningnetstat -a | findstr 3389
. - Toggling the Remote Desktop checkbox (see above) and then restarting, per a suggestion I found using Google. I tried this in various ways, including:
- Disabling Remote Desktop and then restarting. Then enabling Remote Desktop and then restarting.
- Disabling Remote Desktop, then enabling it, then restarting.None of these cause Remote Desktop to start listening on this port.
- Putting the two computers in a homegroup together, per another suggestion. After doing this, the two computers share files and other resources.
How can I fix this issue with Remote Desktop and allow the target machine to be connected to remotely?
As you can see, I've tried a lot of things to solve this issue. Hopefully I've missed something that somebody can spot!
Ben N31.6k1313 gold badges108108 silver badges153153 bronze badges
Beta033Beta033
migrated from serverfault.comAug 15 '15 at 3:28
This question came from our site for system and network administrators.
2 Answers
Did you add your user to the remote user list?
This PC -> Properties -> Remote Settings -> Advanced -> Select Users ... And select the users.
Install Rdp On Windows 10
Also, Did you allow the incoming connections on port 3389 TCP?
Control Panel -> Windows Firewall -> Advanced settings -> Inbound Rules -> New Rule ... And follow the wizard to add the port.
Roy CalderonRoy Calderon
You can telnet the PC to check whether RDP port is opened.
Telnet tserv
Rdp Host Windows 10
It should make communication and get a response.
Source - https://support.microsoft.com/en-hk/help/187628/using-telnet-to-test-port-3389-functionality
Also, a few points to consider.1) Network Level Authentication2) Firewall settings or personal firewall and AV settings - that might block incoming RDP requests.3) User/Group permission4) Check the remote desktop service
More detailed information available here in fixing RDP issues in Windows 10.
DineshDinesh