View Full Version : SD and PC
Can one connect the Squeezebox Controller directly to a PC using a crossover cable? Meaning no LAN and no router.
snarlydwarf
2008-12-11, 11:56
Can one connect the Squeezebox Controller directly to a PC using a crossover cable? Meaning no LAN and no router.
The controller? No, it is wireless only.
The Receiver? Sure, you can use a crossover cable, though there would, technically, be a lan (with two devices, the SBReceiver and the PC).
The Controller could then connect to the the SBR via the wireless that is internal to the SBR, and therefore be a 3rd device on the network.
(Controller) <-wireless-> (Receiver) <-wired-> (PC)
The SBR is smart enough to allow the controller to talk to the PC (sort of a mini-access point, using what is called 'ad-hoc networking') so you don't actually need a 'proper' wireless network.
You would still have a network though. No way around that, but, then you don't actually need a hub/switch/access point.
Thanks. I meant the receiver. The key is I will be using this in my work office. I will have a PC, the SBD, a home audio receiver and JBL speakers. No connection to the company LAN allowed.
OK, got the Squeezebox. The online user docs say:
Next you’ll see the Wireless Connection screen, where you can
choose to “Connect using Squeezebox” or “Connect using other
wireless network”. Since you will be using the bridged installation,
you should select “Connect using Squeezebox.”
I don't have Connect using Squeezebox. I have montana and Other. I am guessing montana is a WiFi network somewhere in the neighborhood. If I select Other it wants a name.
I am stuck.
Is the SBR hooked up to the wired network correctly?
I managed to get the whole setup working when the Receiver was connected to a router. I now have the Receiver connected to a PC using a crossover cable. The PC is not connected to a network. The SqueezeCenter shows the server as 127.0.0.1. I have put that IP into the Controller. I tell the Controller to connect but it never does. The light on the front of the Receiver is blue. There is activity between the PC and the Receiver as I see the green ethernet light blink.
I managed to get the whole setup working when the Receiver was connected to a router. I now have the Receiver connected to a PC using a crossover cable. The PC is not connected to a network. The SqueezeCenter shows the server as 127.0.0.1. I have put that IP into the Controller. I tell the Controller to connect but it never does. The light on the front of the Receiver is blue. There is activity between the PC and the Receiver as I see the green ethernet light blink.
127.0.0.1 is the special "loopback" IP address. It makes a computer refer to itself, which is why it works on the PC that is running SC. But it doesn't work on the SBC because you're pointing the SBC to itself, and obviously it isn't running SC. You need to give the PC an IP address (maybe it already has one -- check under your network settings on that PC) and once you find that address, point the SBC to that.
Millwood
2008-12-12, 12:38
I managed to get the whole setup working when the Receiver was connected to a router. I now have the Receiver connected to a PC using a crossover cable. The PC is not connected to a network. The SqueezeCenter shows the server as 127.0.0.1. I have put that IP into the Controller. I tell the Controller to connect but it never does. The light on the front of the Receiver is blue. There is activity between the PC and the Receiver as I see the green ethernet light blink.
I think you need to reset the receiver. Hold the botton on the front till it flashes FAST red. I would also factory reset the controller if you've been using it on the lan.
aubuti:
I had the PC set to fixed IP 192.168.0.25. Are you saying I should have put that address in the Controller when it asked for the IP address?
I stuck a router in the setup. No WAN connection. Just the Receiver and the PC on the LAN side. All working now.
I will try the crossover cable setup again and point the Controller to 192.168.0.25.
Millwood: Every time I try something I start by resetting the Receiver AND Controller.
Well, I tried setting the IP to the PC IP address. No go. The Controller would just not give me an option to use the Receiver as a music source.
As far as I am concerned the Receiver cannot be used connected directly to a PC. It has to go through a router.
snarlydwarf
2008-12-14, 18:35
Well, I tried setting the IP to the PC IP address. No go. The Controller would just not give me an option to use the Receiver as a music source.
As far as I am concerned the Receiver cannot be used connected directly to a PC. It has to go through a router.
Well, that is just plain wrong...
My server: 192.168.2.2
SBR: 192.168.2.10
SBC: 192.168.2.11
Netmask 255.255.255.0
All talk just fine to each other without a router.
(Actually, the server itself is a router, but that is another story and another Ethernet interface...)
snarlydwarf:
What IP is shown in SqueezeCenter settings ControlCenter Settings for the Server IP Address? Are you sayingt it was 192.168.2.2?
For me, when using a crossover cable it was always 127.0.0.1.
How did you get your PC to assign IP addresses?
snarlydwarf
2008-12-14, 19:14
snarlydwarf:
What IP is shown in SqueezeCenter settings ControlCenter Settings for the Server IP Address? Are you sayingt it was 192.168.2.2?
For me, when using a crossover cable it was always 127.0.0.1.
How did you get your PC to assign IP addresses?
In Linux: ifconfig eth0 inet 192.168.2.1 netmask 255.255.255.0
On Windows: look at the network card properties on Windows.
Assign your Ethernet card an IP and netmask (you don't need a gateway, since you're not trying to talk to a router). The netmask has a 1 in each binary digit that is part of the same network...
So: IP = 192.168.2.1 and netmask 255.255.255.0 means "everything on 192.168.2.X is this network and I can talk to it directly"
OK, PC ethernet port is set to 192.168.2.1 subnet 255.255.255.0.
Plug in Receiver using a crossover cable. Push the front button until it blinks red fast. Get a message from Windows that a cable is unplugged. Then get a message that network is connected at 100mbps. At this point SqueezeCenter says server is 127.0.0.1.
What in Windows assigns IP addresses? When does it get a 192.168 address?
Did a factory reset on the controller. Select English. Select United States. It starts searching for wireless networks. Does not find any so I have to select Other. Next screen wants the wireless network name. I don't have one.
Finally got a controller screen that recognized the Squeezebox. Selected it but it wants a server address. I put in 192.168.2.1 and nothing happens.
Like snarlydwarf said, in XP you set the IP address using Network Properties (eg, Start > Control Panel > Network Connections > right click your ethernet adapter). To confirm what IP your ethernet gets, open a command window and type "ipconfig" to confirm what you have for IP and netmask.
The PC is set to 192.168.2.1 sub 255.255.255.0
What service/program/etc in XP gives the Receiver an IP address? It still shows 127.0.0.1
Success!!!!
I had to set up the PC networking such that other computers used it to 'connect' to the network. I believe this is called ICS.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.