- This topic is empty.
-
Posts
-
I’m working with a client who has both 1200LE and S10 Wyse thin OS clients. I’ve created a WNOS.ini file to push out a new client firmware version to the appropriate terminals and to configure a new ICA connection to a new PS4.5 farm.
I’ve also configured a new Vendor Class on the DHCP server, added the values for 161 and 162 and configured the DHCP scopes to provide these values.
When I bring either of the types of terminal up, they request and IP from DHCP and boot normally. However, they do not connect to the file server and pull the WNOS.ini or the update where applicable. Upon checking the file server settings in the network settings applet on the device, I find that the file server IP is set to the IP for our DHCP server, not for the FTP server I have serving up the files. I’ve tried resetting to factory defaults, reconfiguring and restarting DHCP services, deleting the file server value and rebooting to try and force the devices to collect the DHCP provided FTP address information, all to no avail. I’ve also ensured that the DHCP server does not have the 161 or 162 values already configured somewhere else.
If I input the FTP server address manually, the devices connect and pull the files normally.
Anyone have any idea why we would be getting the DHCP server IP instead of the configured IP on these devices? I have a mix of firmware versions, with the lowest being 4.4.010i and the highest being 5.0.063i I believe. I had, at one point, installed the Wyse Device Manager workgroup edition software on my laptop to see if I could push out the firmware and new connection settings directly to the devices. When I discovered the DHCP method, I brought my WDM installation offline. I did note that once I’d discovered devices in WDM, they picked up my laptop’s IP as the FTP server. This worked fine for a couple of tests once I’d configured the files and placed them on my laptop’s FTP default site, but I’ll be leaving here at the end of the week and want to put in place a system that the local resources can use to update these things automatically.
Thanks for your help!
Hi CivMason,
how did you setup the option tags 161 and 162? As a string or as IP address? It has to be a string value.
The unit always use the IP of the DHCP server as Fileserver address once they haven’t found/configured a FTP server.ConfGen
Thanks for replying so quickly!
I did not in fact configure that setting as a string. I just went back and reconfigured the value to be a string value, then tested and I’m still getting the same result. Any other ideas on what I might have done wrong? I’m a complete newb to the Thin O/S clients in particular, and not terribly versed with Wyse terminals in general. Are there any documents out there for the configuration of these settings? I found one document as I was looking up wnos.ini syntax that mentioned setting up a new vendor class to put the 161 and 162 values in, which I did, but the article was a little vague. Anything better out there?
Thanks again, ConfGen and all, for the assistance!
DHCP options are configured on Windows 2000/2003 server in the below way.
a. Open DHCP manager
b. Right click on the DHCP server
c. Go to “set predefined optionsâ€
d. Click the “add†button
e. Add 161 and 162
f. Go to your Scope and now add 161 and 162 with the correct values.161 and 162 are strings. As a value for 161 enter the IP address of your FTP server. As 162 value enter eg. /mywnosfolder. This will result in ftproot/mywnosfolder/wyse/wnos. If you enter eg /mywnosfolder$ this will result in ftproot/mywnosfolder/wnos.
By default you do not need this unless you wish to change the FTP path from /wyse/wnos which is the predefined path, if you add the path to be /pub/folder then /wyse/wnos will be added to the end.There is a quick start guide available here https://technicalhelp.de/products/1000/Wyse%201xxx%20Serie_german.PDF. Although this is a german PDF it contains some screenshot that may help you as well.
Cheers
ConfGen
- You must be logged in to reply to this topic.