Forum Replies Created
-
Posts
-
We have CE 5 build 559 installed. Atheros is Ver 1.00 (Build 3)
The model number on the Netgear adapter is WG111 but has no letter at the end of it.
I’m hoping not to have to return all of the adapters for new ones, but it’s looking like I may have to.
Ill 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?
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.
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=yesOk I’ll run that trace route and see what I get.
Also I’d just like to let you guys know when I got my s10 I was getting an error “Can’t allocate a consecutive memory” after leaving it on over night. I had moved up to the 5.2.033 firmware and that got rid of the problem. When I went down to 5.1.028 which is on the WYSE site I get that error again after 1 night of use. So if anyone else out there is getting that error you can ask WYSE for the 5.2.033 firmware and that will take care of that issue.
Ok I rolled back to 5.1.028 and its still taking a long time to contact Hserver. After it gets passed that it said it failed to open and I have 2 IP’s that are no where near any IP’s in our organization let alone the rapport server. I get:
Hagent: open “49.48.46.51,51.46.49.46” failed
But I have in my config the server IP (10.33.1.57) and when I go check network settings under rapport server it has 10.33.1.57 there so I’m not sure why I’m getthing these weird IP’s not where I can delete them from.
Sorry its been really busy here today and I wasn’t able to check the forum til now (right before I head home) I will try the downgrade tomorrow and see what happens and let you know. Thanks for the help.
-Mike
Hmmm, if its meant to start then stop then I’m probably just confused as the to cause of my problem. I’ll give you my full story.
My hospital purchased an S10 as a demo to start replacing some of our 3150’s and 3125’s. We got one from CDW and started working on it. There was a memory error we got taken care of with new firmware from wyse (5.2.033) But after we got our terminal talking to our rapport server, instead of the instant boot up and ica connecting right away to our published app, the terminal sits on connecting to Hserver for almost 2 minutes. Then it finishes its look up and connects to the published app.
When I modify the config file to Disable Rapport then it bypasses the connecting part and connects really fast again (which is the point of getting these new terminals as our users hate the long wait times on the CE devices) But Disabling the rapport agent defeats the purpose of having rapport to manage the terminals remotely.
I had tried to look some things up and I had “thought” that the connecting to HServer was it trying to connect to rapport and that it was taking so long because the Hserverinit service was not running. But if its not supposed to be running then there went that theory. Does this mean that if I want to use the S10 and Rapport that the terminal has to connect for 2 minutes whenever it gets restarted/power goes out?
Thanks again for all the help.
Thanks Joe. I gave it a try but that didnt seem to help. I went and looked at your other post and ran the query and it says the service is running. But when I go into Services and look at it its stopped.
We’ve just rebuilt our rapport server 4.4.1 on vmware. We are getting this same problem with hserverinit starting and then immediately stopping.
We are on server 2003 sp2. I’ve gone to your hot fix section and installed all of those along with turning off DEP. We have anonymous access enabled. IUSR account password set to never expire. And no other webserver running on this server.
The reason we’re trying to get this fixed is so that our new S10 wont hangup on connecting to Hserver when it starts up. I edited our config file to disable rapport agent and that sped the terminal back up but then ofcourse I can’t manage the device which kind of sucks.
Have you guys come across any other things which might cause this service to stop? Maybe something on SP2?
P.S. This site is amazing and I want to thank you all for all the info I have gathered from it.
