- This topic is empty.
-
Posts
-
I have an S50 connecting via XDMCP and a font server defined. Initially the unit will connect correctly. After one logs off, the auto-reconnect kicks in, but displays an error message that says it could not connect to the font server. The font server is running, and if you click the connection manually it works flawlessly again. Anyone have any information on how to just get it to auto connect without the bogus failure?
Just to be clear, it’s not a server problem, other S50s, with older firmware, connect just fine. I have about 30 of these things to deploy at this location, and don’t relish flashing that many; I just don’t have time, so that isn’t an option.
Go to Control Panel-Addons and compare the XDMCP addon build number.
Maybe just installing a new addon (or older one) fixes this.
BTW, upgrading to newer/older firmware is a very easy task and takes only a few minutes to setup and a couple of minutes (appr. 10) per unit.CG
It had XDMCP-6.8.0-3.28 installed, so I replaced it with XDMCP-6.8.0-3.21 which I download from WYSE. The error still occurs.
As for the flashing, the flashing takes 15 minutes, plus at least 5 minutes of unpacking, setting up the unit, and then re-packing it for shipping. Doing this 30 times? I have enough to do as is. Is downgrading the firmware to fix a bug really the only solution?
Of course downgrading is not the only solution. The other option would be to contact Wyse, tell them your story, ask to open a call with engineering, maybe get an offer from them what it would cost to fix (this may not occur depending of if they see it as a bug or an enhancement), wait for some time (this could take seom) and get a fix. Maybe the fix is part of the core OS and not the XDMCP addon. This way you would have to upgrade all terminals 😉
OK, I know this is not the scenario you like to see.
What way do you flash your units? It takes about 20 minutes per unit?
Do you units have contact to any FTP server in your network? We could do the downgrade then automatically including the config.CG
Yes, I have to unpack it, set it up with a monitor, keyboard, and mouse, and then configure it to point at a local FTP server. I’ve tried the USB key route, but I can’t seem to get that to work. I have no problem contacting WYSE with bug reports, I have before, but I’m kinda under the gun here time wise, so I don’t think it would help me in time.
I’m wondering if the WYSE Rapport software (I think that’s what it’s called) would be a solution here? I have no problem spending money on a proper solution if one, it saves me time, and two, works well. Do you know if this, or something like it, would work here?
Thanks for the help btw, very much appreciated 🙂
This is the process I do now:
1. Ensure configured DHCP and FTP servers are running. Then power the S50 on.
2. Start –> Control Panel –> Network –> FTP Server
File Server : 192.168.0.10
Root Path : /wyse
FTP User Name: anonymous
FTP Password : [email protected]3. Start –> Control Panel –> System Preferences
Select “Upgrade firmware if version is newer or older”
4. Reboot from the Start menu. It will now flash the firmware.
Individually this isn’t so bad, but with 30, well I’m hoping for something faster, or at least more automated.
Great, you are using DHCP. You can use that to auto configure your clients to do the upgrade.
Go to my homepage and download the Linux quick start guide. It will direct you to the easiest way to upgrade.
Come back if you have questions.CG
I couldn’t find a Linux V6 Best Practices document, but I found “Wyse Blazer Best Practices.pdf”. Is that the one? I gather I need to create an FTP_ROOT/wyse/wlx/wlx.ini file. Is this correct? Then the unit will parse this file, and assuming Autoload is set to “1”, do the downgrade for me? I’m not sure how the unit gets the FTP server though, is this still manual?
Sorry, you are right. The “first steps” doc for Linux is only english.
But you are also right in your assumption about the file-/folderstructure.
Take a further look in the “first steps” from WTOS/Blazer. There you will find a passage about how to set up the needed DHCP option tags. For passing the IP of your FTP server to the Linux clients you will need option tag 161 – nothing more.CG
Well that kinda worked. Didn’t really save me much time though, as I have to pre-configure units for different locations, so the network settings are not uniform. I plan on trying out WDM in the next few weeks and see if that speeds the process up. Thanks for the help and the awesome PDF docs 😀
- You must be logged in to reply to this topic.