XPe load via WSI over LAN not PEER to PEER

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #818
    Avatarcelem
    Member
    • Total Post: 7
    • Newbie

    I had a lot of trouble flashing a new load into a WT9450XPe. After trying many, many variations, I was successful. My final working configuration was WSI version 1.3.0 in combination with FileZilla server with the user anonymous set up with the C:InetPubFtpRoot path.

    My setup is Windows XP Home connected to the Internet through a D-Link router.

    What I noticed during my failed attempts was that nothing material changed from using WSI over a hardwired from connection to my machine configured in the specified 10.1.1.12 and using “Tiny DHCP” or simply plugging it into the D-Link router and letting its DHCP server assign the IP addresses. The real key for success, in my case, was switching from the WAR Deamon FTP server to the FileZilla server. FileZilla made it work for me and via the D-Link router in my normal LAN configuration!

    #11195
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    Hi celem,

    good to know that Filezilla fixed. But I want to warn you to use WSI in a LAN enviroment.
    When you start WSI now and start an imaging job, each and every unit that will boot in the meantime will be reflashed without warning.
    That’s why Wyse recommends to use WSI only in a lab enviroment.

    Cheers
    CG

    #11203
    Avatarcelem
    Member
    • Total Post: 7
    • Newbie

    Regarding the warning on flashing in a LAN environment – I understand the possibility of a problem if multiple Thin-Clients were in the same LAN environment, which is not my case.

    In my case, I consult for a small local medical free clinic and we are migrating to a client-server environment using old eBay obtained thin-clients to same money. The thin-clients sold on eBay almost always have unknown passwords and modified programs, so, at my house, I flash them back to the default state before installing them into the clinic’s LAN environment. Once in the working environment they will never be flashed again as they simply are used to access the server in a very static manner. Thus, in my case, flashing in my own, segregated thin-client LAN environment is OK.

    I think that Wyse’s warning about not flashing in a LAN environment, without explaining why, is a disservice. They should state why, as it obviously doesn’t apply to every situation – mine being an example.

    Thanks for the warning, however!

    #11206
    ConfGenConfGen
    Keymaster
    • Total Post: 11002
    • Jedi Master
    • ★★★★★★★

    That’s sounds like a good solution.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.