Home

Remote desktop to Hyper-V Server 17744 host

%3CLINGO-SUB%20id%3D%22lingo-sub-255278%22%20slang%3D%22en-US%22%3ERemote%20desktop%20to%20Hyper-V%20Server%2017744%20host%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-255278%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20cannot%20connect%20with%20remote%20desktop%20to%20Hyper-V%20Server%2017744%20host.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20enabled%20Remote%20Desktop%20with%20sconfig.%20I%20did%20check%20that%20TermService%20service%20is%20running.%3C%2FP%3E%3CP%3EHowever%20the%20netstat%20-a%20and%20%3CFONT%3EGet-NetTCPConnection%3C%2FFONT%3E%20show%20nothing%20listening%20on%20port%203389.%3C%2FP%3E%3CP%3EI%20have%20tested%20with%20firewall%20disabled%2C%26nbsp%3Bother%20services%20and%20connections%20do%20work%20(icmp%20ping%2C%20PowerShell%20remoting%20etc)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-255278%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267822%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20desktop%20to%20Hyper-V%20Server%2017744%20host%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267822%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Solution%20is%3A%20Windows%20Admin%20Center%2C%20Select%20powershell%2C%3C%2FP%3E%3CP%3ENow%20you%20are%20not%20able%20to%20run%20sconfig%20but%20configure%20your%202019%20Hyper-V%20box%20with%20powershell%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20use%20ALL%20the%20needed%20powershell%20commands%20you%20need%26nbsp%3B%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20solved%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266862%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20desktop%20to%20Hyper-V%20Server%2017744%20host%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266862%22%20slang%3D%22en-US%22%3E%3CP%3ECleaned%20HDD%20-%26gt%3B%20Installed%20Server%202019%20Standard%20edition%20-%26gt%3B%20RDP%20is%20working%20!!!%3C%2FP%3E%3CP%3ECleaned%20HDD%20-%26gt%3B%20Installed%20Server%202019%20Hyper-V%20edition%20build%2017744%20-%26gt%3B%20again%20no%20RDP%20port%20listening%26nbsp%3B%40%203389.%3C%2FP%3E%3CP%3EI%20can%20manage%20the%20server%20via%20Admin%20Center%20but%20I%20am%20not%20able%20to%20access%20%22console%22%20via%20RDP%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20Idea%20what%20to%20do%20now%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266471%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20desktop%20to%20Hyper-V%20Server%2017744%20host%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266471%22%20slang%3D%22en-US%22%3E%3CP%3Etested%20-%26gt%3B%20netstat%20-%20ano%26nbsp%3B%20%26nbsp%3B-%26gt%3B%20no%20RDP%20port%203389%20is%20listening%20%3F%3F%3F%3C%2FP%3E%3CP%3EDisabled%20FW%20-%26gt%3B%20same%20issue%20-%26gt%3B%20no%20port%20is%20listening%20on%203389%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChecked%20in%20registry%20-%20change%20port%203389%20into%203390%20-%26gt%3B%20same%20issue%20-%26gt%3B%20no%20port%20listening%20on%20port%203390%3C%2FP%3E%3CP%3EServer%20coldboot%20-%26gt%3B%20same%20issue%20...%20Server%20warmboot%20-%26gt%3B%20same%20issue.%3C%2FP%3E%3CP%3EPing%20is%20working%20...%26nbsp%3B%20%26nbsp%3BI%20can%20manage%20the%20system%20with%20Windows%20Admin%20Center%20build%201809%20!%3C%2FP%3E%3CP%3EChanged%20port%20back%20to%203389%20-%26gt%3B%20server%20reboot%20...%3C%2FP%3E%3CP%3ERemote%20desktop%20via%20Admin%20Center%20-%26gt%3B%20Not%20working%20%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-265914%22%20slang%3D%22en-US%22%3ERe%3A%20Remote%20desktop%20to%20Hyper-V%20Server%2017744%20host%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-265914%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20same%20issue.%3C%2FP%3E%3CP%3EFirst%20installed%20Hyper-V%202012-R2%26nbsp%3B%20%26nbsp%3B..%20working.%26nbsp%3B%20Tried%20to%20do%20in-place%20upgrade%20to%20Server%202019%20..%20failed%20..%20license%20issue%20%3F%3F%3C%2FP%3E%3CP%3ECleaned%20HDD%20and%20re-installed%20Hyper-V%202019%26nbsp%3Bon%20empty%20disk%20..%20ready%20..%20reconfigured%20settings%20...%3C%2FP%3E%3CP%3EI%20am%20not%20able%20to%20RDP%20to%20server%20%3F%3F%26nbsp%3B%20%26nbsp%3BNo%20idea%20why%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E
Petteri Stenius
Senior Member

Hello,

 

I cannot connect with remote desktop to Hyper-V Server 17744 host.

 

I have enabled Remote Desktop with sconfig. I did check that TermService service is running.

However the netstat -a and Get-NetTCPConnection show nothing listening on port 3389.

I have tested with firewall disabled, other services and connections do work (icmp ping, PowerShell remoting etc)

 

Thank you!

4 Replies

I have same issue.

First installed Hyper-V 2012-R2   .. working.  Tried to do in-place upgrade to Server 2019 .. failed .. license issue ??

Cleaned HDD and re-installed Hyper-V 2019 on empty disk .. ready .. reconfigured settings ...

I am not able to RDP to server ??   No idea why ...

tested -> netstat - ano   -> no RDP port 3389 is listening ???

Disabled FW -> same issue -> no port is listening on 3389

 

Checked in registry - change port 3389 into 3390 -> same issue -> no port listening on port 3390

Server coldboot -> same issue ... Server warmboot -> same issue.

Ping is working ...   I can manage the system with Windows Admin Center build 1809 !

Changed port back to 3389 -> server reboot ...

Remote desktop via Admin Center -> Not working ??

Cleaned HDD -> Installed Server 2019 Standard edition -> RDP is working !!!

Cleaned HDD -> Installed Server 2019 Hyper-V edition build 17744 -> again no RDP port listening @ 3389.

I can manage the server via Admin Center but I am not able to access "console" via RDP

 

No Idea what to do now ?

 

The Solution is: Windows Admin Center, Select powershell,

Now you are not able to run sconfig but configure your 2019 Hyper-V box with powershell :)

 

Also use ALL the needed powershell commands you need  :)

 

Problem solved :)

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
201 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies