T50 FTP option 161 issue

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #7406
    Avatardelboy
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    Hi,

    i have an issue with a T50 terminal. For some reason the T50 isnt pulling through the correct FTP server details from DHCP.

    Instead of pulling through the correct IP of the FTP server (option tag 161) its pulling through “ftp://25436207i/wyse”.

    Option tag 161 is currently working for 3500 Thin OS terminals so i know thats ok.

    Any ideas why this is reading the IP and converting it into /254/036/207

    thanks in advance.

    Del

    #22504
    Avatartarasov
    Member
    • Total Post: 138
    • Legend in Own LunchBox
    • ★★★★★

    Guido helped me with this yesterday: DHCP 161 should have STRING type – I had IP address and ThinOS worked OK while Linux showed garbage just like yours

    #22505
    Avatardelboy
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    Thats good thanks. Have you proved that changing option tag 161 to string doesnt affect Thin OS terminals yet? We have 3500 Thin OS terminals and I want to make sure this doesnt affect them.

    #22506
    Avatartarasov
    Member
    • Total Post: 138
    • Legend in Own LunchBox
    • ★★★★★

    yes, shure – this was the number one task! My ThinOS works OK either with string or with IPs. In fact according to docs 161 SHOULD be string not IP.

    #22507
    Avatardelboy
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    ok thanks for the info. we have been using Thin OS terminals since they were release several years ago and have also used IP instead of string and never had a reason to use anything other until now.

    Whilst your on, do you know of anyway to add a dislaimer (end user agreement) to the T50. We have one for all of our T10’s but I cant find anywhere to add one for the T50.

    thanks again.

    #22508
    Avatartarasov
    Member
    • Total Post: 138
    • Legend in Own LunchBox
    • ★★★★★

    so as I understood NoticeFile is not working in Linux (I myself never tried it). As workaround I would recommend creating of autostarting browser connetion to the web page with end user agreement. This lacks NoticeFile timeout…but works at least:-)

    #22509
    Avatardelboy
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    thanks for the workaround. I will try that.

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