This is a public Discussion Forum  public


    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 
    4463 Views, 26 Comments
    What is wrong with my network configuration?


    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.


    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.


    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.


    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.


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


    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.


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


    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:

    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:


    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
    PING ( 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
    PING ( 56 data bytes
    64 bytes from icmp_seq=0 ttl=30 time=0.863 ms
    64 bytes from icmp_seq=1 ttl=30 time=1.086 ms
    64 bytes from icmp_seq=2 ttl=30 time=1.120 ms
    64 bytes from icmp_seq=3 ttl=30 time=1.050 ms
    64 bytes from icmp_seq=4 ttl=30 time=1.088 ms
    64 bytes from icmp_seq=5 ttl=30 time=1.183 ms

    Notice that each line after the PING command reads something like "64 bytes from". 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.


    • coryallen
      Thank you for the detailed walk-through.

      Here's a hypothetical situation: In a minimalist setup (1 AXT400 with 2 AXT100 for example), is the receiver able to communicate with a computer running WWB6 with a crossover ethernet cable and manually assigned IP addresses (eliminating the need for a switch and DHCP server)?
    • Sam Drazin
      Cory, this setup should work just fine. Be sure that you configure your computer to the same subnet mask as the device(s) you plan to give manual IP addresses to.

      Also, note that any hardware devices (and your computer, for that matter) will retain any manually configured network settings until otherwise changed. If you later want to use a DHCP server to automatically assign IP addresses to multiple devices, both your computer and all associated hardware (networked gear, not portables) will need to be configured to automatically receive IP addresses.
    • mwebber
      Very helpful troubleshooting guide - this saved me having to call or email you when I ran into a small mystery today. I was connected directly to one AXT400 but it was not showing up on the inventory page. The network icon was green but showed zero devices. I was able to ping the device successfully, so I knew my network settings were correct. What I did not notice until going through those steps was that this particular AXT400 was still on firmware 1.7.5. Would it be possible for WWB to report that a connected device has old firmware, rather than it just not showing up in the inventory?
    • Sam Drazin
      ...Would it be possible for WWB to report that a connected device has old firmware, rather than it just not showing up in the inventory?

      Mike, I'm glad the guide was able to help you through this issue. We are currently working on making this information more readily available and obvious to the end-user. Thanks for your feedback.
    • musicmanf5
      I am seeing my network icon on my ur4d receivers and wwb6 but they are not showing up. I had a succesful ping. Firewall settings are good.Any ideas?
    • mwebber
      Matt, make sure your UR4D receivers have the most recent firmware installed. I think that will solve your problem.
    • psusound
      How can we update firmware on the UR4D?
    • buhmanb

      See the topic: Firmware Update UHF-R

    • tceriale
      i have set up 6 UR4D networked via a switch, there is also a wireless router connected handling the DHCP. my laptop is connected to the wireless network but i cannot see any devices. if i hard wire straight into the switch everything works fine. i just cant see anything when im connected to the wireless network. note this setup was tested in my company's wharhouse and worked fine with a mac, i have a windows system
    • buhmanb

      Hi Thomas,

      Make sure the proper network adapter has been chosen via Menu: Tools > Preferences > Network

      If you've already done this, and there is still a problem - take a look at this topic: UR4-D not showing up on Wifi

      I know that is a long post - but in summary the way Windows OS retains some information about both the wired and wireless adapter settings confuses WWB. A couple different work-around methods are listed in that post.

      Hope that helps!

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