- This topic is empty.
-
AuthorPosts
-
March 18, 2011 at 2:00 pm #6529
Hello,
I am setting up a test View lab using the Wyse C50LE thin clients. I have most everything working and can establish a view connection manually using the Wyse Connection Manager. I have the FTP server setup and all the extra bits in the DHCP scope that I think I will need to make it all work. Here is the extra options in my DHCP scope:
161 (192.168.11.12)
162 (/$)
184 (wyse)
185 (wys3)When the wyse client boots my FTP log shows the Wyse user logging in then out immediately a couple times but no files are ever transfered. My ftp root directory for the wyse user looks like this:
/
/Wyse
/Wyse/WLX
/Wyse/wnosInside the /Wyse/WLX directory, I have a file named “wlx.ini”. I used the configurator to make this file, and intend for it to automatically load the view login instead of the admin/admin or thinuser/thinuser login. Not sure if it will work or not, but here are its contents (comments removed to save space):
Update.Mode=Both
Privilege=HighKeyboard.layouts=us
DisplaySettings=MON1 rotate-normal DDC
Timeserver=192.168.11.11
Timeformat=”12-hour format”
TimeZone=”US/Eastern” ManualOverride=1EthernetSpeed=Auto
Autologin=NoCONNECT=VMWARE_VIEWCLIENT
Description=”RWL Connection”
Host=viewconn1.rwl.local
Port=443
DomainName=RWL.local
AutoConnect=yes
Fullscreen=yes
DesktopSize=fullscreen
UseSSL=yes
UseAllMonitors=yes
LocalCopy=yesSo my questions are this:
1. Why is the Wyse client not pulling this file
2. Is this even the right file to make the thin client auto boot to a view login instead of the normal wyse login
3. Is the file configured correctly to do what I need to do?Thanks so much, I am VERY new to this, but have tried to do my homework before asking any questions.
ED7
March 21, 2011 at 10:55 am #202611. It is in the wrong folder or you are pushing the wrong value for OT161. Change the OT161 to / (simply remove the “$”)
2. yes
3. looks OK to me.CG
March 21, 2011 at 5:37 pm #20265OK, the issue was that even though I provided scope options 184 and 184, the system used those the first time to check versions, but the next 3 calls made to the FTP server were made by anonymous user and I had that access turned off. I have since changed the FTP server to only accept anonymous logins from a scope of IPs I trust, and this fixed the problem. Weird, but hopefully this will help someone in the future.
-
AuthorPosts
- You must be logged in to reply to this topic.