sgmlaw wrote: > 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.
Thanks very much sgmlaw- The router shows the receiver with which I am working, which is connected to the Mac by ethernet, as active and the green light is on. I have tried rebooting everything several times I take your point about sound quality with wall plug devices. Only I of my 2 receivers works via wall plug and I am not working with that one, preferring to start with the ethernet-connected receiver. That said, I unplugged the wall plug device with no effect on the problem I did try to redo things by restoring factory settings on the controller may times and connecting it first to the network. No dice there, either. Based on past advice from Michael, I had shut down the firewall and made sure that perl and perl 5 had full disk access. I also shut down my security software-Bitdefender. Not sure what a PSU is, but I suppose the power cord could be the problem. I switched with the power cord for my other receiver and had no different result. I'm going to let this sit for a few days and then come back to it. Not optimistic. But thank you very much for taking the time to suggest to me some things I had not previously tried. They were very much worth a shot. Best regards. Dan McInerney ------------------------------------------------------------------------ [email protected]'s Profile: http://forums.slimdevices.com/member.php?userid=17776 View this thread: http://forums.slimdevices.com/showthread.php?t=116975 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
