Can no longer RDP to our SIMS Server

[mrwoberts]

So if we focus then on the changes that [were] made before the reboot

 

Were Windows updates applied?

Have any non-SIMS related changes been made to the server before this problem occurred - between this recent reboot and the previous reboot (possibly last month when if you applied Feb/March updates)

Edited April 18, 2019 by mrwoberts

[Steve21]

Is NLA enabled on the server RDP config? If so does it work if you disable that?

 

If you change the MSTSC advanced options on the client end (server auth) from warn me, to connect and don't warn does it still fail?

 

Steve

[fiza]

Is NLA enabled on the server RDP config? If so does it work if you disable that?

 

If you change the MSTSC advanced options on the client end (server auth) from warn me, to connect and don't warn does it still fail?

 

Steve

NLA is enabled. Still doesnt work if disabled.

Tried the advanced options with don't warn me etc but still fails.

[fiza]

As this is our SIMS server is it safe to remove it from the domain and rejoin? Hoping (clutching at straws) that it may resolve the issue.

[howartp]

Just beware of the SIMS Document Server, which uses c:\......\domain\internal\random\sets\of\letters.

 

Not sure if it "encrypts" (ish) with a GUID, or if re-joining same domain will generate same set of paths.

[fiza]

Just beware of the SIMS Document Server, which uses c:\......\domain\internal\random\sets\of\letters.

 

Not sure if it "encrypts" (ish) with a GUID, or if re-joining same domain will generate same set of paths.

 

Think I will leave it then. Don't want to cause any more issues. Staff are back in work on Tuesday so need SIMS working even if we can't remote on.

[fiza]

Does anyone have any other ideas please?

[howartp]

Look in Windows Update history.

 

It shows you date-order of what was installed.

 

Anything since last Monday, remove one-by-one and try again?

[fiza]

Just looking in the Event log and each time I try to rdp from another machine to the server I get an Audit Failure Event Id 5061. Any ideas what this could mean please?

 

Edited April 23, 2019 by fiza

[ThomL]

A quick google search leads to talks of corrupt registry entries, advice given to stop rds service then backup and delete keys followed by rds service restart to re-gen keys - HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

 

worth trying?

[fiza]

A quick google search leads to talks of corrupt registry entries, advice given to stop rds service then backup and delete keys followed by rds service restart to re-gen keys - HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations

 

worth trying?

 

Unfortunately I tried that already, no joy.

 

- - - Updated - - -

 

Look in Windows Update history.

 

It shows you date-order of what was installed.

 

Anything since last Monday, remove one-by-one and try again?

 

Nothing to cover period when it stopped working.

[skillkan]

It is likely you have run out of space on the local drive of the SIMS server. You can go to a file or domain server and in windows explorer type\\servername\c$ of the SIMS server. This should take you to the C drive, if it is not your C drive, could be D or E or another drive.

 

The path should look similar to this

 

E:\Program Files\Microsoft SQL Server\MSSQL13.SIMS2016\MSSQL\Backup

 

Most likely culprit are the .bak files that are created when you run a SIMS update, if the updates have been successful, then you don't need to keep these files. You have stated you have done an update and this may have used up the space on the drive.

 

I have had this problem a few times and once I have cleared the BAK files, its fine (To be safe, copy off the BAK files to an external drive only if you can get that far)

 

Delete the oldest BAK files first not the newer ones just to make sure you can then log on and the system does not freeze

 

Hope this helps

[fiza]

It is likely you have run out of space on the local drive of the SIMS server. You can go to a file or domain server and in windows explorer type\\servername\c$ of the SIMS server. This should take you to the C drive, if it is not your C drive, could be D or E or another drive.

 

The path should look similar to this

 

E:\Program Files\Microsoft SQL Server\MSSQL13.SIMS2016\MSSQL\Backup

 

Most likely culprit are the .bak files that are created when you run a SIMS update, if the updates have been successful, then you don't need to keep these files. You have stated you have done an update and this may have used up the space on the drive.

 

I have had this problem a few times and once I have cleared the BAK files, its fine (To be safe, copy off the BAK files to an external drive only if you can get that far)

 

Delete the oldest BAK files first not the newer ones just to make sure you can then log on and the system does not freeze

 

Hope this helps

 

Plenty of space on both C drive and the D drive which contains the SQL stuff.

[bald_pig]

This is the only other thing I can suggest to try is this:

 

When the Interwebs Really Let Me Down

[fiza]

This is the only other thing I can suggest to try is this:

 

When the Interwebs Really Let Me Down

 

That looks promising. Will try that when I am able to reboot the server.

[fiza]

This is the only other thing I can suggest to try is this:

 

When the Interwebs Really Let Me Down

 

That worked!

 

Thank you for finding that. I must have missed it in my searches.