WDM 4.5.2 – Discovery Problem

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #947
    dshaun
    Member
    • Total Post: 59
    • Back Stage Pass
    • ★★★★

    Hey guys

    Im having discovery issues with WDM. At the moment i have the dhcp tag 186 set up and i also have “RapportServer = [ipaddress]” in my wnos.ini file. Im not sure if i have a setup wrong,but i cant manually discover my S10 units, tried multiple times. Manually adding them to the WDM is out because there in different locations and im not sure of their MAC address.

    I have few registered in WDM but there are alot that are missing. These S10 units are also on different subnets. I also tried removing the RapportServer command in the wnos.ini as well. Just to verify, the wnos.ini file is on a different server to the WDM. Not sure if that makes a difference or i can manage it better. Any suggestions would be appreciated.

    Thanks

    #11771
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    DON’T use WDM 4.5.2 – 4.5.3 is now released so upgrade to this.

    Once you have done this you may need to upgrade the firmware on the devices to get them to check in, the 186 tag should make it work,

    Cheers,
    -TT

    #11772
    dshaun
    Member
    • Total Post: 59
    • Back Stage Pass
    • ★★★★

    My S10 units are on system version 6.1. Once i download 4.5.3, compability wont be an issue??

    #11775
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    OK, 6.1 is new so they will work with 4.5.3…

    #11793
    dshaun
    Member
    • Total Post: 59
    • Back Stage Pass
    • ★★★★

    Ok so i have done the upgrade to WDM 4.5.3. I have the same problem. Some units are being discovered while some arent. However i found that the ones that were being discovered are the same ones that came up in the previous version of WDM

    I had a look at one of the S10 unit event logs that is not showing up in WDM. The ones that can’t be discovered are not coming up with “Contacting HServer” in the bootup.

    Any ideas?

    Thanks

    #11806
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    It is still worth the upgrade, 4.5.2 is not too good.

    Now I would remove either the 186 tag or the RapportServer= and only use one or the other. If you use the 161 and 162 tag then use the RapportServer= command and no 186 tag.

    Make sure under WDM preferences you have the Blazer option “return ftp/ini” turned off (un-ticked).

    On the units that do not check in can you check to see if the WDM server IP is filled in and greyed out?

    Finally check the event logs on the server for any hserver or web server errors,

    Cheers,
    -TT

    #11812
    dshaun
    Member
    • Total Post: 59
    • Back Stage Pass
    • ★★★★

    hey

    Yeah i checked it , it was greyed out with the right WDM ip address. I checked the tags, with and without and the rapport command in the .ini file. Nothing worked. Final solution, i decided to reset them to factory default, and it worked. They are now checking in to WDM. Now i would be a little happier, but looks like i may have travel around a bit to reset them all. Fun, fun, fun lol. Thanks for the help. Much appreciated.

    #11814
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Wow, thats weird!

    Well at least I can maybe save the travel! Try this command in the wnos.ini, I have pasted this from the WTOS parameters guide:


    FactoryDefault={yes, no}

    Set to yes to reset the system setting to factory default only
    once for each firmware change. Set to no then reboot, the
    option will be initialized again.



    Cheers,
    -TT

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