WDM: Devices Not Discovered

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #428
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    Greetings:

    I’ve got WDM 4.5.1 up and running, but it’s having some problems talking to my thin clients. As detailed in the documentation, I have defined an IP Range and used the Discovery option to look for devices on that range. No results are returned.

    However, if I reduce the range to include one IP address higher and lower than a known client, it will discover it properly.

    I’m wondering if this is an issue that others may have seen? Or maybe it’s time to get our networking team involved?

    I have not installed any patches to WDM, as I couldn’t find anything on the Wyse.com site.

    Thanks for your help!

    #9587
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Joe,

    I have seen this exact issue now a few times – using subnet discoverys fails but an IP range works. I will ping wyse…

    #9590
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I just fixed it.

    I had to slow down the scan by increasing the Connect timeout to 2000MS. I currently have my delay timeout at 2000 as well, but I’ll be lowering both of those values to find the best one for us, as I’m pretty sure they both don’t need to be at 2000.

    As far as I can tell, the firewall is seeing the scan as an attack and it starts to block it after so many sequential address scans. Putting a delay in seems to do the trick, though!

    #9591
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I take that back…

    Discover is very flaky, and unreliable. It isn’t finding any devices anymore.

    #9650
    Avatarsteinlager
    Member
    • Total Post: 20
    • Regular Joe
    • ★★

    Hey joe,
    I have found the discovery process doesn’t work with older thinclients when using 4.5.1

    Anything newer than a 3125 is generally discovered, but older terminals that aren’t running the newer web version of rapport agent wont’ be detected. I have now seen this on 3 different sites.

    I would reccomend sticking to Rapport 4.4.1, detect the old winterms, update the agent, then update to 4.5.1 😉

    #13182
    Avatarltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    I know this is an old thread,
    but I seem to be experiencing the same issues…

    How come Wyse Support wouldnt mention this on the phone? They said that all devices should and would be detected by 4.5.3…

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