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 
    4465 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

    • jonhems
      Thanks for the prompt reply.

      We are in the middle of a conference so not possible to try everything you suggest immediately.

      To answer some of your queries,

      1. Yes, there are addresses available. I am able to get a valid address assigned by setting a manual IP and then reselecting automatic. It doesn't seem to be an issue receiving the IP, rather the unit is not asking for an address on start up but is returning to a default address (this is the address that was assigned when the unit was first powered on and had not connected to any network)

      2. We have no issues connecting multiple different laptops to this network with auto configured IP's on an ah-hoc basis.

      I dont have access to the switch utility but will ask my IT admin to check. Are there any particular things to look for in the network log?

      I will try the factory default thing next week when we have some down time. Hopefully that can work...
    • jonhems
      Forgot to add the router model.

      my local router is a Prolink PSW242G, but its connected to a building network so I dont think the prolink is the DCHP host.
    • buhmanb
      Thanks - having read your follow up comments - I don't think factory defaulting the ULXD4 would be necessary.

      The Prolink PSW242G is a GB switch, not a router. That isn't a problem.
      A couple other things to consider.

      Is the Prolink switch, and your ULXD4 being powered on at the same time? i.e. maybe all in 1 rack connected to a power strip?
      I have seen cases in our lab where various GB Switches that are connected a mix of 10/100/1000 MB devices that the Switch itself takes a long time to negotiate and enable the ports. Long enough that a device like the ULXD4 will "fall back" to an AutoIP address (169.254.x.x).
      The ULXD4 should, after a few minutes re-request a DHCP address. Depending on timing, and the DHCP server itself this may be 3-5 minutes.
      If the switch and your gear are on the same power source, can you try powering up the switch first and let it initialize. Then power up the ULXD4.

      Or - some IT departments don't like to have multiple devices connected to individual ports of their routers/switches. In some cases they can identify and disable ports if they see multiple MAC addresses at one port.
      The ULXD4 utilizes 2 or even 3 MAC / IP addresses, 1 for the main processor and a second (and potentially third) for the Dante card. When / if you talk to the IT person - make sure they know that the ULXD4 is going to need 2 IP addresses.

      The case of 3 - would be running Dante in a Redundant mode. Check out the user manual for a description of the Dante modes.
      I imagine that yours is setup to "Switched" mode.

      Best luck!!
    • rockyroadaudio
      Hello,

      The network is setup as described. The ping test works but the problem is:

      Launching wwb 6.4 everything works. All devices are discovered.
      Launching wwb 6.8.1no devices are discovered. The green light on bottom right is on but states that there are 0 devices online. Network preferences are set the same in both wwb versions.

      Using Mac OsX Lion 10.7.5
      Is there a way in the software to prompt a device search without quitting and relaunching?
    • rockyroadaudio

      Sorry for the hastened prompt on a problem. I have figured out the problems....

      My units have firmware version 1.150. Need 1.16 for WWB 6.8.1

      My Mac Pro is an Intel Core Duo. It has restricted network access due to old processors.

      I'll stay with WWB 6.4. It works fine in this version

    • ADRIAN HEREVIA

      can someone explain to me how to add a device that is not SHURE, I manually add it to WWB 6 but can not see it, how do I add the IP address on WWB6?

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