This is a public Discussion Forum  public

Topic

    Sam Drazin
    What is wrong with my network configuration?
    Topic posted November 11, 2011 by Sam DrazinExpert, last edited December 10, 2013 by AdminProficient, tagged how-to 
    4424 Views, 26 Comments
    Title:
    What is wrong with my network configuration?
    Description:

    Overview

    This page will outline a set of tests and diagnostic measures you can run to ensure that your network is properly configured.

    The end-goal is to have a properly configured network such that Wireless Workbench discovers all Shure wireless devices online, and that your computer can effectively and reliably communicate with said devices. This page will act as a troubleshooting guide for debugging your network setup.

    Related Links

    Step 1: Selecting a Network Interface

    Wireless Workbench gives you the flexibility to choose which of your computer's network interfaces you would like to connect to. To inspect or modify which network interface Workbench is currently connected to, go to the Preferences menu and select the Network tab.

    To access the Preferences menu, select Tools -> Preferences.

    69c3c894c5_01.png

    From this display, all available network interfaces known to your computer are displayed. To view more details about a particular network interface, select the "Details" button next to one of the network interface options.

    69c3c894c5_02.png

    Once you have selected the network interface you'd like to use to connect to your devices, select "Save" to commit the change.

    Note: If you have configured your computer for both wired and wireless networking, the two IP addresses must be on separate subnets for WWB to work properly. The wired and wireless adapters on the computer should not be "bridged".

    Network Status Indicator

    Wireless Workbench offers a simple "Network Status" label that, at a cursory glance, allows you to assess the basic state of your connection to a network.

    The Network Status indicator is in the bottom right corner of the application, and is visible in all three tabs.

    69c3c894c5_03.png

    The Network Status indicator can read one of the following states:

    • Network Off: there is no network seen by your computer. If you see this, the network interface you've selected is either invalid, or disabled.

    69c3c894c5_04.png

    • Network On: there is a network seen by your computer, and the label will indicate the number of Shure wireless devices seen online.

    69c3c894c5_05.png

    When you first configure your network of wireless gear, this indicator can serve as a first-check of whether or not your computer sees a valid network or not.

    Step 2: Check your Computer/Hardware

    Pinging devices

    When configuring a network, you may find yourself in the scenario where you are not sure you have a valid connection to a particular networked device. Pinging a device is a precise way to discover whether or not a device is available on the network, regardless of other signs that it may or may not be exhibiting.

    First, isolate the device that you want to ping- you will need to get it's current IP address. On the device's front panel, access the Network menu. For Axient, PSM1000 and UHF-R rack devices, this menu can be accessed by selecting Util -> Network.

    69c3c894c5_06.png

    The device's IP adress will be listed next to the label "IP:".

    69c3c894c5_07.png

    If you are working with a UHF-R receiver, be sure to check the IP address on the left front panel, not the right. This is because the IP address for
    devices in DHCP (Automatic) IP mode is only listed on the left panel.

    Note the device's IP address. For this example, let's use the IP address of the AXT400 receiver above: 169.254.132.186.

    Next, open a command prompt on your computer. For Macs, this would be Terminal. For Windows machines, this would be Command Prompt.

    Type the following command:

    ping 169.254.132.186

    Press return. The results of this command will indicate to you whether your device is online or not.

    The ping command will send a small packet of information the IP address that you listed, and wait for a response. If none was heard, you will see messages similar to this:

    pcni4299al:~ drazins$ ping 169.254.0.1
    PING 169.254.132.186 (169.254.0.1): 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    ping: sendto: No route to host

    Notice that there was a "Request timeout". This indicates that your computer waited for a response for a certain amount of time, and none came.

    If your ping was successful, you will see a message similar to this:

    pcni4299al:~ drazins$ ping 169.254.132.186
    PING 169.254.132.186 (169.254.132.186): 56 data bytes
    64 bytes from 169.254.132.186: icmp_seq=0 ttl=30 time=0.863 ms
    64 bytes from 169.254.132.186: icmp_seq=1 ttl=30 time=1.086 ms
    64 bytes from 169.254.132.186: icmp_seq=2 ttl=30 time=1.120 ms
    64 bytes from 169.254.132.186: icmp_seq=3 ttl=30 time=1.050 ms
    64 bytes from 169.254.132.186: icmp_seq=4 ttl=30 time=1.088 ms
    64 bytes from 169.254.132.186: icmp_seq=5 ttl=30 time=1.183 ms

    Notice that each line after the PING command reads something like "64 bytes from 169.254.132.186". This is a sign that the device we pinged is on the network.

    If you're still not discovering devices in your inventory after a successful ping, check your firewall settings. Be sure to allow all processes listed in the "Firewall Setup" section of the Proper Network Setup through any and all security and firewall software your computer is running.

    If you ping a device and it does not appear to be connected on the network, some of your next steps should be:

    • ensure that there is a valid network connection from that device to your network (operational ethernet cables/ports, etc)
    • ensure that your computer is connected to the same network as the device you are trying to ping
    • ensure that the device itself is operational

    Common Mistakes

    Below is a listing of common mistakes made when setting up a network.

    • No two devices (including a computer on the network) can ever share identical IP addresses.
    • Ensure that all devices on your network share the same Subnet Mask. Consult the Automatic vs. Manual IP Mode section of this page for more details on proper IP/Subnet Mask configuration practices.
    • Do not connect a device to the same network twice, ie: via ethernet AND Wi-Fi. Connecting a device to the same network interface with two connections will not yield valid results.
    • Ensure that all devices on your network are set to the proper IP mode.
    • Check your ethernet cables and ethernet ports. Replace old cables and look for data transfer indicator lights on ethernet ports with LEDs to indicate such. If these lights are present but not illuminated, this may indicate a faulty or incomplete connection.

    Answer

    • AaronMorris
      I am networked to my ULX-Ds, I can see them in wireless workbench but in the monitor section I don't see RF or Audio deflection. What am I doing wrong?
    • buhmanb

      What version of WWB6 and ULXD4 are you using?

      Current versions are:

      - If you open the properties panel for the ULXD4 channel, do those RF/Audio meters match the meters on the physical ULXD4 units?
      - If you have other devices (i.e. UR4, PSM1000) do the meters work for those devices?
      - Right click on the Monitor Tab and open the Channel Strip Settings - make sure the parameter: ULX-D > RF Meter/Audio Meter has been selected
      - Make sure all desired channels have been added to the Channel Strip / Monitor Tab. Click on the Channels section of the Device Chooser to toggle.
      - Make sure you've given unique names to your channels. By default all channel names are "Shure" - so you might be looking at the meter for different unit. Unique channel names are not required - but does help in cases where there are multiple channels.
      - Make sure the devices are actually "online"
      - Look in the lower right corner of WWB - it will indicate "X Devices Online" - that should match the number you expect
      - An "offline" device will appear grayed out.

      Hopefully one of those items will help get you going, if not the answers will help take the next step to resolving.

    • UCSC_LTMV
      Can WWB6 find mic receivers across subnets, or does the computer running WWB6 need to be on the same subnet as the receivers? I have two receivers setup for testing and playing with before I add the rest of our receivers, but I am in my shop and the mics are on a different subnet and I am unable to find them. I am using static IPs.
    • buhmanb
      WWB6 needs to be on the same subnet as the gear that it is controlling.

      The protocols used by WWB6 and the devices for discovery and control utilize multicast packets (and broadcast in the case of UR4). So most routers will not propagate those packets across the 2 subnets.

      In addition, devices like the UR4 do not configure a Gateway address. Future firmware for ULXD, Axient, etc. will be able to configure their Gateway address, but not at the current time.

      One thing that I do is remote desktop or VNC to a computer that is on the same subnet as the gear. Then run WWB6 on that computer remotely. May not be exactly what you were after, but it has helped me.

      Best luck!
      -Brian
    • tristang
      I find this is a bad limitation not to be able to work across subnets. Is there any intention of this being fixed soon?
    • hautzir
      Can you get into detail related to what the benefit according to the application would be to be able to work on different subnets?
    • fohquack
      hey sam
      the wwb6 is wreaking havoc on my airport card on my mac book pro any thoughts?
      fohquack
    • buhmanb
      Hi - Can you be a little more specific about your setup and what problem you are having.

      For example
      * Macbook Pro running OSX 10.8.4
      * WWB 6.8.0.40
      Devices:
      * X number of UR4D units
      * Y number of AXT400 units
      etc.
      All devices are connected to a 24 port Netgear switch
      Also connected to the switch is a Netgear WiFi router which is used to provide WiFi access to the Macbook so WWB6 can be run remotely.

      Then describe the problem. i.e.
      Doesn't discover devices?
      WiFi signal goes in/out even in close range?
      ??

      Or are you trying to use an AirPort card on a Macbook Pro?
      http://support.apple.com/kb/HT1621
      according to Apple - that isn't supported.

      Just trying to understand the problem. Thanks!
    • jonhems
      I'm having a network issue with my ULXD4Q receiver.

      I am running through a router with the ULXD4Q set to automatic network detection.

      The issue i encounter is that on start up the ULXD is defaulting to a IP address 169.blah blah which is a long way off my 192.168.***.*** ip's in use on my network.

      I am able to resolve the issue by configuring a manual IP and then switching back to automatic IP. If I do this the unit will then take a correct IP.

      I do not wish to use static IP in the long run as there are a lot of users on my house network and its largely unregulated so concerned about IP conflicts. Wondering why the automatic mode is not actually working automatically.

      I am running the following

      ULXD4Q 1.3.6
      WWB 6.8.1.1

      Appreciate any suggestions/input
    • buhmanb
      What router is it?

      Can you verify your router has available addresses in its pool? Router often have a web based configuration utility that can tell you:
      1. The DHCP server settings
      2. A table of currently allocated IP addresses
      3. Potentially a log of activity

      You can also try:
      1. Set your computers wired Ethernet NIC to Automatic mode (disable WiFi, other adapters for this "test" - reenable as desired after the test)
      2. Plug the computer wired Ethernet NIC into port 1 of the router & verify your computer gets an appropriate address from the DHCP server. Then disconnect.
      3. Factory default the ULXD4 then power OFF.
      4. Plug the ULXD4's primary Ethernet port to port 1 of the router using the same Ethernet cable that was just used for the computer. Don't use the secondary port for this test.
      5. Power ON the ULXD4 and see if it gets an appropriate address(s) from the DHCP server.

      NIC: Network Interface Controller

      If that doesn't work... there are some other things we could try, but I hope this will get it.
      Best luck!
    © 2009-2014 Shure Incorporated All rights reserved.
    • Privacy
    • Powered by RightNow