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.
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.
djmoeller
1 Rookie
•
8 Posts
0
March 21st, 2017 10:00
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.
RMontalvo
2 Intern
•
560 Posts
0
November 1st, 2016 09:00
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.
k11no
1 Rookie
•
6 Posts
0
March 21st, 2017 10:00
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
k11no
1 Rookie
•
6 Posts
0
March 21st, 2017 10:00
Ahh....interesting. Thanx for posting your solution in here...:-)