![]() ![]() Run the following command - "netstat -an" and share the output. What about events in the Windows? Is there anything in Windows Event Manager? Maybe it is some sort of Port conflict inside the Windows. Neither rebooting nor restarting the service has helped. ![]() I have a standard setup with an ordinary (and single) ethernet network interface configured to get its IP using DHCP. However, noone seems to be listening on port 3389: >$ netstat -ano | findstr LISTEN | findstr :3389 Running termservice Remote Desktop Services Service seems to be running: PS >$ Get-Service -Name termservice -ComputerName hypervserver HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber = 3389 HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fEnableWinStation = 1 Registry keys look good as well: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnection = 0 I can see that I successfully enabled RDP, because sconfig.cmd says: 4) Configure Remote Management: Enabled No changes even after disabling firewalls and setting the network category of the used network profiles to Private. Could not open connection to the host, on port 3389: Connect failed ![]() Routing seems to be fine and pinging works as well, but the RDP port is not reachable: >$ ping hypervserver Now I'm not able to connect to this machine (which I named hypervserver) using remote desktop. Sort of out of ideas at this point, I'll continue to search around and see if anyone else has any ideas.I just downloaded and installed Hyper-V Server 2019 from Microsoft Evaluation Center (version: 1809/3.1). I experience this issue less frequently on other servers, generally I just reboot them to fix this short term. One of my co-workers figured out you can restart the server from the "Server Manager" on another system, doesn't really fix the issue though. I have a monitoring product running against the server, sometimes it stops reporting when the server becomes unavaliable, other times it's keeps reporting mostly idle numbers (CPU under 10%, plenty of memory, no super heavy HD usage). I enabled the local admin account on the server so I can connect to it without running against my centralized AD server, that doesn't work either, still get the black screen of death. ![]() Ok I'm making progress, remote straight up freezes when I try to make a remote connection to the system that is locked up, the following command(powershell) just never completes: $session = New-PSSession -ComputerName DXYZServerNameHere I've enabled remote powershell and can use that even when I can't RDP, I will gather performance metrics and attach to this ticket. The issue got significantly worse and developed into a situation where I was being booted out of RDP every 15 minutes and needed to Force Stop the instance constantly, I replaced the server with a new one using the old data drives(but a new C drive) and still experience this issue on my new server every other day. Has anyone experience this sort of issue before, if so what solution did you come to? Update 1 I'm not sure how one can identify the root cause of this issue. I do see these sort of messages in the system log:ĭon't really tell me allot of than my server is "broken". I can still reboot the box via AWS but it'll just do the same thing the next night, the event log doesn't contain anything that indicates what is occurring on this server. (SQL Server) Still able to connect but is experiencing various issues related to SQL Agent In fact if you attempt to reboot ANY service on that box remotely is get's stuck in the "Starting." state. Can't restart the RDP service (remotely) because the "Remote Desktop Services UserMode Port Redirector" service is stuck in a "Stopping." state and you get the following error when you attempt it:Įrror 1061: The service cannot accept control messages at this time.Ĭan't use " Invoke-Command" due to security restrictions.Get-Process : Couldn't connect to remote machine. Can't kill processes with "Stop-Process", "Get-Process" returns error: I have a development box that is (nearly every night) experiencing the same symptoms:Ĭan't RDP due to the "Black Screen of Death"Ĭan't issue remote powershell commands because the "Remote Registry" service is stuck in a "Starting." state. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |