Cannot terminal into a server after SP4 rollback

[Yaakov]

We installed SP4 on one of our terminal servers, there
were some issues with clipart files with one of our
clients so to make them happy we decided to remove SP4 and
roll back to SP3. When we removed SP4 the computer locked
and needed to be cold booted, when it came back online in
had SP2 installed. We reinstalled SP3 and now get the
error ( The client could not connect to the terminal
server. The server may be to busy. Please try contacting
it later ) Well this is all we get no matter what we do
nothing seems to give us access, any suggestions heard of
this before?

Thanks,
(e-mail address removed)

 

[Vera Noest [MVP]]

Is there anything in the EventLog?
Is the TS listening on port 3389?
Can you logon locally on the console? If so, what do you see in TS
Manager? Are there idle sessions waiting for a remote connection?
Have you tried to delete and then recreate the rdp-connection?
Some articles that might help:

187628 - Using Telnet to Test Port 3389 Functionality
http://support.microsoft.com/?kbid=187628

258021 - Event ID 52 When You Start Terminal Services
http://support.microsoft.com/?kbid=258021