Troubleshooting Network Issues

General Notes

Internet connection is not required for AudioFetch to work. However, internet connection is recommended for better user experience.

1. Some mobile phones can experience difficulty remaining connected to WiFi if no internet. The mobile device may want to hop to an internet connected WiFi. If you are on a non-internet connected WiFi network for AudioFetch and experience the mobile device hopping to a different WiFi, you can solve this issue by turning off “Auto-Join” under the other WiFi network setting.
2. When first installing the AudioFetch App, you must accept the permission “Allow AudioFetch to Access LOCAL NETWORK”. You can check this setting in your mobile device within the Settings tab of AudioFetch.

Symptom

Troubleshooting

Is the WiFi using “Captive Portal”? (splash screen or login page)

1. All AudioFetch boxes must be whitelisted in the Access Point and/or Router to bypass the captive portal.

Is AudioFetch box connection to network wired? (Ethernet Cable)

1. Check that cable is good, plugged in securely on both ends, and plugged into active port on network router or switch. Try connecting another network device, notebook computer, etc. into the same cable to confirm it is working. Try changing cable, changing Ethernet port.
2. Check configuration settings of the network Router and/or Switch: ensure the Ethernet port is enabled and DHCP is enabled.
   1. If DHCP not enabled on network, then set manual IP address in the AudioFetch Doghouse
3. Are Access Points (such as Meraki) operating in NAT mode? If so they must be reconfigured to operate in Bridge Mode.

Is AudioFetch box connection to network wireless? (FetchExpress in Wireless Client Mode)

1. Is 2.4 GHz band available? FetchExpress can only connect into a 2.4GHz WiFi network.
2. Double-check SSID/Encryption/Password information provided at time of FetchExpress order match the current WiFi settings exactly. If not then re-configure FetchExpress with correct SSID/Encryption/Password settings which match your WiFi network.
3. Check that existing WiFi network is operating (connect another device to confirm), try adjusting FetchExpress antenna position then power cycle, try moving FetchExpress closer to Access Point temporarily then power cycle.
4. Reconfigure FetchExpress Wireless Client Mode SSID/Encryption/Password settings (in case they are incorrectly configured), see FetchExpress Quick Troubleshooting Guide: Wireless Client Mode WiFi SSID & Password.

Symptom

Troubleshooting

Check these first:

1. Ensure the mobile device (running AudioFetch App) has WiFi enabled and is connected to the correct WiFi network.
2. Check that AudioFetch App is updated to the latest version.
3. Ensure “client isolation” is disabled in the Access Point or Router configuration settings.
   1. Or if available in Access Point/Router settings: add each AudioFetch box to Client Isolation Whitelist.
4. Some Access Points such as Ubiquiti have a setting called “Guest Policy,” try disabling this.
5. Some Access Points have a setting to “Enable Multicast,” try enabling this.
6. If using FetchExpress in Wireless Client mode, ensure it connects into same network (or same VLAN) as users connect to.
7. When connected to the user WiFi network (with PC or mobile device), can you successfully ping the IP address of the AudioFetch box? If not then review/adjust network settings (VLAN, Firewall, etc.) as needed to make pings work.

Do users connect to a “guest” WiFi network? (good to check all these points even if not using a guest network)

1. Ensure all AudioFetch/Express/Home boxes are configured as public/visible devices on guest network. (check config. settings of Access Point/Router)
2. If AudioFetch box is using wired/Ethernet connection, ensure Router forwards all traffic between the guest network and Ethernet port.
   1. Try mapping the Ethernet port directly into the same subnet or VLAN as users connect to.
3. Try moving users and AudioFetch boxes to a standard (not guest) WiFi network, such as the main WiFi of a Wireless Router.

Do users connect to different subnet(s) than AudioFetch boxes are connected to?

1. Use a single subnet or VLAN for users and AudioFetch boxes.
2. If separate subnets are required:
   1. Network must forward all traffic between user mobile devices and AudioFetch boxes on the different subnets: Either:
      1. Multicast must be forwarded between subnets; or
      2. DNS discovery must be used (see Alternate Discovery Methods section)

Does the AudioFetch box respond to a “ping” from a user device (or tablet/PC connected to the user WiFi)?

1. No – The network is blocking most or all communication between AudioFetch box and user WiFi, this must be resolved.
2. Yes – The network is blocking only some of the communication, usually, it is blocking multicast traffic; Either:
   1. Multicast must be allowed; or
   2. DNS discovery must be used (see Alternate Discovery Methods section)

Other things to check:

1. Are Access Points (such as Meraki) operating in NAT mode? If so they must be reconfigured to operate in Bridge Mode.
2. Does Access Point and/or Router have a firewall enabled which blocks traffic between users and AudioFetch boxes?; Either:
   1. Whitelist AudioFetch boxes; or
   2. Add rules allowing all AudioFetch traffic (see AudioFetch App Note: Network Quick Start Guide)

AudioFetch App seems to start correctly (no error messages) but audio cannot be heard.

 

 

ALTERNATE DISCOVERY METHODS

 

The AudioFetch App tries to discover AudioFetch boxes using IP multicast communication. If the network blocks multicast traffic and it cannot be enabled for some reason, then the network must be configured to allow one of these alternate discovery methods:

DNS

1. The AudioFetch boxes must be assigned fixed/static IP addresses:
   1. This is usually done by configuring the network DHCP server to reserve static IP addresses for each AudioFetch box’s MAC address.
2. Double check that each AudioFetch box is configured with a unique box letter in each of the Doghouses (Multi-Box Setup page)
3. The network Router must be configured to run a Local DNS Server (consult Router manual or contact manufacturer’s tech support)
   1. For example, Cisco Small Business Routers can be configured through their GUI setup with “DNS Local Database” which is a local DNS server.
4. The Local DNS Server must be configured with manual entries for each of the AudioFetch boxes, each box must be given a unique hostname in this format: audiofetch, audiofetch-2, audiofetch-3, audiofetch-4, etc.
5. For more information, consult the AudioFetch App Note: Network Details

SSDP Fallback

1. In some cases where multicast traffic is generally restricted from or between clients on the WiFi network, it may be possible to open up one-way multicast traffic from the AudioFetch box(s), which will allow the AudioFetch system to work.
2. Is AudioFetch box connection to network wired? (Ethernet Cable)
   1. Check network Router settings and configure to allow multicast from the AudioFetch Box(s).
   2. Check Access Point settings and configure to allow multicast from the wired connection through to the WiFi.
3. Is AudioFetch box connection to network wireless? (FetchExpress in Wireless Client Mode).
   1. Check Access Point and/or Router settings to determine if it is possible to enable (whitelist) multicast from the AudioFetch box(s).