- This topic has 2 replies, 1 voice, and was last updated 5 years, 11 months ago by
.
-
Posts
-
I went ahead and made a new thread now that I better understand the issue, the old thread can be viewed here.
There appears to be an issue with the MirrorFileServer parameter and the DNS parameters, setting both parameters causes the thin client to run off of the cached configuration file, ignoring changes made to the wnos.ini file found on the FTP server.
This can be demonstrated with the following wnos.ini file, if you uncomment the DNS settings you will no longer be able to change the Terminalname.
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 7.0.011 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 2 *
;*************************************************************MirrorFileServer=yes
;*************************************************************
;* Network *
;*************************************************************Terminalname=TC001
;Terminalname=TC002
;DNSIPVersion=ipv4 DNSServer=1.1.1.1;1.1.1.2 DNSDomain=fqdn
SignOn=NoI tested this against 8.3_109, 8.4_104, 8.4_112, and 8.5_009. The last time this worked was 8.3_014. Are my DNS settings invalid, is anyone else able to reproduce?
Could anyone else take a minute and test this? Dell Enterprise Support claims they can’t reproduce the issue with the provided config file, which I find surprising.
Just an update in case anyone else comes across this. Dell support has acknowledged that this is a known issue introduced in 8.3. As of 8.5_012 it still exists.
Reproducing the issue appears to require the use of Static IPs, DNS and MirrorFileServer wnos.ini parameters and a manually configured File Server in a different subnet from the client.
- You must be logged in to reply to this topic.