- This topic is empty.
-
Posts
-
We have 11 VL10 terminals deployed at present & get this error message showing up at the base of the login box. It happens randomly on all the trminals at random times. A re-boot of the terminal fixes the issue & all is good again in the world of VDI.
Anybody seen this or got some bright ideas? All responses greatfully accepted.ChrisK from TPS Support
Do you get this message on all terminals?
Do you get it always?
What firmware are you running on?
What BIOS version are using?
Can you ping something when this message is seen?
Does the device has an IP address when the message is seen?CG
I’ll try to answer some of your questions in the reply as I can.
The terminals are running system version 6.2.0_08 and ROM 1.15i.
This info was from the system info screen.
When the error occurs it seem to happen on any of the 11 we have deployed and it could happen at any time. No pattern to it at this stage.The terminal can’t be logged into in this state so I would assume that it can’t be reached with a ping. Haven’t had one do it today so can’t answer this one yet.
Don’t know if there are later versions of system code or bios availabe. It seems to be some thing that you can’t get from the Wyse site without paying extra money which I don’t agree with. If it’s available elsewhere I would love to know.
Hope some one can shed some light or help with this issue.
ChrisK (tpssupport)
Just had one show this error. I noted it’s IP & I could ping it. Can’t ping from it as it’s locked down.
Just can’t be logged into until it is re-started. Most strange.ChrisK (tpssupport)
What’s your backend? Brand of switches?
If using Cisco switches look for a parameter like “FastPort” and enable it.CG
@ConfGen wrote:
What’s your backend? Brand of switches?
If using Cisco switches look for a parameter like “FastPort” and enable it.CG
Thanks for the advice. Our switches are HP procurve 5300 & 4100 series. Will have a search on the net as to what “fastport” is & see if there is a HP equivalent.
ChrisK
Just did a search & found thet “Fast Port” in Cisco is the equivalent of “spanning tree” in the HP world. We are in an education environment & by default have spanning tree enabled on all our switches. Stops the kids from bringing our whole network down when one of them decides to plug a utp cable direct between 2 network points.
ChrisK
PortFast != Spanning tree, don’t mistake.
PortFast is a manner in which you can tell Cisco devices that the port is going to be used by end devices, The port wil therefore go in to a forwarding state without completing extensive tests regarding spanning-tree loops. It will test for these and block the port if a loop is found but this could be a little too late.
The reason i suppose for ConfGen to point this Cisco option out is that it is known to put a port in a forwarding state too slow, therefore missing the initial connection from the client to the LAN (usually the DHCP proces) and leaving the client booting slow and missing stuff. (PXE booting is near impossible without it)
So, a lot of blabla, but in essence, if someone tells you to enable or disable Portfast, dont mess with your Spanning-Tree, its not the same thing.
An Update…..
I have notice that more often than not the terminal will come up with the “network i/o error” after it’s been in use & the user logs out. At this stage it goes back to the normal wyse login screen with username, password & our domain name in the bottom row.
It’s still happening on a semi regular basis & I have asked our local Wyse tech if he can help but so far he hasn’t been able to come up with a solution.ChrisK
We have the same problem. Running 6.2.0_08. I got one on the line this morning. I could shadow the session and ping from the terminal and to the terminal. DNS to our connection broker and domain controller also worked. Very odd but it does not seem to be an actual network error.
Ask Wyse for a new firmware version. I know they have fixed several things in the network stack. Latest version should be around 6.2.025.
CG
I took your advice and I am now running 6.3.0_11f (1.15i). I will slowly roll this out to the site and will report back later next month.
Thanks
@thinman89 wrote:
I took your advice and I am now running 6.3.0_11f (1.15i). I will slowly roll this out to the site and will report back later next month.
Hmmm 6.3.x has been released ? Or just a typo
I received 6.3 from Wyse support. My sales rep said they moved the release date due to some QA testing needed for one of the TCX extensions. Maybe today will be the day!!
- You must be logged in to reply to this topic.