- This topic has 5 replies, 2 voices, and was last updated 4 years, 10 months ago by
.
-
Posts
-
It seems like this topic has been beaten into submission, but I cannot get my S10 thin clients to update their firmware from the FTP server. The FTP server is running on a Windows Server 2016 system in one of the virtual machines. The logs show the thin clients logging in correctly, but when they try to retrieve the files (.ini and boot files) the FTP server posts 550 errors,”file not found/file unavailable”. I’ve tested this from multiple thin clients and get the same results. The strange thing about this problem is that I can FTP into the server from a computer and pull down the files with no problems using the same anonymous credentials as the S10s. I have been working on this problem for almost two weeks now with no resolution. Everything is configured per Wyse documentation. I need to be able to update the firmware as my customer will updating their ERP system later this summer and several of the S10s have version 5 firmware that cannot correctly connect to the WinServer2016 terminal server. The rest of the S10s are on v 6.5.0_22 but should be upgraded as far they can go. I am doing this testing with a 6.5.0_22 thin client trying to update it 6.5.0_30. The problem would appear to be a permissions issue, but being able to retrieve the files from a computer using the same credentials would seem to blow a hole in that theory. What am I missing? Any help would be greatly appreciated!
Here’s a PowerShell directory listing:
Directory: C:\inetpub\ftproot\wyse\wnos
Mode LastWriteTime Length Name
—- ————- —— —-
-a—- 1/26/2010 8:07 AM 21504 RCA_boot
-a—- 1/26/2010 8:08 AM 3130924 RCA_wnos
-a—- 2/7/2010 8:07 PM 232361 RN -WTOS 6 5 0_30.pdf
-ar— 5/8/2019 3:44 PM 40 wnos.iniWhat should the file attributes be? Would assume that they should be a minimum of read only. Does the “archive” attribute prevent them from being read? Will try to change attributes to see if that make a difference.
Modified attributes to “ar” adding read only, still getting 550 error when thin client tries to access.
Set up another ftp server on a plain Win7 machine instead of Server 2016 and still get the same result. Can ftp in and fetch files from a computer but not a thin client. Tried several different S10 boxes to no avail, could the problem be something in the S10s?
- You must be logged in to reply to this topic.