This is a public Discussion Forum  public

Topic

    S2H
    UR4-D not showing up on Wifi
    Topic posted October 10, 2012 by S2HCompetent 
    332 Views, 5 Comments
    Title:
    UR4-D not showing up on Wifi
    Description:
    have a bunch of wireless out on a tour...
    using workbench strictly for remote monitoring

    have 12 ch of psm-1000 and 8 ch of UR4 wireless..

    eveything has been working great for over a month...
    yesterday, I wasnt able to see the UR4's over Wifi for some reason...
    still having the issue today...

    I have been using version 6.3 since the tour started... never updated.

    I have no idea why I cant see them over Wifi...
    when I connect to a Hard line Ethernet cable into the router, I see it all Just fine, everything pops up.

    Nothing has changed since day one inside the rack...nothing is loose...
    anybody have any ideas?

    if it was a bad ethernet cable somewhere, then I wouldnt see them at all no matter what I do.


    I have already tried a full reset of the router, and still no change.
    I have tried different IP Addresses and I have tried Manual and Auto IP settings... nothing seems to work except for connecting with a physical hard wire ethernet cable between the laptop and the router.

    Comment

     

    • buhmanb
      Hi Scott,

      I've attached a diagram of what I can gather you have setup. (click to view a larger image) It might be a little different, but hopefully it can "frame" some of the questions / suggestions.


      Questions:
      1. When using WiFi - is WWB6 still able to discover the P10Ts? Just not the UR4Ds?
      2. IP Addresses? Are you using DHCP or manually assigning IP addresses / subnet masks?
      3. When using WiFi - is your PC/Mac able to ping, or open the Web based management utility of the WiFi router?
      4. What model of WiFi router is it?

      Suggestion:
      Make sure your PC/Mac's IP settings match those used by all devices.
      1. Unique IP addresses in the same range. (i.e. 192.168.1.10, 192.168.1.11, etc..)
      2. Same Subnet Mask on ALL devices and PC/Mac (i.e. 255.255.255.0)

      If the Subnet Mask on the PC/Mac is different than on the UR4 - WWB6 will not discover the UR4Ds.

      If you can't ping / manage the WiFi router itself over WiFi - then the WiFi section of your router or PC/Mac may not be configured correctly - or failed. Refer to the troubleshooting guide for your WiFi router.

      Hope that helps!
      -Brian
    • S2H
      Hi Scott,

      I've attached a diagram of what I can gather you have setup. (click to view a larger image) It might be a little different, but hopefully it can "frame" some of the questions / suggestions.


      Questions:
      1. When using WiFi - is WWB6 still able to discover the P10Ts? Just not the UR4Ds?
      2. IP Addresses? Are you using DHCP or manually assigning IP addresses / subnet masks?
      3. When using WiFi - is your PC/Mac able to ping, or open the Web based management utility of the WiFi router?
      4. What model of WiFi router is it?

      Suggestion:
      Make sure your PC/Mac's IP settings match those used by all devices.
      1. Unique IP addresses in the same range. (i.e. 192.168.1.10, 192.168.1.11, etc..)
      2. Same Subnet Mask on ALL devices and PC/Mac (i.e. 255.255.255.0)

      If the Subnet Mask on the PC/Mac is different than on the UR4 - WWB6 will not discover the UR4Ds.

      If you can't ping / manage the WiFi router itself over WiFi - then the WiFi section of your router or PC/Mac may not be configured correctly - or failed. Refer to the troubleshooting guide for your WiFi router.

      Hope that helps!
      -Brian


      1: discovers PSM 1000's no problem
      2: DHCP on all... predefined in the router for Mac address so they always get the same IP.
      all subnets on units and pc set to 255.255.255.0
      Have tried making it a manual IP, and it doesnt make a difference..
      3: get to the router software with no problems...
      4:Netgear WRN2000
      specifically this one.. http://www.bestbuy.c...outer&cp=1&lp=2

      I've been using this exact wireless device for years with no issues connecting to UR4-D's... this one was bought new for this tour along with 2 others to go in Racks with backline wireless... I can link up to 6 of them in bridge mode... 1 base unit and 5 remote stations


      Double wide rack..19 spaces per side
      its panel mount ethercon to the router mounted in the rack.
      router port 1 to a cisco switch,
      cisco switch hits 4 units of UR4-D and one output of the switch goes across to the other side of the rack to hit another cisco switch that is connected to the 6 PSM1000's

      It has been working fine for over a month on a Major touring act....(I do not wish to post details....but its sold out in arenas across the US and europe thru April with a stadium tour being scheduled for next year)

      literally, just stopped working correctly yesterday
      I've been connecting wirelessly to it the entire time...

      on a side note...I did have issues connecting wirelessly the other day due to too many other AP's broadcasting in the Venue....wasnt able to get any real range out of it.....common problem when a lot of wifi devices are present...so I ran a hardwired ethernet cable to it for the duration of the show and turned off the wireless side for the night

      in the mornings I will usually program using wifi since I'm sitting right on the rack usually and I'm syncing new frequencies every day

      I do all my coordination using a TTi Scanner and IAS software and Just use WWB6 to program and to monitor during the show....
      I have over 80 Frequencies to coordinate every day and WWB6 Just cannot do that many......doesnt even come close...
    • buhmanb
      Thanks for the information. I've spent some time in our lab working with a configuration similar to yours.

      4 UR4D
      6 P10T
      WiFi Router: NETGEAR WNDR3400, DHCP Server 192.168.1.2 - 192.168.1.100 / 255.255.255.0

      PC running Windows 7 Professional, WWB6

      I believe that you have come across a bug in WWB6 triggered by using multiple network adapters in a specific order.

      The behaviour of Windows 7 seems to trigger the problem more easily, but there is a work-around. And the WWB6 team should address the problem in a future release.

      Here is what I think is occurring:
      1. PC is connected via wired Ethernet. The WIRED adapter gets assigned an address, or has been manually configured to an address such as: 192.168.1.5 / 255.255.255.0

      2. WWB6 is run, and the Tools > Preferences > Netowrk dialog is used to select that WIRED adapter. WWB6 discovers ALL the devices.

      3. Ethernet cable removed, WiFi on the PC is enabled and connects to the router. The WiFi adapter gets assigned an address, or has been manually configured to an address such as: 192.168.1.3 / 255.255.255.0

      4. WWB6 is run, and the Tools > Preferences > Netowrk dialog is used to select that WiFi adapter. WWB6 discovers the P10Ts, but not the UR4Ds.

      Example Screen Shot:

      If you note from the screen shot, WWB6 still "thinks" the WIRED adpater is still configured to 192.168.1.5 The "SNET" protocol used to manage UR4s apperas to be confused at this point. The "ACN" protocol used to manage P10T, Axient, ULX-D, is not confused.

      Windows 7 appers to remember the last used settings even for automatic / DHCP mode.
      I've seen that after rebooting the PC, the Tools > Preferences > Network dialog still shows the "old" addresses.

      Try this Work-Around:
      1. Disconnect the Ethernet cable from the PC
      2. Reboot the PC and only use the WiFi connection to access the gear.
      3. WWB6 should discover all.

      There are other methods that can work-around the problem, but those are even more convoluted.

      Try it out - let us know if the work-around works as a temporary measure. At least that may confirm my theory.

      Best luck!
      -Brian
    • S2H
      I actually Tried that this morning before even seeing this reply...
      I remembered an issue with a different product that we use that sometimes has a similar issue... if more than one adapter is enabled, sometimes it gets lost and cant find all the devices...

      seems to have worked.

      definitely a bug that needs to be addressed.. I know most users will not turn on and off adapters.....I certainly hate to do it...what a pain in the ***...
    • Liam135db
      Hi Scott,
      rather than having to reboot, it might be worth trying a command line command.
      open a command prompt and try typing in "ipconfig /release"
      This should release all ip addresses from within windows.
      then trying to reconnect to whichever network.
      if you have only one active connection a handy cmd command to refresh the ipsettings is "ipconfig /renew"
      both commands should be used without quotes!

      I have not got an access point available to try this at the moment, but the two commands above have fixed a few ip related issues for me, so thought it might be worth mentioning.

      Hope this helps.

      Liam

     

    © 2009-2014 Shure Incorporated All rights reserved.
    • Privacy
    • Powered by RightNow