- This topic is empty.
-
Posts
-
At one of the sites I am looking after on a daily basis Wyse terminals are locking up, only by resetting the Wyse terminal are users able to work again.
The Firmware version they are using is 4.4, they access applications in two separate Citrix farms (3.0 and 4.0), they connect to a DHCP scope with settings to gain access to the farms.This has been going on for some time now, any help appreciated!
Hi, basically the screen freezes, the user is unable to do anything with the application.
They press the white reset button and hey presto they are able to work again.White reset button? The 1200LEs don’t have any reset button. Only the Power on/off switch.
What 4.4 version exactly are you running? Do you see a difference with the unit that you have upgraded to 5.x?CG
Hi, Thanks for the reply. Yes you are right they have to switch off and on, they are doing this regularly.
I need to check the version and will let you know. The firmware upgrade to 5.2 was just on a test machine, my next step is to upgrade one of the users and monitor this over a week to see if there is any improvement.
Basically they are getting a Security Message, once the security message kicks in the only way to get the Wyse terminal active again is to turn off and on again.
I am wondering if this is a Group policy causing the issue………I will attempt to be a bit clearer!
Basically the Wyse Terminals are locking up (freezing) they can’t continue unless they power down then power back up. The security message I spoke about is just a screen saver message, often the Wyse terminals ‘lock up’ after the screen saver kicks in but this appears to be just conincidence with the terminals ‘freezing’ up.
For the site that has this problem the Wyse terminals pick there configuration up from a DHCP server, I ‘think’ the problem may lie here hope you can clear up a couple of questions I have about the DHCP configuration scope settings.
There is an entry for ‘ (181) Wyse PNLite Server List’ this contains a DNS entry for a server in the PS4.0 farm and also a round robin entry called ‘ica’ (there are 6 dns entries for ‘ica’ the 6 entries relate to citrix servers in the PS 3.0 farm).
I believe it was configured this way so that the terminals could access applications in both the PS3.0 farm and the PS4.0 farm.
The questions I have around this that I hope you can help me with are….
1) (181) Wyse PNLite Server List – Do Wyse (1200LE) support entries like this for PS3.0 and PS 4.0 farm, can this cause issues?
2) (181) Wyse PNLite ServerList – should these entries be Citrix server specific or point to the NFUSE server (or web interface server)
3) Can I configure the Wyse terminals to connect directly to the FTP servers and still access all required applications. For this I mean can I configure one single trial Wyse terminal manually to bypass the DHCP configuration and still get it to access applications in both the PS4.0 and PS3.0 farm.Hi,
1) (181) Wyse PNLite Server List – Do Wyse (1200LE) support entries like this for PS3.0 and PS 4.0 farm, can this cause issues?
Not that I am aware of.
2) (181) Wyse PNLite ServerList – should these entries be Citrix server specific or point to the NFUSE server (or web interface server)
You should point them to one or more Citrix Datacollectors. No need to use the WI.
3) Can I configure the Wyse terminals to connect directly to the FTP servers and still access all required applications. For this I mean can I configure one single trial Wyse terminal manually to bypass the DHCP configuration and still get it to access applications in both the PS4.0 and PS3.0 farm.
Two options here:
1. Configure the client to use static IP address and enter the FTP server address manually
or
2. Create a DHCP reservation for this one client along with special scope options for this only client.CG
- You must be logged in to reply to this topic.