[THIN] Re: WYSE "Protocol Driver Error"
- From: "King, Jesse" <JKing@xxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 13 Jun 2005 09:21:53 -0400
In the past when I have seen this on our older Wyse units, it was a DHCP
problem where the thin client was not getting an IP address.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Luchette, Jon
Sent: Monday, June 13, 2005 9:19 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WYSE "Protocol Driver Error"
it occurs when these units are in the process of making a connection to
the published desktop, it is not every time but it is happening more and
more often. they disconnect after an idle timeout of 2 hours, and then
they are setup on the terminal to auto start the connection. so it is
after they logoff, when they start to make the connection to the
published desktop that they get this error message. usually just a
plain old reboot on the terminal will clear the error message
temporarily.
_______________________________________________
Jon Luchette
Emerson Hospital
Technology Specialist III
Work: 978-287-3369
Cell: 978-360-1379
jluchette@xxxxxxxxxxxxxxx
_______________________________________________
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Jeff Durbin
Sent: Monday, June 13, 2005 9:07 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: WYSE "Protocol Driver Error"
When does the message occur? If it's at startup, maybe it's a
speed/duplex negotiation issue.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Luchette, Jon
Sent: Monday, June 13, 2005 5:54 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] WYSE "Protocol Driver Error"
Hello,
We have been having an issue for quite some time now with our WYSE thin
clients getting this "Protocol Driver Error" message far too often. All
that WYSE has come up with to troubleshoot is to try and reset the
terminal to factory defaults to clear out the flash and see if it
happens again, but that is not working at all. When these units get
this error message, they are not pingable on the network. They are
running CE.net 4.2, and we are running MF PS 3.0, on 6 win 2k sp4
servers, dual PIII procs, w/ 4 GB Ram. These clients automatically
logon to a locked down Published Desktop.
Has anyone else seen this Protocol Driver Error message on WYSE thin
clients before and come up with a real fix?
Thanks,
_______________________________________________
Jon Luchette
Emerson Hospital
Technology Specialist III
Work: 978-287-3369
Cell: 978-360-1379
jluchette@xxxxxxxxxxxxxxx
_______________________________________________
Other related posts:
