- This topic is empty.
-
Posts
-
We have about 40 V10L machines (6.1.08 ) deployed at a remote site. We configured a FTP server and DHCP in our local location and created a wnos.ini and in our local location everything works like it should.
In the remote site every time we restart or shutdown machines when they come back on, the machines do not get the settings from wnos.ini. It comes back up to the default (unlockdown) screen with RDP or ICA connection choice. This only happens at the remote site.
We checked the connection between us and the remote site and only about 30% of it is used. We also tried putting a local DHCP server in our remote location and that did not help. This happened on 6.1.05 and is now happening on 6.1.08.
Has anyone seen this before? Any ides on what we can do to fix it?
Thanks,
VHi,
What switches do you have? Maybe you need to set portfast as the unit may be starting to fast for the switch?
Cheers,
-TTDid the units get their IP address?
What path is entered in Fileserver field?
Is this the correct one?
Do you use Option Tag 161/162 to send out the fileserver settings?
Same in LAN and WAN?
Any errors in System Log on the WTOS units?Portfast, as TT suggested, is a good point to start.
Regards
CGIt seems that you are saying this may be a sporadic problem at the remote sites? I have seen where the remote thin clients sometimes pick up the settings and then other times they don’t. Very frustrating, and unfortunately I don’t have the solution to the problem – I just wanted to find out if this was the same thing happening at your site. ❓
Hi Akwoolf,
If you have intermediate issues like this I have always found them to be network related. As with all network issues a pain to track. If you know you have the paths correct to the wnos.ini (as it works sometimes) next to look at is switches. The S10 and V10L boot so fast some switches have not had time to enable the port so the terminal “Can not find system profile”
Now you can use WireShark to track this but to prove it plug in a really cheep Fry’s style switch (like a cheap 5 port netgear or similar) in between you device and the floor switch. This will cause you floor switch to keep the port alive and the cheap switch will not have the Spanning Tree process that sets the port enabled/disabled. If the device works time to set the spanning tree options on your switch. I have hit this problem on switches from Cisco, Nortel, HP, Dell and Avaya IP phones.
Cheers,
-TTAt the remote site, are they going through a Cisco switch? This happened to us a few weeks ago and with the help of the guys on this site it was fixed.
We had to go into the Cisco switch and turn of the STP on each individual port the the V10L’s were plugged into.
Are you using WDM and the 161 DHCP option? If so, have you seen this link?
http://www.freewysemonkeys.com/modules.php?name=News&file=article&sid=23&mode=thread&order=0&thold=0
We had things set up just fine using an FTP server to serve up wnos.ini and as soon as I introduced WDM into the mix our V10Ls failed to configure after restart. It turns out that WDM overrides the 161 option by default and resets the FTP server entry to itself. Unchecking “Enable Return FTP/INI at Checkin” fixed the problem. Don’t know if this is applicable but good luck!
- You must be logged in to reply to this topic.