- This topic is empty.
-
AuthorPosts
-
March 14, 2011 at 12:38 pm #6512
Hello,
After upgrading a V50 with the last Linux 6.6.2_12 – FTP firmware the wlx.ini on the ftp server is not read anymore.
All the old V50 terminals are still working and getting there wlx.ini off the ftp server.What wrong with this firmware?
Peter
March 14, 2011 at 8:36 pm #20220Are you using DHCP option tags?
I think the latest FW is not reading the option tag 162 correct and eliminates the /Wyse prefix.
Check your FTP server log to verifiy.CG
March 15, 2011 at 8:59 am #20225Yes I use DHCP
This is a copy of the FTP log
The FTP server is a Windows 2008R2x64 server, if I switch to the old W2K3 FTP server it still not working.2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelOpened – – 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 USER anonymous 331 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASS [email protected] 230 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab /
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 TYPE I 200 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 SYST – 215 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASV – 227 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 – – 10.10.0.222 49302 DataChannelClosed – – 3 3 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 RETR //wlx/0080646CC038.ini 550 3 3 753fc6d6-e01e-4808-96ee-76c5fcb754ab /wlx/0080646CC038.ini
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelClosed – – 0 0 753fc6d6-e01e-4808-96ee-76c5fcb754ab –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelOpened – – 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 USER anonymous 331 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASS [email protected] 230 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 /
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 TYPE I 200 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 SYST – 215 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASV – 227 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 49303 DataChannelOpened – – 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 49303 DataChannelClosed – – 3 3 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 RETR //wlx/wlx.ini 550 3 3 f53f767a-3ca0-4d85-a546-f136b48fd1f1 /wlx/wlx.ini
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelClosed – – 0 0 f53f767a-3ca0-4d85-a546-f136b48fd1f1 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelOpened – – 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 USER anonymous 331 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASS [email protected] 230 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 /
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 TYPE I 200 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 SYST – 215 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 PASV – 227 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 49304 DataChannelOpened – – 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 49304 DataChannelClosed – – 3 3 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 RETR //wnos/wnos.ini 550 3 3 80ff2345-dd2a-460c-8f23-8eac9d7e5121 /wnos/wnos.ini
2011-03-15 08:53:22 10.10.0.60 – 10.10.0.222 21 ControlChannelClosed – – 0 0 80ff2345-dd2a-460c-8f23-8eac9d7e5121 –March 15, 2011 at 5:08 pm #20230RETR //wlx/wlx.ini 550
This indicates that there is either no wlx.ini ro the NTFS right are not correct. I assume the first.
What makes me suspicious is that there are two slashes in front of the wlx/wlx.ini.
Are you using DHCP option tags? Which? Which value? Can you try without?CG
March 28, 2011 at 1:19 pm #20289Removed the / in the DHCP 162 option.
Now its working again and the old Wyse clients still work. -
AuthorPosts
- You must be logged in to reply to this topic.