Wyse V50L Wireless Problems

  • This topic is empty.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #890
    Avatarskinnyvinny
    Member
    • Total Post: 8
    • Newbie

    Our company purchased two Wyse V50L clients with the integrated wireless for a proof-of-concept test. Long story short, the internal wireless acts flakey and unreliable. It will not associate with an accesspoint and then three reboots later it will associate fine. So far we have not been able to get to a comfortable point with the wireles reliability to even start testing deployment scenarios involving wireless.

    Here’s the technical nitty gritty:
    1 – We’re running WEP with open authentication and a simple 40-bit WEP key.
    2 – The AP’s used are Cisco 1200-series AP’s and the signal coverage is more than adequate. The wireless network has been in production for 18 months without a single problem. Mostly mobile laptop users running WinXP with a mix of OEM integrated wireless cards.
    3 – The V50L was purchased back in October and has Linux V6 (6.3.2 build 40) and the OS version is listed as 2.6.16.40.

    Should we give up on the dream of wireless-based thin clients and go the route of the wired V50’s….what has everyone’s experiences been using the wireless options Wyse offers in their Linux OS?

    I’ve tried the Wyse support site, but that is lacking in information to say the least. Any help anyone can offer is greatly appreciated.

    -Skinny

    #11513
    ConfGenConfGen
    Keymaster
    • Total Post: 10981
    • Jedi Master
    • ★★★★★★★

    Hi,

    wireless works fine for me.
    What wireless addon version are you using.
    I am working with WIRELESS-3.37.pak. You can download this from me here.

    CG

    #11515
    Avatarskinnyvinny
    Member
    • Total Post: 8
    • Newbie

    Since the original posting I upgraded to 6.3.2 build 52 via a link posted elsewhere in this forum AND loaded the WIRELESS-3.37.pak. Still no luck.

    Now I’m receiving an error that reads “Unsupported driver ‘vntwusb'” in the system status window and the network config dialog box keeps popping up on every boot.

    If I remove the WIRELESS-3.37.pak I no longer receive the error regarding vntwusb but the wireless still won’t associate with the access points.

    #11576
    ConfGenConfGen
    Keymaster
    • Total Post: 10981
    • Jedi Master
    • ★★★★★★★

    That is real strange as I am using a Cisco AP 1100 Series here.
    I’ve attached the USB wireless stick from Wyse and loaded 6.2.3-53 plus Wireless-3.37.
    All is running with WEP, 40-bit. The only difference is that I am using Shared instead of Open Authentication.

    #11578
    Avatarskinnyvinny
    Member
    • Total Post: 8
    • Newbie

    I’m going to spend some more time on this issue tomorrow and I’ll try getting the vendor involved (Wyse.)

    One other thing to note is that we are running the integrated wireless in the V50L, not the USB stick.

    #11579
    ConfGenConfGen
    Keymaster
    • Total Post: 10981
    • Jedi Master
    • ★★★★★★★

    Integrated and stick are technically identical.
    Both are attached via USB – yours internal and mine external

    #15089
    AvatarITperson
    Member
    • Total Post: 2
    • Newbie

    I am having the same problem with the WYSE wireless USB stick giving an “unsupported driver” vntusb error when plugged into a WYSE S50 device. Wireless add-on pack 3.17 is loaded on the device. Do you know where I can download 3.37?

    Thanks.

    #15090
    ConfGenConfGen
    Keymaster
    • Total Post: 10981
    • Jedi Master
    • ★★★★★★★

    I have put it on my my website.

    http://www.technicalhelp.de/products/5000/WIRELESS-3.38.pak
    Which firmware version are you running on your S50?

    CG

    #18957
    Avatardanjardon
    Member
    • Total Post: 2
    • Newbie

    I am having similar issues – have tried with and without the wireless addon.

    I am running V50L with:
    Version: 6.6.2
    Build: 02
    OS Version: 2.6.16.40

    WYSE USB Wireless Dongle – CCAD06LP1840T7

    With the addon, it appears to be working, but I cannot obtain an IP address. WEP is enabled.

    Without the addon, I receive syslog messages about can’t insert module and failed to load module.

    Any ideas?

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