Can no longer RDP to our SIMS Server

[fiza]

Just tried to RDP from my desktop to our SIMS server and I get "This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator"

 

Both technician machines have this issue. Nothing appears to be wrong with the SIMS Server as it is a VM and I can get to it via the Host. I have even rebooted it but still cannot get remote access.

 

I am wondering if this could be a Windows Update that has caused this? Having said that, I can remote onto other servers just fine.

 

Any ideas please?

 

edit: This is from Windows 7 desktop to Server 2012 R2

Edited April 17, 2019 by fiza

[Steve21]

How long ago was it last updated? There were some patches that broke RDP but that was like last year the ones I last remember anyway.

 

Can you remote to it from another Server OS? (Wasn't sure if you meant RDP from the HOST or like local access) As it was only clients that got affected by the patch I'm referring to

 

Steve

[Shadow_Walker]

Can you remote to it via the ip address?

[Reboot_IT]

Check the Windows Firewall is disabled.

[fiza]

How long ago was it last updated? There were some patches that broke RDP but that was like last year the ones I last remember anyway.

 

Can you remote to it from another Server OS? (Wasn't sure if you meant RDP from the HOST or like local access) As it was only clients that got affected by the patch I'm referring to

 

Steve

Regularly updated. I cannot remote to it from another server either.

Can you remote to it via the ip address?

Nope.

Check the Windows Firewall is disabled.

Disabled

[mrwoberts]

Can a Windows 10 client connect to the server?

 

From the affected server, via the VM host connection, what results do you get when you issue this command (from the cmd prompt).

netstat -a | find "3389"

 

EDIT: Also, just double check the network on the affected server is domain, assuming it's joined to your domain, otherwise it should be private

Powershell

Get-NetConnectionProfile

Edited April 17, 2019 by mrwoberts

[glen_j]

it could be the oracle remediation issue, have a look at this https://4sysops.com/archives/rdp-authentication-error-due-to-the-credssp-encryption-oracle-remediation-error

[fiza]

it could be the oracle remediation issue, have a look at this https://4sysops.com/archives/rdp-authentication-error-due-to-the-credssp-encryption-oracle-remediation-error

Thanks but it's not the CredSSP issue. All updates on the server are upto date.

[caffrey]

Are all the VMs on the host affected ?

[fiza]

Are all the VMs on the host affected ?

Not sure, will check tomorrow.

[fiza]

Can a Windows 10 client connect to the server?

 

From the affected server, via the VM host connection, what results do you get when you issue this command (from the cmd prompt).

netstat -a | find "3389"

 

EDIT: Also, just double check the network on the affected server is domain, assuming it's joined to your domain, otherwise it should be private

Powershell

Get-NetConnectionProfile

 

For the first test I can see the server is listening on 3389

 

For the second test I get "Provider Load Failure"

 

What does that mean please?

 

- - - Updated - - -

 

Are all the VMs on the host affected ?

No other VMs connect fine remotely.

[Sylv3r]

I take it Remote Desktop is still enabled on the server itself? i.e. remote connections are still enabled?

 

https://support.honeywellaidc.com/s/article/How-to-enable-Remote-Desktop-on-Windows-Server-2012-R2

[fiza]

I take it Remote Desktop is still enabled on the server itself? i.e. remote connections are still enabled?

 

https://support.honeywellaidc.com/s/article/How-to-enable-Remote-Desktop-on-Windows-Server-2012-R2

Yes it is, I even disabled it and re-enabled it. No change.

[mrwoberts]

For the first test I can see the server is listening on 3389

 

For the second test I get "Provider Load Failure"

 

What does that mean please?

 

You need to run the (native) 64 bit version of Powershell, not the Powershell (x86).

[fiza]

You need to run the (native) 64 bit version of Powershell, not the Powershell (x86).

 

Ok, ran that just now ;

 

[mrwoberts]

Looks good.

 

Can you just confirm whether a Windows 10 PC is able to RDP into that server?

 

Also, can you see if the 3389 connection is 'connectable', using this Powershell script (.PS1) from an affected client PC

 

$Connection = New-Object Net.Sockets.TcpClient

try {

   $Connection.Connect("localhost",3389)

   if ($Connection.Connected) {

       $Response = "Open"
       $Connection.Close()
   }
}

catch [system.Management.Automation.MethodInvocationException] {

   $Response = "Closed / Filtered"
}

Write-Host $Response

$Connection = $null

 

And can you post the output of these two Powershell commands

Get-ItemProperty 'HKLM:SYSTEM\CurrentControlSet\Control\Terminal Server'

and

Get-ItemProperty 'HKLM:SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' | Select-Object PortNumber

Edited April 18, 2019 by mrwoberts

[mrwoberts]

Actually, this looks like a simpler way to test a remote connection

 

Powershell

 Test-NetConnection -ComputerName "fqdn_of_your_sims_server" -Port 3389

[fiza]

Looks good.

 

Can you just confirm whether a Windows 10 PC is able to RDP into that server?

 

Also, can you see if the 3389 connection is 'connectable', using this Powershell script (.PS1) from an affected client PC

 

I have run the first script from an affected machine. I get the result "open"

 

From where should I run the 2nd and 3rd commands? From an affected machine or the server?

 

If I try to connect from a Windows 10 machine it still fails but I get a different message " An Internal Error has occurred"

[mrwoberts]

2nd and 3rd command from the SIMS server

[fiza]

2nd and 3rd command from the SIMS server

 

2nd Command result

 

 

3rd command result

 

[fiza]

Just spoken to our SIMS Support unit and they were the last ones to remote in on Monday to do the SIMS Spring Update. They said they had to reboot the server and then apply additional SIMS patches/upload reports. They did this successfully. Today they are unable to remote in either.

[fiza]

Just noticed that in my original post I said it was a 2012 R2 server. Its actually 2016.

[fiza]

Our SIMS Support Unit also use Dameware RDP and they are able to remote in using that over the VPN but the MS RDP client does not work.

[mrwoberts]

When you say you're trying to RDP from desktop to server, are you using the Dameware software, or the Microsoft RDC client?

I don't know anything about the Dameware software, but could we perhaps take that out of the equation for the minute - temporarily remove it from the SIMS server ....

[fiza]

When you say you're trying to RDP from desktop to server, are you using the Dameware software, or the Microsoft RDC client?

I don't know anything about the Dameware software, but could we perhaps take that out of the equation for the minute - temporarily remove it from the SIMS server ....

 

For the SIMS Unit to connect : This is the set up. We have Cisco AnyConnect as our VPN software. They make a connection using that to our Firewall and then use an RDP client to make the connection to the SIMS Server via the VPN. If they use the MS RDP client then they get the same error as us. If they use the DameWare RDP client then they can successfully connect.

 

We only use the MS RDP client and we cannot connect.

 

We dont have any Dameware software installed on the server. It is purely an RDP client the SIMS Unit use to connect.