T
thatotherguy
Guest
We've got this problem with some of our thin clients getting bumped off the
server with the message "Because of a protocol error, this seesion will be
disconnected. Please try connecting again" after about 2 or 3 minutes of
inactivity from the user, starting about a month ago.
I thought it might have been packets being dropped, and after harassing our
ISP, and going through hundreds and hundreds of traceroute logs, its not
that. I have found a potential fix at
http://support.microsoft.com/kb/824683, but we don't have access to Platform
Builder, so it's not much use to us, plus they all just started dropping off
at the same time, which is the real puzzle.
To make matters even more confusing, it only affects the TC's running
Windows CE .NET 4.1 - the Windows CE 5 (I think, they look like XP) Embedded
thin clients and the workstations are fine.
After a bunch of Google searching, the only other thing that pops up is the
visual style on the server, but thats been set to Windows Classic through the
control panel initally, then through GPO ever since Windows Server 2003 was
installed.
Any ideas?
Cheers,
Jeff
server with the message "Because of a protocol error, this seesion will be
disconnected. Please try connecting again" after about 2 or 3 minutes of
inactivity from the user, starting about a month ago.
I thought it might have been packets being dropped, and after harassing our
ISP, and going through hundreds and hundreds of traceroute logs, its not
that. I have found a potential fix at
http://support.microsoft.com/kb/824683, but we don't have access to Platform
Builder, so it's not much use to us, plus they all just started dropping off
at the same time, which is the real puzzle.
To make matters even more confusing, it only affects the TC's running
Windows CE .NET 4.1 - the Windows CE 5 (I think, they look like XP) Embedded
thin clients and the workstations are fine.
After a bunch of Google searching, the only other thing that pops up is the
visual style on the server, but thats been set to Windows Classic through the
control panel initally, then through GPO ever since Windows Server 2003 was
installed.
Any ideas?
Cheers,
Jeff