djmoeller
1 Copper

ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

I support an existing ThinOS environment, we have approximately 200 devices. The entire site uses static IP’s, we do not use DHCP options.

Configuration of 8.0 and older thin clients requires us to make four changes from default.

[Network Setup]
IP Address: 1.1.1.5
Subnet Mask: 255.255.255.192
Default Gateway: 1.1.1.1

[Central Configuration]
File Servers/Path: 1.1.1.4/wyse

If I make these changes on an 8.0 client and reboot, the event log contains the following.

12:33:06 System Start Date: 2016/06/15 Wednesday
12:33:06 System Version: 8.0_037
12:33:06 CPU Version: Marvell PJ4 v7 Processor-wmmx rev5 (v7l)
12:33:06 Ethernet device version: MV Gigabit Ethernet.
12:33:06 CESA: driver register OK.
12:33:06 Embedded Controller Version: 3.04
12:33:06 Initializing Certification Center …
12:33:06 AUDIO: Change record device to DOVE Audio
12:33:06 AUDIO: Change playback device to DOVE Audio
12:33:06 VUSB: Local Device(0x05e3 0x0608, 0x09, 0x00, 0x01)
12:33:07 USB: Found a new device “HUB” on port 1
12:33:07 Waiting for network link …
12:33:07 VUSB: Local Device(0x046d, 0xc054, 0x03, 0x01, 0x02)
12:33:07 USB: Found a new device “HID” on port 1
12:33:08 VUSB: Local Device(0x413c, 0x2107, 0x03, 0x01, 0x02)
12:33:08 USB: Found a new device “HID” on port 2
12:33:09 Looking up WDM server by DNS hostname …
12:33:09 DNS/WINS can’t resolve [wdmserver]
12:33:09 Looking up WDM server by DNS SRV record …
12:33:09 DNS/WINS can’t resolve [_wdmserver._tcp]
12:33:09 Contacting File Server …
12:33:45 Accessing system profile …
12:33:45 Contacting SNTP [ouradserver.fqdn]
12:33:45 DNS/WINS can’t resolve [ouradserver.fqdn]
07:33:47 Contacting SNTP [ouradserver.fqdn]

The FTP server also contains logs.
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 ControlChannelOpened – – 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 USER anonymous 331 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 PASS -guest@wyse.com 230 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d /
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 TYPE I 200 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 SIZE /wyse/wnos/xen.ini 550 2 3 61371d8d-60d3-4136-b404-51219bdc5b3d /wyse/wnos/xen.ini
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 CWD /wyse/wnos/xen.ini 550 2 3 61371d8d-60d3-4136-b404-51219bdc5b3d /wyse/wnos/xen.ini
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 PASV – 227 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:45 – – 1.1.1.4 50148 DataChannelClosed – – 2 3 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 RETR /wyse/wnos/xen.ini 550 2 3 61371d8d-60d3-4136-b404-51219bdc5b3d /wyse/wnos/xen.ini
2016-06-15 12:33:45 1.1.1.5 – 1.1.1.4 21 ControlChannelClosed – – 0 0 61371d8d-60d3-4136-b404-51219bdc5b3d –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 ControlChannelOpened – – 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 USER anonymous 331 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 PASS -guest@wyse.com 230 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 /
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 TYPE I 200 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 SIZE /wyse/wnos/wnos.ini 213 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 /wyse/wnos/wnos.ini
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 MdTm /wyse/wnos/wnos.ini 213 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 /wyse/wnos/wnos.ini
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 PASV – 227 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 50149 DataChannelOpened – – 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 50149 DataChannelClosed – – 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 RETR /wyse/wnos/wnos.ini 226 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 /wyse/wnos/wnos.ini
2016-06-15 12:33:46 1.1.1.5 – 1.1.1.4 21 ControlChannelClosed – – 0 0 7a37e255-6740-4cdf-b922-dcf53344dbb5 –

Performing the same configuration to an 8.1 client and rebooting produces the following event log and no FTP logs.

12:52:09 Embedded Controller Version: 3.04
12:52:09 CESA: driver register OK.
12:52:09 System Version: HF 8.1_031
12:52:09 CPU Version: Marvell PJ4 v7 Processor-wmmx rev5 (v7l)
12:52:09 Extracting package: rom.pkg V1.01 …
12:52:09 rom.pkg: 202 files extracted
12:52:09 VGA: offscreen video ram = 207 MB
12:52:09 Screen1: [0xac10, 0x4061] DELL P2211H Week(37) year(2011) S/N: W4XCG19FC3XL
12:52:09 Screen2: [0xac10, 0x4061] DELL P2211H Week(37) year(2011) S/N: W4XCG19FC3XL
12:52:09 Initializing Certification Center …
12:52:09 System Start Date: 2016/06/15 Wednesday
12:52:09 Ethernet device version: MV Gigabit Ethernet.
12:52:09 AUDIO: Change record device to DOVE Audio
12:52:09 AUDIO: Change playback device to DOVE Audio
12:52:10 VUSB: Local Device(0x05e3 0x0608, 0x09, 0x00, 0x01)
12:52:10 USB: Found a new 480Mbps device “HUB” on port 2
12:52:10 Waiting for network link …
12:52:10 VUSB: Local Device(0x046d, 0xc054, 0x03, 0x01, 0x02)
12:52:10 USB: Found a new 1.5Mbps device “HID” on port 1
12:52:11 VUSB: Local Device(0x413c, 0x2107, 0x03, 0x01, 0x02)
12:52:11 USB: Found a new 1.5Mbps device “HID” on port 2
12:52:11 ENET: set default gateway 1.1.1.1
12:52:12 ENET: set default gateway 1.1.1.1
12:52:12 Contacting file server …
12:52:12 Looking up WDM server by DNS hostname …
12:52:12 DNS/WINS can’t resolve [wdmserver]
12:52:12 Looking up WDM server by DNS SRV record …
12:52:12 DNS/WINS can’t resolve [_wdmserver._tcp]
12:52:44 DNS/WINS can’t resolve [wyseftppfbc4tc]
12:52:44 Cannot access system profile
12:52:45 Contacting SNTP [pool.netp.org] …
12:52:47 DNS/WINS can’t resolve [pool.ntp.org]

For the purposes of troubleshooting I have simplified my wnos.ini file.

;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.4.013 *
;* Copyright by Thomas Moellerbernd *
;* *
;* http://www.technicalhelp.de *
;* *
;*************************************************************

;*************************************************************
;* General 1 *
;*************************************************************

autoload=1

;*************************************************************
;* Time *
;*************************************************************

Timeserver=adserver.fqdn Timeformat=”24-hour format” Dateformat=mm/dd/yyyy
TimeZone=’GMT – 06:00′ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”Central Standard Time” DayLightName=”Central Daylight Time”

;*************************************************************
;* Network *
;*************************************************************

WINSServer=1.1.1.3
DNSIPVersion=ipv4 DNSServer=1.1.1.2 DNSDomain=fqdn
SignOn=No

;*************************************************************
;* Services *
;*************************************************************

Service=WDM disable=yes

Also of note, I can “browse” the FTP server from a 8.1 thin client using the import certificate tool. This will logically produce logs on the FTP server. I can also use RDP if I setup the connection manually. It seems to me there is an issue with the 8.1 firmware, and that it no longer respects the setting typed into central configuration?

0 Kudos
1 Solution

Accepted Solutions
djmoeller
1 Copper

RE: ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

Our config file does contain DNS settings and also uses the server name. The IP address is used only for initial setup. This allows technicians on the floor to replace a failed device with minimal setup. The answer in our case was to increase the TCP Timeout from 1 x 30 seconds to 2 x 30 seconds. This change was necessary when transitioning from 8.0 thin clients to 8.1 thin clients. Presumably the firmware has changed in some small way.

0 Kudos
4 Replies

RE: ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

DJMoeller,

the firmware version you have installed is obsolete, so you may want to consider downloading the latest version available (as of this date is 8.3_014) to verify. Details on getting this firmware can be found below my signature.

Roger Montalvo

0 Kudos
Highlighted
k11no
1 Nickel

RE: ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

You have probably solved this by now, but for what it's worth:

Don't use ip's in your config. Use DNS-names with FQDN.

Change:

File Servers/Path: 1.1.1.4/wyse

To

File Servers/Path: servername.domain/wyse

Tags (2)
0 Kudos
djmoeller
1 Copper

RE: ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

Our config file does contain DNS settings and also uses the server name. The IP address is used only for initial setup. This allows technicians on the floor to replace a failed device with minimal setup. The answer in our case was to increase the TCP Timeout from 1 x 30 seconds to 2 x 30 seconds. This change was necessary when transitioning from 8.0 thin clients to 8.1 thin clients. Presumably the firmware has changed in some small way.

0 Kudos
k11no
1 Nickel

RE: ThinOS 8.1 Firmware not working with FTP server.

Jump to solution

Ahh....interesting. Thanx for posting your solution in here...:-)

0 Kudos