C50LE doesn’t always pull wlx.ini file??

Hello

I have a network setup with a windows FTP sever for WYSE configs. I have DHCP setup using a cisco router. I have added the 161 and 162 parameters. When my clients boot, they sometimes pull the wlx.ini file, and sometimes they dont. I thought maybe it was related to the file not changing, but even if I change the wlx.ini file I can’t get the clients to pull it all the time. Here is a detailed clean log of a single wyse client booting and the effect on my WYSE ftp server:

#Software: Microsoft Internet Information Services 7.0
#Version: 1.0
#Date: 2011-03-30 20:05:41
#Fields: date time c-ip cs-username s-ip s-port cs-method cs-uri-stem sc-status sc-win32-status sc-substatus sc-bytes cs-bytes x-session x-fullpath x-debug
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 ControlChannelOpened – – 0 0 0 0 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 USER anonymous 331 0 0 72 16 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PASS anonymous@ 230 0 0 21 17 8b29fc05-1316-4cf5-aa24-e963b9e190a8 / –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PWD – 257 0 0 31 5 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 TYPE I 200 0 0 20 8 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 MDTM – 501 87 0 214 7 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PASV – 227 0 0 52 6 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 61344 DataChannelOpened – – 0 0 0 0 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 61344 DataChannelClosed – – 0 0 45 0 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 LIST – 226 0 0 111 6 8b29fc05-1316-4cf5-aa24-e963b9e190a8 / –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 ControlChannelClosed – – 0 0 332 65 8b29fc05-1316-4cf5-aa24-e963b9e190a8 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 ControlChannelOpened – – 0 0 0 0 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 USER anonymous 331 0 0 72 16 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PASS anonymous@ 230 0 0 21 17 e9341c6c-71c2-47a8-95f3-49277a3b14e1 / –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PWD – 257 0 0 31 5 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 TYPE I 200 0 0 20 8 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 CWD wyse 250 0 0 29 10 e9341c6c-71c2-47a8-95f3-49277a3b14e1 /wyse –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 CWD wlx 250 0 0 29 9 e9341c6c-71c2-47a8-95f3-49277a3b14e1 /wyse/wlx –
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 MDTM 0080649988D5.ini 550 2 3 49 23 e9341c6c-71c2-47a8-95f3-49277a3b14e1 /wyse/wlx/0080649988D5.ini File+system+returned+an+error.
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 PASV – 227 0 0 52 6 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – –
2011-03-30 20:05:41 – – 192.168.11.12 61345 DataChannelClosed – – 2 3 0 0 e9341c6c-71c2-47a8-95f3-49277a3b14e1 – File+system+returned+an+error.
2011-03-30 20:05:41 192.168.199.10 – 192.168.11.12 21 RETR 0080649988D5.ini 550 2 3 49 23 e9341c6c-71c2-47a8-95f3-49277a3b14e1 /wyse/wlx/0080649988D5.ini File+system+returned+an+error.

It never even tries to get the wlx file?