- This topic is empty.
-
Posts
-
I have been testing out blazer terminals to replace our CE devices which our doctors complain are too slow to reconnect (and god are they horribly slow).
Any issues I’ve had with the terminals have been taken care of and I really like the V10L and would like to push it as our new standard but have one problem that is setting me back.
We have 5 citrix servers in our environment with load balancing on. The users go to a published desktop and log in with their active directory credentials. The users on my test terminals (2 S10’s and now the V10L) were complaining of being kicked out of their sessions while in the middle of working and being brought back to the windows login screen. I did some investigating and found out a second citrix session had opened on the terminal. If I hit cntrl, alt, down I could switch back to the first session and their work would be right there.
I set up a terminal at my desk and just left it running for a day and a half straight not logged in or anything. When I came into work the next day I noticed the terminal had 2 citrix sessions running. A quick restart takes care of the problem but it comes back again after 2 days of running.
We have not had this happen on ay of our 350 CE device so I was wondering if I maybe had to add something to my config file to limit the number of concurrent sessions available to the terminals.
Any help would be great because I’d really like to get rid of the old terminals. Thanks again and love the site.
Check the System Log for a message called :”Cannot access system profile” or “System Profile accessed” (or simliar).
Latter would indicate you are using a wnos.ini. If so, please post it here, so we can check it.ConfGen
Sorry knew I forgot something. There are a couple little things that arent correct on there but for the most part that gets all 3 of my terminals working (1 wireless, 2 wired)
#
# Prompt the user for Log-in
Signon=0#
# Firmware loading
Autoload=1#
# Priveledges
Privilege=HighDeskcolor=”000 000 000″
Desktop=bwlogo.bmp
MaxVNCD=1
VncPrompt=0
Device=Wireless
Mode={Infrastructure}
SSID={CALL4962}
WepKey={1}
Key1={**************************}
RapportDisable=yes
RapportServer=10.33.1.57
Resolution=1024X768
Timezone=”GMT – 06:00″
ScreenSaver=0
AutoPower=yes
#ICA Connection Setting to Gottlieb Desktop
Connect=ICA
Browserip=”TS02, TS03, TS04, TS05″
Icon=citrix.bmp
Description=”Gott Desktop”
Application=”Gottlieb Desktop-GOTT”
Fullscreen=1
Autoconnect=1
Reconnect=1
Resolution=1024X768
Encryption=128
LocalCopy=yesOne thing that I noticed you might want to change the BroswerIp= the Data Collector (Probably your 1st citrix Server). I had this same issue with mine until one of the gentlemen on the forum corrected it for me.
What should I change the browserip to just one citrix server?
One thing I didnt check was to see if the 2 sessions that opened up were on different servers. That would be pretty interesting.
No Problem, I wondered if you got this resolved. This was an issue with using the localcopy=yes and the autoconnect= command together that was fixed in later firmware.
Try setting the localcopy=no and re-setting the terminals back to factory defaults. Do two sessions or one start? (use ctrl-alt-down arrow key to check).
Now set the localcopy=yes, do two sessions start? If so contact wyse support for later firmware,
Cheers,
-TTIll turn local copy off and give that a try. The problem with testing is that it takes a day or 2 for the multiple sessions to arrive so I will give you a heads up when that happens.
Also I checked the wyse site for firmware versions. for the S10 they have 5.1.028 and i’m running 5.2.033
And for the V10L they have 5.2.035.05 and im running 5.3.0_09 (came on the demo unit)
Was the problem fixed after that?
@MikeFelice wrote:
What should I change the browserip to just one citrix server?
One thing I didnt check was to see if the 2 sessions that opened up were on different servers. That would be pretty interesting.
Change it to your Data Collector which is probably the first Server you installed Citrix on. This one holds the information on where to point the load balancing applications. Ours is our CTX001 server.
- You must be logged in to reply to this topic.