Cannot connect to one of three terminal servers following failed SP3 install

I have a machine that until a week ago was able to connect to any of the three terminal servers within our organisation.

Last week I attempted to install SP3 but the installation failed resulting in a BSOD.

After running a repair install and getting the machine back up and running I can no longer connect to the preferred Terminal Server (TSA for the sake of this description)

I can however connected to TSB and from there open another remote desktop connection to TSA. Everyone else on our network can connect to TSA without incident.

Following the logic of this I can assume that;

My user profile is ok as A) its crapping out immediately not at the point where I log in, just where I try and connect. B) I can log in with my credentials from TSB without incident.

The Remote Desktop Client on my PC is ok as it lets me connect to TSB without any problems.

The registry on TSA is OK as it lets other sers connect without incident.​

So where do I go now? I have checked groups etc on the domain controller and compared my settings & permissions to other machines on the network that can connect and all seems well.

I'm totally stuck and would greatly appreciate any help anyone can offer on this.

 

Not much logic behind my answer but I would attempt another sp3 install. I would download it manually and install it manually opposed to getting it through automatic updates. I deployed sp3 on hundreds of computers without much issue. Only time I ran into problems is when I installed it through automatic updates in which case it would freeze part way through installation and never fully install.

Let me know how it goes. That is odd though how you can connect to any other ts fine

 

Haven't had chance yet to try reinstalling SP3 but have somemore information/observations to add.

The exact message that reads when trying to connect an XP Pro machine to a Server 2003 Terminal Server using the Microsoft client is as follows;

"Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network and the try connecting again."

We double click on the Remote Desktop Connection icon, enter the address (IP or Name , neither works) then click Connect and this message appears. As messages go its about as helpful as just saying no.

I checked all sections of the event log for both the Terminal Server and the Local machine and nothing, nada, zip.