Hi.

I have a Terminal Services Server running on Windows 2003 Server Standard Edition.

Also, a worstation running Windows XP SP2 with last security patches and hotfixes installed, and using RDP client to connect to the TS Server.

When I turn on the workstation and login with an account with administrator's privilegies, I can connect with no problem to the TS Server.

If, after any amount of time has passed, I lock the workstation and come back a few hours later, when I try to connect to the TS, I get the TS Server's session window but with a black background and no login box is shown.

Nothing in the workstation's Event Log.

If I disconnect and try to connect again I get the same results.

Looking in the server's EVent Log I found, in the System Log, an event with the following:
Type: Error
Computer: <TS Server's name>
Source: TermDD
Event ID: 50
Description: The RDP protocol component WD detected an error
in the protocol stream and has disconnected the
client.

The most curious thing is that, if I wait about 15 minutes (more or less) I am able to connect again.

I tried changing the Encryption Level for the RDP-tcp connection (in Terminal Services Configuration -> Connections) from "Client Compatible" to "Low" but got the same results.

One more thing to consider about my configuration is that I'm connecting to this TS server through a VPN over the Internet. I seems that, for some reason, if I close the VPN and lock the computer (instead of loging off) and then unlock it and reopen the VPN, I have to wait about 15 minutes for my connections to work.

I have another TS Server also running Windows 2003 Server Std. Edition and have no problem at all to connect to it.

Any help with this would be greatly appreciated.