Converted Thin to 0 won't grab wnos.ini config file

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #42663
    dragon6687
    Participant
    • Total Post: 5
    • Newbie

    I’ve been given the task to convert all of our Wyse Thin clients running Win 7 embedded to a 0-client version similar to that of the Xenith boxes we also own. While my Xenith boxes are working great in terms of getting their config file off our FTP server, I’m running into issues with the now 2 converted thin clients.

    During boot I keep getting:
    Contacting File Server….
    DNS/WINS can’t resolve [FTPserver.domain.com]
    DNS/WINS can’t resolve [wyseftpfbc4tc]

    I’ve looked through the forums already and tried a bunch of different things (like adding the wyseftpfbc4tc as an alias of my FTP server).

    I have options 161 and 162 set, and are working fine for my Xenith boxes.
    I have copied my configuration xen.ini and renamed is wnos.ini once I found out the converted thin clients look for wnos instead of xen. I am not using any Wyse Device Manager software, simply the FTP server to distribute the config files.

    Below is my config file and my FTP log regarding the client:

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

    ; If you are using a version of WTOS code < 7.1_133 please use:
    ; Rapportserver= instead of WDMServer=
    AdminMode=yes Username=Administrator Password=***********
    Privilege=None KeepDHCPRequestIP=yes
    ShowDisplaySettings=yes

    ;*************************************************************
    ;* General 2 *
    ;*************************************************************

    Locale=English
    EnableGKey=yes

    ;*************************************************************
    ;* General 3 *
    ;*************************************************************
    AutoSignoff=yes
    ShutDown=standby

    ;*************************************************************
    ;* Peripherals *
    ;*************************************************************

    Language=Us
    Device=audio Volume=100 mic_vol=100

    ;*************************************************************
    ;* Display *
    ;*************************************************************

    Dualhead=yes Mainscreen=1 Orientation=hort Align=Bottom MonitorAutoDetect=yes
    Screensaver=15 LockTerminal=yes Type=0

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

    Timeserver=10.10.1.1 Timeformat=”12-hour format” Dateformat=mm/dd/yyyy
    TimeZone=’GMT – 05:00′ ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName=”Eastern Standard Time” DayLightName=”Eastern Daylight Time”

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

    RapportDisable=yes
    Device=Ethernet Speed=”Auto”
    ; If you are using a version of WTOS code < 7.1_133 please use:
    ; RapportDisable= instead of WDMService=
    ;WDMService=No DHCPinform=yes DNSLookup=yes
    SignOn=No
    MaxVNCD=2
    VncPassword=********
    VncPrompt=No

    ;*************************************************************
    ;* General Session *
    ;*************************************************************

    SessionConfig=ALL MapDisks=yes DisableSound=No UnmapUSB=yes
    SysMode=VDI toolbardisablehotkey=yes DisableAddConnection=yes ToolbarAutoQuit=no toolbardisablemouse=yes

    FTP LOG:
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 ControlChannelOpened – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 USER anonymous 331 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 PASS -guest@wyse.com 230 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 TYPE I 200 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 SIZE /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 CWD /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 PASV – 227 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 49809 DataChannelOpened – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 49809 DataChannelClosed – – 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 RETR /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 ControlChannelClosed – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –

    #42665
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Check locally on the client – System Setup-Central Configuration-Fileserver.
    What is shown there? Does it correspond to your ftp server setup?

    CG

    #42667
    dragon6687
    Participant
    • Total Post: 5
    • Newbie

    from what I can see yes, it has \\ftpserver.domain.com/wy (then it goes off screen). The File Server/Path is tinted in green and grayed out though.

    UN and PW are set to anonymous which is correct.

    The only “special” setup I have that is different is in my DHCP 162 settings. The way my FTP server is setup, you start already in the Wyse folder, because of that my 162 option has to be /$ to truncate the path so that is skips looking for the Wyse folder and directly for the wnos folder. Works fine with the Xeniths…would the converted thins not be able to react/see the truncation the same way?

    #42669
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    So, your OT162 ends with $, correct?
    This means that the Wyse folder should not be used. From your observation the local Fileserver entry shows /wyse/, which souldn’t be.
    Check your ftp server log to see if the clients (Xenith vs. ThinOS) try to access the same folder structure.
    Make sure the converted units really do get an IP from this DHCP server and not a different one.

    CG

    #42672
    dragon6687
    Participant
    • Total Post: 5
    • Newbie

    Yes, it looks like they are looking at the same place. According to the FTP logs it looks as though the converted client is actually seeing and attempting to access and read the wnos.ini config file, but then disconnects and fails. I’m beginning to wonder if it’s something in the config file that’s causing the system to refuse to load it?

    Here is the FTP logs, 10.10.50 is a working Xenith, 10.10.0 is my converted client:

    Xenith
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 USER anonymous 331 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 PASS -guest@wyse.com 230 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b /
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 TYPE I 200 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 SIZE /wnos/xen.ini 213 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b /wnos/xen.ini
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 MdTm /wnos/xen.ini 213 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b /wnos/xen.ini
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 PASV – 227 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 49767 DataChannelOpened – – 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 49767 DataChannelClosed – – 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 RETR /wnos/xen.ini 226 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b /wnos/xen.ini
    2016-04-01 12:06:20 10.10.50.130 – 10.10.1.202 21 ControlChannelClosed – – 0 0 76be0e4d-a8c0-4918-bc40-bd9c4b57675b –

    Converted Thin
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 ControlChannelOpened – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 USER anonymous 331 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 PASS -guest@wyse.com 230 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 TYPE I 200 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 SIZE /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 CWD /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 PASV – 227 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 49809 DataChannelOpened – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 49809 DataChannelClosed – – 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 RETR /wnos/wnos.ini 550 2 3 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 /wnos/wnos.ini
    2016-04-01 12:43:26 10.10.0.21 – 10.10.1.202 21 ControlChannelClosed – – 0 0 33b6d5d0-c9d7-44ae-bf70-524cc40b17e4 –

    #42673
    dragon6687
    Participant
    • Total Post: 5
    • Newbie

    Gah, I found the reasoning.

    Apparently the Xenith’s are more than fine using the fqdn for the 161 option, but the Converted dont. Once I change the option to just the IP address, it got it’s config file fine.

    Thank you for your help and advice of what to look at!

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.