- This topic is empty.
-
AuthorPosts
-
June 4, 2014 at 6:32 am #8240
I’m using D10D clients to connect to a xenapp 6.5 farm. I’m using pnagent and the connection works fine, however, right after logon, the wyse client comes up with an error message “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”.
However, the connection to xenapp farm is not broken, so when you press OK to the error message, it switches back to the desktop/xenapp and you can work as normal. So the solution works fine, no connections gets dropped, but we get a lot of calls from our users because of this error message and would like to fix the problem.
I do not get similar errors with S10 or C10 clients to the same farm. My wnos looks like this: (removed servernames and domainnames, and farmname)
DomainList=”xxxxx”
Screensaver=0
TimeServer=x.x.x.x
TimeZone=’GMT + 01:00′ ManualOverride=yes
Language=No Charset=ISO-8859-1
SignOn=Yes ExpireTime=1 EnableOK=Yes
Priviledge=low
AutoSignoff=YES
IcaBrowsing=HTTPPnliteServer=http://HRT2WTSDC.xxxxxxx.no/Citrix/wyse/config.xml AutoConnectList=”farmname:desktop” ReconnectAtLogon=1
SessionConfig=ALL MapDisks=yes
SessionConfig=ICA SessionReliability=yes AudioQuality=High
I’m attaching a pic of the error. As you can see at the bottom, the connection is not broken.pic: https://www.dropbox.com/s/sl15tsb4h5jj00w/Photo%2013.05.14%2010%2036%2021.jpg
June 4, 2014 at 10:36 am #24773Do you also see this message, if you remove the AutoConnectList parameter and start the app manually?
CG
June 4, 2014 at 12:56 pm #24779Hi ConfGen, thanks for the reply!
I now tried removing the AutoConnectList parameter and launched the application (which is a published desktop) manually, but I get the same message. I also tried a couple of my other applications, same happens with all of them..
June 26, 2014 at 7:27 am #24831It’s me who originally created this post.
Update: I found out that this error message is not related to connecting to my farm, but it is because I have enabled pre-launch and the wyse client itself is trying to launch the citrix pre-launch application, which fails, because connection directly from the wyse client to this application is not allowed in firewall, and should not be. This pre-launch session should only occur within the users published desktop..
I see that pre-launch was enabled in thinos 8, that’s why I don’t have this issue on C10 or S10 because they’re on thinos 7..
Is there any way to disable pre-launch on the wyse device in the .ini file for example? I can’t find anything about it in the admin guide or ini file documentation.
June 26, 2014 at 11:35 am #24833Where have you seen that pre-launching is enabled?
No ini parameter available at moment?
CG
June 26, 2014 at 11:54 am #24834I see it in the eventlog that it tries to connect to PreLaunch-xxx… just as it is stated in ftp://210.245.180.77/C10LE_8.0_037/RN_Wyse_ThinOS_8_0_037_RevA_GR.pdf under “new features” so it is indeed enabled and there doesn’t seem to be any way to disable it..
June 26, 2014 at 12:02 pm #24836No, not that I am aware of.
CG
July 1, 2014 at 11:23 am #24842That’s it for my with wyse clients.. Adding a new feature like this with no option to disable it. Disaster.
-
AuthorPosts
- You must be logged in to reply to this topic.