- This topic is empty.
-
AuthorPosts
-
September 6, 2012 at 8:03 am #22752
It does not matter where you put it in.
CG
September 10, 2012 at 9:00 pm #22765Tagging along…
I’m experiencing the same issue with the Wyse T10 (Tx0) where the autoconnect through pnliteserver is not working.
There are no log errors and I’ve exhasted my options ❓
I’ve tested on firmware v 7.1_122 & 7.1_125
Syntax:
PnliteServer=CLLDCWI01 ReconnectAtLogon=2 ReconnectFromButton=2 AutoConnectList=”Production Desktop”I’ve include the farm name with no success: “XAFarm:Production Desktop”
Any Suggestions? Could this be a bug?
September 12, 2012 at 5:10 pm #22766The following WNOS settings work for our autolaunch. I would try adding a http:// or https:// along with the fully qualified domain name of your Web Interface server to see if that makes any difference.
;************************************************************
;* ICA *
;************************************************************IcaBrowsing=HTTP
PnliteServer=https://desktop.company.com ReconnectAtLogon=2 AutoConnectList=”FARMNAME:Full Screen Desktop”The event log on the WYSE T10 shows the following entries after successful logon:
40: ICA: pnhost = “https://desktop.company.com”
41: ICA: Connecting to “FARMNAME:Full Screen Desktop” …After logging off or disconnecting the XenApp desktop session these two entries are logged, and the WYSE login prompt is displayed.
42: ICA: terminated, status 0x1
43: Connection closed by server!Hope this helps.
September 14, 2012 at 12:04 pm #22770I would always start troubleshooting this ba using variables.
PNliteserver=blablabla Autoconnectlist=”*”
or
PNliteserver=blablabla Autoconnectlist=”XAFarm:Desk*”Make sure you take care of case sensitivity of the autoconnectlist value.
CG
January 17, 2013 at 11:25 am #23326I know this is an old thread but I just wanted to post this so that it may help other people.
I was also getting the “Invalid Statement” error. It turns out that I needed to put the following all on one line in the WNOS.ini file:
PnliteServer=http://address of server ReconnectFromButton=2 Timeout=30 AutoConnectList=”FarmName:AppName”
I didn’t create the WNOS.ini file in the first place but am told it was created using the config file generator so it maybe that that puts those all on separate lines but the firmware we are running definitely requires it all to be on the same line.
January 18, 2013 at 9:01 am #23328Yes, all has to be on the same line and ConfGen is doing this correctly.
CG
September 4, 2013 at 8:15 am #24171I’ve recently built a new Citrix XenApp 6.5 farm to replace our now aging Presentation Server 4.5 farm.
We have been successfully using Wyse S10 thin clients for a number of years without an issue.
However, I simply cannot get the S10 to connect to the Web Interface server in our new XA 65 environment?
It will connect to the XML service on the Session Controller XA server, but not the XenApp Services site on our WI server?
Our S10’s are running WTOS 7.1.207.
The wnos.ini file generated using ConfGen is below:
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.4.010 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************Autoload=2
#Privilege=Low Lockdown=No;*************************************************************
;* Peripherals *
;*************************************************************Language=AU
;*************************************************************
;* Display *
;*************************************************************; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=1280×1024 Refresh=
Screen=1 Resolution=1280×1024
DeskColor=”37 176 64″
DesktopColorDepth=32
Desktop=FinsburyLogo.bmp Layout=Center
Screensaver=”10″ LockTerminal=no Type=0 Image=FinsburyLogo.bmp;*************************************************************
;* Time *
;*************************************************************Timeserver=dc3.gotham.local
TimeZone=’GMT + 09:30′ ManualOverride=yes;*************************************************************
;* Network *
;*************************************************************SignOn=No
MaxVNCD=1
VncPassword=”F1nsbury”
VncPrompt=No
EnableLocal=Yes;*************************************************************
;* ICA *
;*************************************************************Seamless=Yes
;
;- ICA Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=ICA
Description=”XA65 Logon”
Icon=ica.bmp
HttpBrowsing=1
BrowserIP=http://WIserverFQDN
Application=”Desktop”
Fullscreen=1
Autoconnect=1
LocalCopy=NoThe event log when running the above wnos.ini file shows:
ICA: Connecting to “XA65 Logon”
DNS/WINS can’t resolve [Desktop]
socket connect: Connection timed out
ICA[Desktop]: Connection timed outI have also tried replacing the ICA configuration above with the following, as suggested in this thread, but this didn’t work either.
PnliteServer=http://FQDN of server ReconnectFromButton=2 Timeout=30 AutoConnectList=”FarmName:AppName”
The event log for this shows that it only gets as far as “Contacting SNTP”, like it doesn’t recognise the PnLiteServer command at all?
Any Suggestions?
September 8, 2013 at 7:39 pm #24173Have you a PNAgent site running on that WI? You cannot connect to a WI directly. You need a PNAgent site.
CG
-
AuthorPosts
- You must be logged in to reply to this topic.