- This topic has 101 replies, 32 voices, and was last updated 13 years, 6 months ago by
.
-
Posts
-
Hi bcgjay,
have you send a trace along with your ticket to Wyse?
CG
Thanks for the reply ConfGen. Wyse support actually haven’t called me back yet – I escalated the ticket on Friday so I suspect they will call on Monday (tomorrow).
When originally troubleshooting the problem, I did follow the steps you had posted in another thread to get a trace on an S10, but that did not appear to work for my V10L’s. I did a quick search but couldn’t find any instructions specific to this model.
GJ
There is nothing special. You have to do the same steps on S10 and V10L.
What was the problem?CG
Ok I’ve got trace working now. It wasn’t working before because I was putting the “EnableTrace=yes” on its own line in the wnos.ini rather than on the same line with “Privilege=High.”
That’s why I recommend using ConfGen to create the wnos.ini 😉
CG
Just wanted to update that Wyse support has recommended I upgrade my firmware on the V10Ls from 6.2.0_08 to 6.2.0.18; however, at the same time the tech says he couldn’t find any documented fix included in this firmware that specifically addresses this problem.
However, without upgrading, I haven’t yet seen the issue reoccur since disabling session reliability. It could also be possible that the users have simply stopped calling the helpdesk when receiving the error(s) though.
I just started experiencing this issue w/ 1 S10. The terminal itself does not freeze, the RDP session just disconnects while still showing the session screen. It’s like the S10 doesn’t know it’s been disconnected. A reboot jumps her right back into her disconnected session and all is good—for a while.
We have 100+ terminals scattered throughout WAN links that don’t have this problem—this particular problem is on the same LAN that the TS resides.
Swapped network cables, terminal itself—problem still exists no matter what. My .02
Just wanted to add a final update that since disabling session reliability our issues are still completely gone. No more panic errors or “bad file name” messages and random disconnects have disappeared.
Wyse support have (finally) acknowledged this as an issue in firmware 6.2.0_08 on the V10L; which, they say, is resolved in firmware 6.2.0_18 – however I have not yet tested this.
I’ve had the latest firmware on my test client with session reliability enabled for a couple of weeks without any issues, but it’s not used that often (few times a day, only for a few minutes each time) so I don’t consider this a real “test.” At some point in the near future, I’ll upgrade our other 2 test clients, a random prod client. If all goes well, we will slowly phase in the 6.2.0_18 firmware. I’ll update with results as I get them.
I can confirm the same problems and WYSE sent me Firmware 6.2.021 as there were problems with .018.
All problems have now disappeared.
Hi Guys,
Looks like I spoke to soon. We have a number of users who are still being randomly disconnected with errors saying session timed out, etc.
Any more thoughts?
- You must be logged in to reply to this topic.