[email protected] wrote: > I upgraded my iMac (with the silicon chip) to Ventura last week and, as > with most recent Mac OS upgrades, LMS and my players will not work > without putzing around after installing the upgrade. Upgrading to LMS > 8.3 did not change the situation. > > My Squeezebox is a Duet, with 2 Squeezebox receiver players and several > other players (2 Apple TVs, my AVR receiver) have been added to the 2 > Squeezebox receivers. I run the Duet in hybrid mode, with LMS on my Mac > connected to one receiver (feeding into my AVR) with ethernet cable and > the other receiver being connected via wall plug ethernet. The music > library on the Mac is contained in an external hard drive connected to > the Mac. > > After installing 8.3 and granting it full disk access and getting around > the Mac firewall, LMS on the Mac sees the non-Squeezebox players, but > not the Squeezebox receivers. LMS will not play through to these > receivers, however, showing my library only on the Mac. LMS "plays" on > the Mac, but no sound emanates from the Mac's speakers. > > I have attempted to access one of the Squeezebox receivers via the Duet > controller and I can get it connected via ethernet, and it sees my > library on my Mac, but it cannot connect to the library. > > The preference pane Michael shows above seems substantively the same as > mine. > > Trying to make things work through the terminal, as Michael suggests, > failed. > > I cannot successfully access the scanner log, apparently. > > Would appreciate any insight people would care to offer regarding > resolving this problem I am a retired lawyer, not a tech guy. > > Thank you
I have a large contingent of Squeezeboxes, of most models. Even Ethernet-connected, the model that presents the most difficult network issues are the Receivers. Even the AX Router Wi-Fi incompatibility issue with Squeezeboxes pales in comparison at times. So you are not alone with your struggle. My suspicion is that this is not an LMS issue, but a networking one. A first step is to go into the Router administration portal and check the connected device table. Make sure there is not an active IP address conflict involving that client. Also, make sure that the Receivers are coming up in the tables. If they're not, that's a giveaway. A Receiver will also give itself away by its status lamp. Unless the lamp is out (connected, off) or a soft white (connected, on), it is not connected to the network. Unfortunately, even the status lamp is not dispositive of functional networking with the Receivers. Next go around your local network, and starting with the server machine, reboot that machine, and then reboot all the SB clients. Temporarily remove power line networking from your setup. Unplug the power line modules and connect the Receivers directly to the Router to eliminate that trouble source. One aside about power line networking if you are an audio enthusiast. Those plug-in modules inject a tremendous amount of broadband noise on their mains lines, some of which can get into the power supplies of your audio equipment. And yes, it can be audible. I've used them as an absolute last resort where a Wi-Fi media bridge won't work. But the line noise is a high price to pay, and line filtration is often required to get rid of it. If you can pull it off with an EX2700 wireless media bridge (802.11n), that is the cleaner solution. Some other initial steps are to clear the IP table on your Router. Sometimes, that is as easy as a Router reboot. Eventually, if you do nothing, a Router will clear itself via lease renewals, but that can take days. Once the table is cleared, the router's DHCP server will reassign the clients on reboot without conflicts. Even absent an obvious conflict, clearing the Router's assignment table sometimes gets a client working again. However ... sometimes it takes repeated attempts with the Controller to properly configure a Receiver to a network. And that is the only way to get it to connect. Don't ask me why this is, but it can be so at times. And absent some obscure terminal commands, the only effective way to do it is with a Controller. Make sure the Controller is on your network first before configuring the Receiver. And as a long-shot, you can try this (as it once coincided with some lingering networking issues on a Receiver): if the PSU is original, replace it. As these old wall warts fade, they can create some issues before they finally die. We had one Receiver exhibit increasing network disconnects and networking difficulties in the month or so before the PSU finally died. Once a fresh PSU was attached, it has worked perfectly ever since. Because you are also experiencing playback issues at the server machine, the other thing to make sure of, as has been alluded, is that all the Mac's disk access protections involving LMS are disabled. That primarily involves allowing full disk access for Perl and Perl5. If you are running a software firewall on your Mac, I suggest turning it off if you already have a hardware firewall at the Router. In their increasing zeal for 'security', recent iterations of MacOS have made networking (and even local external disk access) increasingly complicated. Also, in the very rare chance that you are running any third-party AV/anti-malware software on your Mac, temporarily disable it. I mention these MacOS issues secondarily, because if you can see your library anywhere, that means that MacOS is allowing LMS to start and granting it sufficient disk access to do so. While it likely won't solve your present issue, another tip for fewer networking problems down the road is to assign the server machine a fixed/static IP address. ------------------------------------------------------------------------ sgmlaw's Profile: http://forums.slimdevices.com/member.php?userid=13995 View this thread: http://forums.slimdevices.com/showthread.php?t=116975 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
