Forum Replies Created
-
Posts
-
Tt,
Wyse now confirms they will not be out onsite and that it is a bug in the OS code. No resolution yet. We will be shipping the V10L back and possibly trying a V90L. If I hear anything re a resolution, I will post.
Thanks for all the attempts to assist.
DDS
Update on V10L OS.
Wyse emailed back today via our vendor stating that they will probably send an engineer to our site to see the problem first hand in our operating environment. Sounds like they are getting serious.
I will advise if they find anything (assuming they show up).
TT & ConfGen,
Thanks to both for your replies. I have contacted Wyse again and they affirm the bug is present in the new code in the Wyse proprietary OS. They also told me that the embedded XP OS or the CE OS should work properly with NLB. I assume this is correct as we have tested an HP Thin Client that has embedded XP on it and it works flawlessly. The engineer at Wyse said she would post back to me when they found the resolution to this issue. They are very interested in getting it resolved.
We may see about getting a V90L demo unit from Wyse to see how well it works. If I hear of anything positive from Wyse I will try to get it posted back here.
Thanks again for the replies.
DDS
Hi CG,
We do not use Session Directory. We were hoping for an out of the box solution that we could just plug into the network and access our TS servers via NLB. We “purchased” the box from Lenovo on a 30 day trial. We are currently working with Wyse to try to find a solution, no joy so far.
I suppose I could ask them to ship me a box with a previous Wyse OS on it to see if it would work. I guess it depends on how badly they want to resolve it. We are not destined to be a big Thin Client site, maybe 30-40 units. But if we are having an issue with NLB, I suspect others with our same setup may have one too. Knowing that HP Thin client works right out of the box makes me think Wyse would want to resolve it.
Thanks for the reply. Every little bit helps.
DDS
TT,
I changed the TCP/IP timeout to 4. No change. I downloaded the ver 5 firmware and was unable to load it. System log says “Firmware 5.2.0_35.05 is too old to ensure hardware compatibility. (Hitachi processor)”
Is there a way to force the firmware downgrade?
Thanks,
DDS
TT,
Thanks for the reply again. We worked with a Wyse engineeer yesterday for a while and upgraded the firmware to 6.1.0_06. We also set the unit to static IP. None of the above did anything to change our situation. Wyse says they are moving this issue to the “inside” to dig more deeply into it.” We shall continue to work it from out here though as I would like to resolve it.
I will see what happens once I set it to a TCP/IP timeout=4 setting. If that makes no difference I will try the older version of the firmware. The Wyse engineer did make a comment about “maybe the bug is back”….
I will let you know how it goes. Appreciate your continued assistance.
DDS
TT,
All of our terminal servers have the same setting for encryption. They (including the NLB server settings) are set for Client compatible/RDP security level. No certificates have been loaded.
So if I can connect to a single TS IP and maintain a session, should I not be able to connect to a NLB session and maintain it if encryption settings are the same? (RDP V2) It seems (remember I am very new to this…) that in a single session the 2 NICs talk back and forth as they should but in a NLB session it is as though once connected, some network miscommunication occurs and dumps the session. Not a wildly technical explanation but that it what seems to be happening.
FQDN was correct and does not work. As mentioned, single IP of nonNLB server does work.
Do you have a “primer” on how to setup the .ini files on a server if we decide to try that? I know the sys admin wants an out of the box connection but maybe that won’t be possible?
Thanks,
DDS
TT,
Thanks for the reply. As mentioned I am quite new to T Clients, but need to evaluate them. Our Hp demo as mentioned worked out of the box the way we wanted it to. I suspect it might be because it has the embedded XP Pro OS on it.
Version of firmware in the V10L is 6.0.1_04. We do have it setup with FQDN as host name, but will check to be sure there are no typo’s, etc. As mentioned, it does connect, just won’t stay connected to NLB IP. It is ok on the Non-NLB IP though. I will also check the RDP encrytpion status and get back to you.
I have a conf. Call with Wyse support scheduled for 11am Pacific time today so maybe they can also shed some light on it. I appreciate your taking time to answer. Nice to see knowledge shared.
Thanks,
DDS
