I just downloaded and installed Hyper-V Server 2019 from Microsoft Evaluation Center (version: 1809/10.0.17763.1).
Now I'm not able to connect to this machine (which I named hypervserver) using remote desktop.
Routing seems to be fine and pinging works as well, but the RDP port is not reachable:
>$ ping hypervserver
Reply from {IP}: bytes=32 time<1ms TTL=128
[...]
>$ telnet hypervserver 3389
Connecting To {IP}...Could not open connection to the host, on port 3389: Connect failed
No changes even after disabling firewalls and setting the network category of the used network profiles to Private.
I can see that I successfully enabled RDP, because sconfig.cmd says:
4) Configure Remote Management: Enabled
7) Remote Desktop: Enabled (all clients)
Registry keys look good as well:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnection = 0
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fEnableWinStation = 1
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber = 3389
Service seems to be running:
PS >$ Get-Service -Name termservice -ComputerName hypervserver
Status Name DisplayName
------ ---- -----------
Running termservice Remote Desktop Services
However, noone seems to be listening on port 3389:
>$ netstat -ano | findstr LISTEN | findstr :3389
>$
I have a standard setup with an ordinary (and single) ethernet network interface configured to get its IP using DHCP.
Neither rebooting nor restarting the service has helped.
Event log does not contain any errors.
What else could be the problem?
Shouldn't this work out of the box?
Best Answer
What about events in the Windows? Is there anything in Windows Event Manager? Maybe it is some sort of Port conflict inside the Windows. Run the following command - "netstat -an" and share the output. Also, you can change the decimal value of the RDP default port and try to log in.
Take a look at Microsoft forum https://social.technet.microsoft.com/Forums/windowsserver/en-US/c3cfc2df-fc29-4abc-acf1-01797f528333/port-3389-not-listening?forum=winserverTS
There are the problems with some MS driver:
"We opened a case with Microsoft on this issue and we determined that it was related to the following driver being disabled: remote desktop services security filter driver To check whether this enabled or disabled, open device manager and show hidden devices. We were not able to enable it, so we uninstalled it and rebooted. After rebooting we were able to telnet to the server on port 3389, but we were still not able to connect with remote desktop. As a last step, we set remote desktop security layer to “negotiate”. To do this, open the "remote desktop session host configuration" application in administrative tools and edit the properties of “rdp-tcp”. The setting can be found on the general tab. Hope this helps someone!"