wnos.ini changes not working

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #64630
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    Sup!

    I’m trying to change wnos.ini file because all machines here does have
    permission to reset to factory defaults (because Privilege=None or AdminMode=Yes)

    but there’s a problem: when i change the file in ftp:\\[server ip\wyse\wnos\wnos.ini
    a Dell Menu comes in, and we cant logon (even with SignOn=on or off), everytime that i change Privilege/Admin mode to Low or No the Dell screen shows of in a blank page.

    After some tests i saw that .ini file inside the folder was useless, because if i delete
    it or change the name to wnos.txt ou wnos.html, the configuration to our server comes in and works perfectly (but the user still can reset factory default)

     

    My question is: if the wnos.ini is not who sets the configuration in ftp:\\[server ip]\wyse\wnos\wnos.ini, how does our ThinClient can enter normally with privilege none?

    it’s because of ftp? how can i change it? we do need to be able to change the configurations

    by the way we are using a lot of ThinOS versions, but mostly are S10 Wyse or Wyse 3040

     

    #66491
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    up

    #67876
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    Post
    1. your wnos.ini
    2. a screenshot of the location where the wnos.ini is stored
    3. a screenshot of the Thin Client System Setup-Central Configuration-WDA

    CG

    #68615
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    Here’s our .ini file:wnos.ini exampleAnd here’s the location folder:

    location example

     

    The  Thin Client System Setup-Central Configuration-WDA config is:

     

    WDM Checked and DNS: SRV RECORD checked too

    the path that TC seeks is:

    192.168.11.1\wyse\wnos

     

    Just to add more info:

     

    TC tried to connect to WDM/WMS and failed

    Tried to connect to our file server wyseftpfbc4tc and failed

    Connected at SNTP: 192.168.11.1

    #68728
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    what happens when you try from a Windows PC to access that ftp folder?
    Does it work?

    CG

    #69226
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    Yep, this ftp server is accessable trough windows

    #70798
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    When you are using a browser and access ftp://192.168.11.1/wyse/wnos you can see the wnos.ini, correct?
    When you click on the wnos.ini you do see the content, correct?

    the path that TC seeks is:

    192.168.11.1\wyse\wnos

    Add “ftp://” in front of the URL of the fileserver value on the client.

    CG

    #72005
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    When you are using a browser and access ftp://192.168.11.1/wyse/wnos you can see the wnos.ini, correct?
    When you click on the wnos.ini you do see the content, correct?

    Correct, but the wnos in there is not readable (not .ini)

    ftp files

    If wnos in this server is not readable, where does ThinOS get the config.?

    Because if i change the wnos.in or wnos.ini.ori file to .ini (default), our configs change and a blank page requesting login starts, so i need to reach where is the actual configuration and try to change it, where does ThinOS search if wnos.ini file is not readable?

    #73509
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    If the file does not exist, has a wrong name or the extension is wrong (.in, .ini.ori, .ini.txt) then it will typically fall back and use the last wnos.ini it was able to read in the past, as this would have been cached locally.
    Simply download the Configuration Generator from this website and configure your wnos.ini as you need it. Then copy it to your /wnos folder and you are ready to go.

    CG

    #73537
    AvatarHyuu
    Participant
    • Total Post: 7
    • Newbie

    If the file does not exist, has a wrong name or the extension is wrong (.in, .ini.ori, .ini.txt) then it will typically fall back and use the last wnos.ini it was able to read in the past, as this would have been cached locally.

     

    There’s a way to get back this last wnos.ini cached locally??

    I will try to generate a new config with ConfGen but it will be nice to see what’s inside the
    actual configuration

    #74794
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    No way to pull a config from the device.

    CG

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