Term Serv remote control sessions fail

NT4 classic domain with 70+ W2K servers. We use mstsc.exe (Remote Desktop Connection) to remote connect to the servers and it works fine.

Last week we received a new server that was staged/built by another group of folks and sent here to run Spectrum. All seems well after some tweaking but from the time it arrived, we have been unable to establish a termserv connection. The error is pictured.

We do have connectivity since Ecora has no trouble pushing patches, Legatto has no trouble backing it up, etc.

The only significant event log error is

Some searching dug up Terminal Services Client Cannot Connect to a Server Running 128-bit Encryption that looked likely but setting the Remote Desktop Protocol (RDP) to medium and then to low didn't help.

I have no idea what the other server group did differently when building this server to cause the problem. I did check the server in Terminal Services Manager to make sure there weren't a couple of existing connections and there were not. Everything there looks fine. TermService is running normally and with the same settings as on all the working systems.

 

What OS is the terminal server? Im going to assume Win2k...

Have you tried whacking the certs?

 

2K Server it is.

The only one of those I found was Certificate and it is now toast with the server in the process of rebooting.

Thanks and I'll let you know how it works.

 

Eureka!!!

That worked. We are in business.

Thanks a bunch Ben.

 

Glad i could help.