TS problems

[Ian]

Hello,

I have a few customers that are running a terminal server
session to run an application. On a couple of the servers
we have some files that keep getting corrupted and causing
that part of the application to stop working. We setup the
user's session to launch the application automatically and
log them in. When the application locks up, it throws them
out of the session and I get know error in the event
viewer on the server nor does the application generate any
errors. The application vendor said it was TS
disconnecting them and causing the problem so I decided at
one company to have the user log into the servers desktop
and run the application from there. When the problem
happened again it closed the application and left the user
on the servers desktop. This leads me to believe that TS
is not causing the problem and that something else might
be. The application vendor went and setup one customer
with a mapped drive and ran the application without TS's
(through a mapped drive) and they have not had the problem
since.
The server's are Windows 2000 and the clients very from
Windows 2000 to Windows XP with all different levels of
the RDP client. I will say that the clients at one site
are the same but may differ from site to site. Most of the
servers are at SP4 with most of the updates, but we do
have one that is still at SP1 and is having the problem as
well. We also have some customers that are not having any
problems at all.
Has anyone seen anything like this before or have any
other ideas for trouble shooting?

Thanks for any input,

Ian

 

[Guest]

I've had similar problems, Ian, and was hoping to find some help on Microsoft's site. I'm sorry this doesn't answer your question, but hopefully my adding to it will get both of us some answers. =

I have users using an app, and intermittently the following error occurs

"Because of a protocol error, this session will be disconnected. Please try connecting to the remote user again.

Upon reconnecting to the server immediately, you reach the same session, but get the same error and are immediately dumped again. The client must wait until their session is reset by the server until they can reconnect. The The server is a Windows 2000 Server, sp4. Clients are a mixture of 2000 and XP clients running Remote Desktop.

I've checked logs, and no errors are posted, no spike in the usage of resources occur. I'm at a loss to explain why this is happening.

Has anyone seen this error, and if so, what is it typically tied to

Any help is greatly appreciate

Ada

 

[Vera Noest [MVP]]

There is a fix for this problem, but it only applies to clients
running CE:

824683 - FIX: A Terminal Server Client Session Quits Unexpectedly
Because of a Protocol Error
http://support.microsoft.com/?kbid=824683

However, this KB articles last line says:

"The error that is described in the "Symptoms" section can also
occur if malformed remote desktop protocol (RDP) packets are
received by the client."

I would try to delete the rdp-tcp connection and recreate it, to
see if that helps. Are you running the latest rdp client (version
5.2.3790)? Downloadable from:

http://www.microsoft.com/downloads/details.aspx?FamilyID=a8255ffc-
4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en