- This topic is empty.
-
Posts
-
First of all, I truly appreciate any help in advance, I am completely new to WYSE thin clients and am pulling my hair out. I hope this issue has not been covered here, as I have done a fair amount of searching through the forums and cannot find a similar case.
About 9 months ago, I took over a complete thin client environment, with a combination of 60 WYSE and HP tc’s. This client had been sold on the idea that tc’s were completely maintence free and that all work needed to be done on the Terminal Server – needless to say this is not entirely true. All of the 35 WYSE units are 1200LE’s that have never had the firmware updated (rev 4.3.092i or 5.0.004.1i).
I have found the newest firmware available on the wyse support (WTOS 5.2.0_69) and have followed the instructions provided as well as directions found on their kb and the instructions here – to a T – and have had no success in getting the clients to update. I have tried it on an Server 2003 FTP server as well as an XP pro box, both of which had the firewalls turned off. I have entered the appropriate info into the tc’s network setup for file/ftp server and can see the anon user making a successful connection in the ftp log. I finally tried installing rapport server with the same results.
When the 1200LE boots i get:
5. Contacting File Server
6. Accessing system profile
7. Checking Software ftp:/wnos/UTC_wnos
8. Checking Firmware ftp:/wnos/UTC_b512The tc does nothing after that point.
My wnos.ini file is as follows:
autoload=2
signon=0I would like to do more config with the wnos.ini in the future but need to get past this issue first. Am I missing something here? Also, are there any good guides or suggestions for how to do some basic centralized management of the 1200LE’s.
Thanks again for any and all help
Zackp.s. just before posting this, i looked in the Wyse device mgr all of my devices under the imageable column it says “No”. Is this the root of my issue?
Hi,
can you post the FTP server log and the complete 1200le System log?
WDM is not really needed in first place and Imageable=no just means that the units are not able to do a PXE boot.
Check out the “First Steps” document in the Products section to read about the simple way to manage the clients.
CG
Thanks for the quick response. The log files are as follows:
FTP:
#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2009-11-30 20:26:03
#Fields: time c-ip cs-method cs-uri-stem sc-status sc-win32-status
20:26:03 10.43.10.3 [133]USER anonymous 331 0
20:26:03 10.43.10.3 [133]PASS [email protected] 230 0
20:26:03 10.43.10.3 [133]sent /wnos/wnos.ini 226 0
20:26:03 10.43.10.3 [134]USER anonymous 331 0
20:26:03 10.43.10.3 [134]PASS [email protected] 230 0
20:26:03 10.43.10.3 [134]sent /wnos/UTC_wnos 550 2
20:26:03 10.43.10.3 [135]USER anonymous 331 0
20:26:03 10.43.10.3 [135]PASS [email protected] 230 0
20:26:03 10.43.10.3 [135]sent /wnos/UTC_b512 426 64Not sure where to find the System log, is that the same as the event log?
Here is my event log:
1. System Version 5.0.004.1i
2. Checking Keyboard and Mouse
3. Looking up IP address from DHCP
4. Checking Security Key
5. Contacting File Server
6. Accessing system profile
7. Checking Software ftp:/wnos/UTC_wnos
8. Checking Firmware ftp:/wnos/UTC_b512Please let me know if you need anything else.
ZackWhat files do you have in your wnos folder?
Can you check the NTFS rights on each of them? Does anonymous user has all rights?CG
My folder structure is c:inetpubftprootwnos. In the wnos folder i only have UTC_b512 and wnos.ini. From ftproot down to the files i have anon set to full control in NTFS.
Zack
- You must be logged in to reply to this topic.