Bugzilla – Bug 9653
Other Server function fails on fw 2873
Last modified: 2008-12-15 16:50:17 UTC
Reports of 3 Controllers that fail to connect to a specified server by IP. These are all happening at our Tier-1 facility in Phoenix: E4E. They description: "When entering in an IP address for SC manually, it allows you to enter the number. After you enter the last digit the cursor is over the ">." Pressing the center button to continue does nothing. You cannot continue. Using another controller with the same receiver works just fine. Also, when selecting "Music Source" does nothing as well." These all failed when they upgraded to r2873.
QA to investigate
Dan E. states "Tier1 reports that issue is gone. But what fixed it was RMA of the defective units"
Reopening bug. The issue is the Duet will not connect to his Linux box that sits outside of the local subnet provided by the Netgear router. even after specifying the server IP address.. The Linux box has a public static IP address from the customer's ISP. The router also has a static public IP address assigned to its WAN port. All the devices on the internal network, including the two Squeezebox Classics, can access the server without issues. The Duet is unable to connect to it as its music source. We verified that all the devices including the Duet are receiving proper IP addresses from the router's DHCP server. His network topology: Modem > Switch > Linux Fedora 9 w/ SC 7.2.1 installed > Netgear Router > Two SB Classics connected wirelessly > Squeezebox Duet connected to wireless network and to SN > Desktop connected ethernet
Additional Details: Router: Netgear MR-814 vs Controller FW: r3191, obtained update from SN Receiver FW: 48, obtained update from SN Please let me know if additional details are required.
Ross: can you work with TS on this one
Ping support. Do you guys still see this with 7.3? I've tested and I do not. Granted, we have issues with static IP's and Duet, but I'm not able to reproduce the problem in the original post of this bug. Note, bug 7502 is related to DHCP / static / Duet. Also, the only way static IPs will work with Duet is if there is no DHCP on the network. A partially working DHCP, or even DHCP not directly connected to Duet, will hinder static IPs from working.
Anoop -- can you check with Chad or Agustin at E4E. Is this still happening for them? That's the only place I've heard of reproducible cases. Julius-- can you check with your customer below? Still happen on 7.3?
Teir 1 has reported that they have not encountered this bug anymore.
Thank you Anoop. Please feel free to re-open.