Rebooting Wyse V10L

  • This topic is empty.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • January 31, 2008 at 2:02 pm #903
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    We have a office in Charleston, our HQ is located in Memphis. We have 3 V10L’s in the Charleston office. I made a change to the ini file yesterday and had them reboot their machines last night to see the changes. Whenever they reboot them, it take 10-15 reboots to finally see the ini file (they just come up to the blank green screen.) THe ini file sits on a server here in the main office.

    I have a Wyse V10L sitting next to me here in Memphis that comes up on the first try.

    From the remote thin clients i can ping the server that the ini file is on and i can ping the name of the server they are RDP’ing in to.

    They all have the latest firmware, that was the change i made. This happened on old firmware also. Anybody else have this issue?

    January 31, 2008 at 2:11 pm #11566
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    When the remote clients are failing do they get an error message in the V10Ls event log?
    Do you see anything in the FTP servers log?

    January 31, 2008 at 2:25 pm #11568
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Nothing on the FTP server’s log.

    Excuse my ignorance on this, but if i want to get to the event log on the V10L and its is locked down, how do I?

    January 31, 2008 at 2:37 pm #11570
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    If I right click and go to administrator mode, what is the default username and password?

    January 31, 2008 at 2:49 pm #11572
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Ok, here is what it says:

    23: Contacting Hserver
    24: Hagent: open “server” failed
    25: Contacting file server
    26: DNS/WINS can’t resolve [wyseftpfbc4tc]
    27: Cannot access system profile

    January 31, 2008 at 3:42 pm #11573
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Line 27 is the important one.
    It shows clearly that the unit was not able to read the wnos.ini file.
    If can access it sometimes and sometimes not then it is clearly a network issue. Maybe you have some bad or slow networks on the way to the client?

    February 1, 2008 at 6:00 am #11588
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Could also be this issue?

    http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=30

    I also saw once a site where the Microsoft DHCP server was set to respond with a DHCP and BootP response without bootP being used. The default is DHCP only and the scope should be set to this,

    Cheers,
    -TT

    February 1, 2008 at 1:56 pm #11596
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Well, these terminals are plugged into an Avaya phone, then to an Avaya switch, we have VOIP phones there. The other one has mysteriously started working, so I’m not sure where to start.

    February 1, 2008 at 2:46 pm #11599
    jchittick
    Member
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Our Charleston scope has DHCP only, I will get with our WAN guy about the Cisco stuff, thanks for the help.

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