Can't connect to Squeezenetwork

[pEEf]

Ok, I shut down the PacketShaper. It's running in total bypass (physical relays on the ethernet ports).

I'll see what happens....

[xargs]

I've had my Squeezebox for three days now, and I've had two incidents of being unable to connect to SqueezeNetwork. I have the same symptoms reported by others here: I get the connecting screen, followed by a black screen, eventually followed by the setup screen.

In both cases, power cycling the Squeezebox has fixed the problem.

I've never had any issues connecting to my SlimServer.

[Coffee]

I've been experiencing the same black out problems that's been reported here. I just bought 2 SB3's because I thought it's a great product idea. Now I wish I had read the forums more carefully. I would have seen this thread and hold back on my purchase.

The whole SB seems flaky as hell. One of the SB's I bought for my mother near Mountainview, CA. The other I use myself in Vancouver, Canada. They both experience random disconnects at first. Then this black out thing and can't connect to SN thing happened. Occasionally the SBs even reboot and throw me back to the SB setup stage. Now the SB in Mountainview got stuck in the setup stage and nothing works anymore, not even the up/down buttons on the remote. Powering off didn't help. I've posted my problems in the Beginner forum, emailed SlimDevices tech support, phoned... no response from anybody. Did everybody at SD got rich from the Logitech acquisition and now they don't give a damn anymore or what???

[Coffee]

To be fair to SD, I finally did get a reply from their tech support, after 2 days. That's actually not too bad, even though with my frustration level 2 days seem a long time. I'll see if they can help me resolve the problems. I have a feeling, judging from what others have reported on this thread, that I may have to connect through SS all the time, thereby defeating one of the great features of the SB being usable as an internet radio without having to turn on my PC. We'll see how it goes...

[sensi]

I had the same problem and it was fixed by a friend.
Here is the solution that worked for me. It might be really simple for experts but for a beginner, that should help a lot.
Basically, it's a hardware problem and I give as well below a basic explanation of home networking and internet.
First, I did it wrong because I tried to connect my Squeezebox to a switch (it will be the same with a hub) and not to a router.
Thus, I had 2 devices (computer and SqueezeBox) trying to go on internet while my modem was giving only one ip adress.....

It will work only if your modem is a router at the same time, or if your modem is connected to a router (a router being a switch at the same time is of course more convenient).
In my case, I have the modem connected to the router (internet or Wan port), my PC connected to the router and the Squeezebox connected to the router (both on the switch ports).
1 - switch off your modem and your router
2 - reset your modem or wait for 2 minutes for the settings to disappear
3 - power on your modem then your router
4 - the router save ip address (the internet ip address) and dns address from the network (from your provider)
5 - set a fixed ip address for your computer and for the Squeeze box (then your Squeeze box will always see your computer because if you choose dhcp, it's not sure that your box will find easily your computer if this address change). Of course, these ip addresses are only for your home network and are not seen from internet. You might try to leave DHCP for your computer and your box, it should work.
6 - for dns addresses for your computer and your box, set instead the ip address of your gateway (ie your router). Your router obtained the dns address from the modem at step 4. You don't need to specify the real dns address in your computer and your box because the internet side is took in charge by the router. With this solution, your computer and your box are connected directly to the router, speeding up the connections. If you chose at step 5 to leave DHCP, skip this step 6.
7 - from your box, connect to SqueezeNetwork
8 - note your PIN
9 - from Slimserver log to SqueezeNetwork, and write your PIN
10 - done !

I hope this helps.

[Mark Lanctot]

First, I did it wrong because I tried to connect my Squeezebox to a switch (it will be the same with a hub) and not to a router.
Thus, I had 2 devices (computer and SqueezeBox) trying to go on internet while my modem was giving only one ip adress.....

A switch or a hub should work fine provided you have a gateway or router device upstream which provides LAN addresses (192.168.xxx.xxx, some other subnets) downsteam. Examples of these types of devices - modems (in gateway or router mode, not bridge mode), routers and gateway/firewall boxes (ClarkConnect, Smoothwall, monowall, proprietary boxes).

Then you can either use DHCP running in one of these devices or static addresses.

[xargs]

I found something that may be a clue to this problem. When my Squeezebox was in the "can connect to SlimServer/can't connect to SqueezeNetwork" mode, I sniffed the traffic on my SlimServer box. Traffic from the Squeezebox was using a 169.254.x.x IP address, and my wireless router/DHCP server did not show the Squeezebox as a DHCP client (it gives out addresses on 19.168.11.x). I couldn't understand how 169.254 traffic could even get routed to my SlimServer box, until I noticed it had a route for 169.254. I think this route, and the Squeezebox's bogus IP came from a VMWare installation running on the SlimServer box.

I've reconfigured VMWare to remove its DHCP server and deleted the suspect route. I'm hoping this is the solution.

[Mark Lanctot]

I found something that may be a clue to this problem. When my Squeezebox was in the "can connect to SlimServer/can't connect to SqueezeNetwork" mode, I sniffed the traffic on my SlimServer box. Traffic from the Squeezebox was using a 169.254.x.x IP address, and my wireless router/DHCP server did not show the Squeezebox as a DHCP client (it gives out addresses on 19.168.11.x). I couldn't understand how 169.254 traffic could even get routed to my SlimServer box, until I noticed it had a route for 169.254. I think this route, and the Squeezebox's bogus IP came from a VMWare installation running on the SlimServer box.

I've reconfigured VMWare to remove its DHCP server and deleted the suspect route. I'm hoping this is the solution.

? 169.254.XXX.XXX is the Squeezebox's fallback address - one it uses when it can't get a response from the DHCP server.

[xargs]

? 169.254.XXX.XXX is the Squeezebox's fallback address - one it uses when it can't get a response from the DHCP server.

It always successfully acquires an IP at startup, so if it's using its fallback IP, I have to assume it's somehow losing its DHCP-allocated address and unable to get a new one. I guess I'll check on it again tonight when its DHCP lease expires.

I'm still not sure how a route for 169.254 traffic could appear on my SlimServer Linux box. SlimServer doesn't have the necessary permissions to modify the routing table, and I'm not running any routing daemons.

[Mark Lanctot]

It always successfully acquires an IP at startup, so if it's using its fallback IP, I have to assume it's somehow losing its DHCP-allocated address and unable to get a new one. I guess I'll check on it again tonight when its DHCP lease expires.

I'm still not sure how a route for 169.254 traffic could appear on my SlimServer Linux box. SlimServer doesn't have the necessary permissions to modify the routing table, and I'm not running any routing daemons.

You may have hit on something though. Perhaps the Squeezebox momentarily loses contact with the network then can't find the DHCP server again?