[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-27 Thread killick
Hi, Mr. C. I spent some time on the phone with Kevin Pearsall (sp?) at SlimDevices. We didn't get the Squeezebox to connect to the server through the bridge, but we DID get it to connect wirelessly. The reason I had the bridge in the first place was that I was getting drop-outs during play. I'

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-27 Thread MrC
Damon, Have you resolved this? If not, have you tried connecting your SB directly to either your router or your server to eliminate the bridge? -- MrC MrC's Profile: http://forums.slimdevices.com/member.php?userid=468 Vie

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread killick
Hi, Mr. C and snarlydwarf, Thanks for helping me solve this issue. I miss having music in the house. I don't any wireless devices I can connect to the bridge besides the Squeezebox. The bridge is on a shelf 6 feet off the floor and I don't own a laptop. The bridge is connected only (ever) to

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread MrC
killick, Adding to what Snarlydwarf indicated, your Router's DHCP client list is indicating that the MAC address associated with 192.168.2.4 starts with 0050fc, which is registered to EDIMAX, a Taiwanese company. Both MAC addresses of your bridge indicate its a Belkin unit (0030BD and 001150).

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread snarlydwarf
killick Wrote: > Are you saying my router should list the bridge's MAC address at > 192.168.2.4? (and which, wlan or lan?) If that's not what you mean, > then what do you mean? :-) > Yes, that's normal behavior for a bridge. They often present their own MAC ID to the world for any IP behin

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread killick
Thanks for looking at this, snarlydwarf. But I'm not sure what you mean here when you say: "The only odd thing: it doesn't match either address listed for your bridge. It should." Are you saying my router should list the bridge's MAC address at 192.168.2.4? (and which, wlan or lan?) If that'

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread snarlydwarf
killick Wrote: > > The SB2 is wired to a Wireless Ethernet Bridge, which does not appear > to have it's own IP address, but has two MAC numbers labeled on it's > base: WLAN MAC 0030BD-FE26FA and LAN MAC 001150-0276A3. The bridge > connects to the router wirelessly. > That's normal: bridges sho

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-23 Thread killick
OK, here goes. --> wire **> wireless Slimserver-->router***>Wireless Ethernet Bridge-->SB2 My SB2 obtained via DHCP 192.168.2.4. It's menu MAC and label MAC are the same-- 00:04:20:05:85:58. The SB2 is wired to a Wireless Ethernet Bridge, which does not appear to have it's own IP address, but

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-20 Thread killick
OK, here goes. --> wire **> wireless Slimserver-->router***>Wireless Ethernet Bridge-->SB2 My SB2 obtained via DHCP 192.168.2.4. It's menu MAC and label MAC are the same-- 00:04:20:05:85:58. The SB2 is wired to a Wireless Ethernet Bridge, which does not appear to have it's own IP address, but

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-20 Thread MrC
killick Wrote: > My router believes my SB2 IP address is 192.168.2.4 with a hex mac > address of x. > > My bridge at that IP has a MAC of y. > I have to admit, i'm a bit confused about your setup. But your bridge and SB2 should not have the same IP addresses. Perhaps I'm misunderstanding the

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-20 Thread killick
Hi, folks. Thanks for helping me out on this. My router believes my SB2 IP address is 192.168.2.4 with a hex mac address of x. My bridge at that IP has a MAC of y. The SB2 label says the MAC should be z and the SB2 setup menu agrees that the MAC address is z. (Kits, cats, MACs and wives, how

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-19 Thread MrC
killick, I think you've misunderstood Kevin P. He was asking you to verify that the MAC address printed at the bottom of the SB2 matches that shown on the SB2s menus under Settings->Information->Player Information. If it does not, press Right, and change it to the address written on the bottom

Re: [SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-19 Thread Pat Farrell
killick wrote: Kevin P. at Slim Devices support gave me instructions to make sure that the SB2 MAC address matched the address on the bottom of the unit. But what should match to what? SB2 setup MAC address does match the ethernet MAC address on the bottom of the unit, but... Then you are don

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-19 Thread killick
Kevin P. at Slim Devices support gave me instructions to make sure that the SB2 MAC address matched the address on the bottom of the unit. But what should match to what? SB2 setup MAC address does match the ethernet MAC address on the bottom of the unit, but... My SB2 is plugged into a Wireless

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-18 Thread killick
Thanks for the idea, Wild Coder. I tried specifying an IP address but had no luck. Softsqueeze is working, DHCP is working, but the Squeezebox won't connect to the server. Do you or anyone else have any ideas here? -- Damon -- killick

[SlimDevices: Unix] Re: softsqueeze connects, squeezebox no longer connects

2006-01-18 Thread WildCoder
Not sure if it's related or not, but last week I installed slimserver for a friend who just got a squeezebox and it wouldn't connect to the server. The problem was that for some reason it wouldn't find the dhcp server so it grabbed a bad pre canned ip. There was 3 other computers on the network w