PDA

View Full Version : Lights are on but nobody's home



asd123
2008-05-16, 03:39
I have owned Squeezeboxes for many years and have, from time to time, experienced problems that required me to delve into Network Administrator territory. I know little about computer networks and I don't care to know anything at all about computer networks, just as I know nothing about fuel injectors, but expect my car to start when I turn the key.

I have always been able to eventually fix the problems with my squeezeboxes, but this time, I've been unable to fix the problem and it's different than any of the previous ones, in which the players could not access slimserver. It's really getting frustrating, I'm at wit's end and I turn to you for help.

Unlike previous problems, my two Squeezeboxes successfully connect to slimserver. The date and time shows up on the screensaver and all functions work, except that the music library is completely empty.

I have an eMac running OS 10.4.10. When I start Slimserver (ver. 6.5.4), and click on "Web Access", the Slimserver control panel comes up and correctly lists the number of albums, artists and songs in my library. I use iTunes 7.

Sometimes the Players are listed, sometimes not. Clicking on "Server Settings" does nothing.

If I click on "playlists", the first few playlists show up, then nothing. After this, nothing works. Clicking on "Home" does nothing. Likewise, if I click on Player settings or any other link from the control panel, I can access any of the setting for the players, but clicking on "Home" does nothing.

As far as I can tell, all the IP settings are as they should be. The port number seems to change every time I restart Slimserver.

I downloaded SqueezeCenter today and installed that, but it won't run. I click on "Start Server" and after a few seconds, the button goes back to "Start Server". So I went back to Slimserver 6.5.4 and even tried 6.5.0, but with the same results.

The firmware for the players is version 81.

I would greatly appreciate any suggestions for troubleshooting this issue.

peter
2008-05-16, 04:49
asd123 wrote:
> I have owned Squeezeboxes for many years and have, from time to time,
> experienced problems that required me to delve into Network
> Administrator territory. I know little about computer networks and I
> don't care to know anything at all about computer networks, just as I
> know nothing about fuel injectors, but expect my car to start when I
> turn the key.
>


If you don't want to administer networks you shouldn't try setting one
up in your home.
When your car breaks down, you hire a professional. You have the same
option here.

Regards,
Peter

exile
2008-05-16, 07:31
My approach to your problem would first be to uninstall all aspects of slimserver. somewhere in this forum there's detailed instructions on how to properly uninstall on a mac. next, upgrade your os to osx10.4.11.

then I'd try to reinstall the latest version of squeezecenter.

hopefully a clean install in conjunction with updating your os will fix things.

good luck.

pfarrell
2008-05-16, 09:12
Peter wrote:
> If you don't want to administer networks you shouldn't try setting one
> up in your home.

The reality is that serious networking devices are moving quickly into
mass market, not just SqueezeBoxen, but Chumby, weather stations, and
all sorts of stuff.

The days when folks would have one computer directly plugged into the
cable/dsl "modem" are gone. Everyone has networks in their house.

Its not obvious when the line is crossed, that requires more than the
consumer can handle.

I have a six foot high, red roll around tool chest in my garage, along
with air compressors, floor jacks, etc. I used to love working on cars.
Probably because I was cheap, but it gave me satisfaction to do it and
know it was done right.

I have not worked on a car in about ten years. They are too complex, and
require tools that I don't have in my six foot high tool chest. What the
car designers have done is eliminate all of the simple maintenance, but
when it goes wrong, it really takes an expensive professional to fix.

I expect that networks will get there in the near future.


--
Pat Farrell
http://www.pfarrell.com/

danco
2008-05-16, 09:57
If you're going from SlimServer 6.5.4 to SqueezeCenter, you should probably remove the SlimServer cache.

There have been changes in the structure of the cache, I forget when that happened, and your symptoms are typical of a cache issue.

Why 6.5.4 isn't working properly I can't say.

peter
2008-05-16, 10:11
Pat Farrell wrote:

> I have not worked on a car in about ten years. They are too complex, and
> require tools that I don't have in my six foot high tool chest. What the
> car designers have done is eliminate all of the simple maintenance, but
> when it goes wrong, it really takes an expensive professional to fix.
>

Buy a 21 year old car like mine and you can go back to diy.

> I expect that networks will get there in the near future.
>

I'm not so sure. Setting up a network used to be much more difficult.
Now it's so easy that people are looking for more things to do with
them. More complicated things. I think the average SME LAN is less
complicated than what many of us are running at home.

Regards,
Peter

pfarrell
2008-05-16, 10:22
Peter wrote:
> Buy a 21 year old car like mine and you can go back to diy.

Yeah, I did my own on my 85 Mustang GT. It even had a carburetor.



>> I expect that networks will get there in the near future.
>
> I'm not so sure. Setting up a network used to be much more difficult.
> Now it's so easy that people are looking for more things to do with
> them. More complicated things. I think the average SME LAN is less
> complicated than what many of us are running at home.

For sure, a corporate LAN of 1995 was much simpler than a typical geek's
home LAN today. Back then, there was one operating system, usually all
of the PCs were the same brand and often model.


--
Pat Farrell
http://www.pfarrell.com/

CatBus
2008-05-16, 10:27
This is a networking problem, so to troubleshoot it we need information specifically about your network. The types of computers, operating systems, squeezecenter version, and squeezebox firmwares are all pretty much unrelated to the problem.

Are you using a wired network or a wireless network? If you're using a wireless network, does the problem go away when you connect everything up wired? If you're using a wired network, are any of your cables handmade or possibly damaged in some way? If you're using wireless, is your server connected to the WAP wirelessly as well as your Squeezeboxes, or is your server wired and your Squeezeboxes wireless? What channel is your WAP using? When you scan the networks in your area, what channels are they using? Etc etc.

Generally speaking, if you want something that always works and will never flake out on you, use a wired network. It may be a pain to set it up at first but, if you hate troubleshooting networks, it will be worth it.

asd123
2008-05-16, 16:37
I owned a 67 Mustang and did all the work myself too. Newer cars are much harder to work on, but fortunately much more reliable as well, so hiring a professional (at $90 an hour) isn't necessary very often.

Same thing with the Squeezebox. I'd love to have a professional fix the problem, but it's just not cost effective to do that. Whether I like it or not, it's a DIY fix or no fix.

To answer your questions CatBus, it's a wired network between an eMac and 2 Squeezeboxes via a D-Link DI-604 Router. No other devices connected to the network. None of the cables are hand made and I've swapped one out which I connected to another Mac and verified that the cable is good.

I'm no expert with networks, and usually I find some network setting I've never heard of has been changed for some reason and once I change it back, everything works. that's probably what's happened now. This time it's strange because the players connect perfectly fine and the Slimserver web access doesn't seem to be functioning properly.

I can access it right after I stop, then start Slimserver, but shortly after that, I can't even access it.

I did briefly have a glimpse at the server settings in the web access and it said the slimserver ip is 74.216.140.152. I think that may be the problem, but I don't know how to change that.

The last time I had issues and was able to fix them, I wrote down every network number I could find and they were:

Slimserver: 192.168.0.101
Subnet: 255.255.255.000
Player 1: 192.168.0.102
Player 2: 192.168.0.104
eMac: 192.168.0.101
Router: 192.168.0.1

Thanks,
Mike

CatBus
2008-05-23, 00:19
I honestly can't say. I thinking you're running into DHCP lease issues or your router is dropping packets or something arcane like that. If it helps, yes, this is the very sort of weird network problem you shouldn't have to sort out on your own. But it's definitely a networking problem.

Really, I have no clue. With all the time and money in the world, I'd just swap out parts until it starts working, and declare the most recently swapped-out device the broken one.

ds2021
2008-05-23, 06:55
The Server IP address is indicative of a network issue. It should be the same as your EMac. If an odd number is showing up, then the Emac may be losing the IP address assigned by the router (try lengthening or reserving the DHCP lease for the Emac).

Also, it seems that there are known issues with the DI604 and the Emac.

http://discussions.apple.com/thread.jspa?threadID=1371262&tstart=45

The solution could lie there.

Finally, I agree with Catbus about the componentry but would specifically start with the router. It is amazing how unreliable these things can be. For example. two days ago, I decided to undertake a network reorganization. I turned off wireless on my upstairs router and placed a router downstairs with DHCP off but wireless on (as most wireless activity happens downstairs and this will now extend to the yard with summer on its way). Theoretically sound, but wireless connectivity was highly problematic. Eventually, I swapped the routers (different models) and wireless worked instantly. FWIW, the router that was more reliable and which I now favour is the D-Link DIR655.

Mark Lanctot
2008-05-28, 06:12
I did briefly have a glimpse at the server settings in the web access and it said the slimserver ip is 74.216.140.152. I think that may be the problem, but I don't know how to change that.

The last time I had issues and was able to fix them, I wrote down every network number I could find and they were:

Slimserver: 192.168.0.101
Subnet: 255.255.255.000
Player 1: 192.168.0.102
Player 2: 192.168.0.104
eMac: 192.168.0.101
Router: 192.168.0.1

Your SlimServer is using a public IP. Earlier, it was using a private IP that your router assigned. So it seems that your router is no longer assigning DHCP addresses and has connected your SlimServer machine directly to the Internet. The Squeezebox may still have a private IP or it may be public if your ISP allows you to have more than one IP address (unlikely).

Your router is screwing things up, it's acting as a switch or hub, not a router. NAT and DHCP seem disabled and at least one port on your LAN is directly connected to the WAN (Internet).

Things are so seriously screwed up that a reset of your router wouldn't hurt. The only thing you have right now is Internet access, you have no file sharing as you appear to have no LAN and you have no protection/isolation from the Internet.

asd123
2008-05-29, 02:13
I think the problem is with the Slimserver software. I unplugged the router and plugged a Squeezebox directly into the Mac. Then I changed the network settings control panel to assign static ip's rather than DHCP. I set the Mac's ip to the same as Slimserver, except the last number. I reinstalled Slimserver and restarted the Squeezebox, which then downloaded new firmware. I started Slimserver, went to the web access and, as usual, it worked for about 6 seconds, then locked up. I can still use the Player settings web access for as long as I want, but as soon as I try to return to the server setting page, it locks up.

Maybe I'm missing something when I remove the old version of Slimserver. danco mentioned a cache. Is that removed when I remove the Slimserver control panel or do I need to find that and manually delete it?

I can't find anything wrong with the network settings and I think because the Slimserver web access is locking up that the problem is probably with the software somehow.

I appreciate the suggestions so far and if anyone can suggest something else, please do so.

Thanks.

Mark Lanctot
2008-05-30, 12:42
I set the Mac's ip to the same as Slimserver, except the last number.

How did you manage to do that? SlimServer's IP address is always the same as the machine it's running on.

CatBus
2008-05-30, 15:59
I agree with Mark. If your SlimServer EVER said its address was 74.216.140.152, something is really horribly wrong on the network, and I'd start with your router.

Phil Leigh
2008-05-30, 22:26
in player settings , check that the mac address of the sb really matches the sticker on the back/bottom (this is always worth doing before checking anything else, because if this gets messed up all sorts of strange things happen)

asd123
2008-05-31, 18:17
The MAC address matches the sticker on the player. I don't know how or where Slimserver is generating it's ip address. I can't check to see what it is now because web access won't do anything when I click on server settings anymore. Before, it gave me about 6 seconds to click on the link.

I removed the router and the player is connected directly to the eMac, so the problem isn't the router. I'm going to try installing slimserver on an laptop and setting up a network. Maybe the problem is with my Mac OS.

This whole time, the players have had no trouble connecting with slimserver, so the problem shouldn't be with the network. When I had network issues before, the players would say "unable to connect to slimserver". I would think that if the problem is with the network, the players would not be able to connect at all. And I don't know why the network would cause the problems I've had using web access.

I really think it's a software problem or something with the OS.

Thanks for all your suggestions.