- This topic is empty.
-
AuthorPosts
-
8. July 2012 at 19:21 #7417
The problem is, that new device with WTOS doesn’t apply $mac.ini settings althrought all the prerequisites are met. The device appears online in Wyse Device manager.
The folder structure is like this:inetpubftprootwysewnoswnos.ini
inetpubftprootwysewnosincmac.iniThe wnos.ini includes $mac.ini parameter.
Also when looking FTP logs it appears that device has no problem accessing mac.ini
2012-07-05 12:36:11 10.5.65.10 - 10.1.7.132 21 ControlChannelClosed - - 0 0 62d6363d-cee1-41e1-9ea4-f7b3a133bb52 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 ControlChannelOpened - - 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 USER anonymous 331 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 PASS -guest@wyse.com 230 0 3 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 /
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 TYPE I 200 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 SIZE /wyse/wnos/wnos.ini 213 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 /wyse/wnos/wnos.ini
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 MdTm /wyse/wnos/wnos.ini 213 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 /wyse/wnos/wnos.ini
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 PASV - 227 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 54714 DataChannelOpened - - 0 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 54714 DataChannelClosed - - 64 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 -
2012-07-05 13:03:56 10.5.91.11 - 10.1.7.132 21 RETR /wyse/wnos/wnos.ini 550 64 0 f4b2b808-d2ee-4bfd-8b27-1e68445525d6 /wyse/wnos/wnos.iniSo what am I overlooking here?
I appreciate any ideas.9. July 2012 at 9:29 #22562I hope you did not name the mac.ini as “mac.ini” but as something like “008064123456.ini”, didn’t you?
CG
9. July 2012 at 10:05 #22566Yes, it is 008064123456.ini
9. July 2012 at 10:13 #22567And your wnos.ini reflects
Include=$mac.ini?CG
9. July 2012 at 10:23 #22568Yes it does. We have quite a few other terminals also which are all working fine. The problem is only with two new terminals althrough they are the same model and configurated exactly like working terminals.
9. July 2012 at 10:49 #22569You will need a network trace to further analyze this.
THere is nothing mentioned in your ftp logs that the mac.ini to looked for at all.CG
13. July 2012 at 12:41 #22576Strange but seems that the mac.ini configuration file name is case sensitive althrough I didn’t find any information about it from documentation.
I changed letters in mac.ini from lowercase to uppercase and after that the settings applyied to the terminal.31. July 2012 at 8:30 #22597Are you using a Linux FTP server? Linux is case sensitive while MS isn’t.
CG
1. August 2012 at 7:53 #22621No we are using Windows Server 2008.
3. August 2012 at 11:33 #22639Which path is set up in the configuration of your FTP site under IIS? Is DHCP Tag 162 used?
-
AuthorPosts
- You must be logged in to reply to this topic.