Ethernet connection: No source found

[urbo]

I've run into some serious connectivity problems with my Squeezebox Duet. As I have not been able to get wireless working satisfactory with FLAC (probably due to physical constraints in the house and neighbourgs' WLAN networks), I need to establish an Ethernet network. However, although I can run 1 Gbps perfectly with a PC, the Duet cannot connect.

SYMPTOMS:
- The squeezebox cannot find the music source after the button color turned blue, after precisely following the manual instructions for a "bridged network configuration".
- SqueezeCenter cannot find the player.
- Player received IP-number according to router's admin interface

SOLUTIONS TESTED (unsuccessfully):
- Restarted player & controller to factory defaults
- Ports opened in firewalls of Windows as well as router according to the SqueezeBox manual.
- "Permit all" rule set for squeezecenter.exe in antivirus program

USED GEAR:
- SqueezeCenter (version 7.3.1) running on a Windows XP PC, with:
- Norton AntiVirus 2005
- NAS storage: D-Link DNS-323
- Router: D-Link DI-724GU (with both PC and SB connected), with DHCP activated
- Cabling (from router to SqueezeBox): Three brand new Ethernet cat5e 568-B cables; connected with one modular jack with 568B wiring, and one coupler. Total length around 25m.

Any help would be greatly appreciated.

All the best, /J.

[camore]

More information about your network infrastructure would help to be able to give you a solution.

Please specify the following points:

- Is DHCP activated on your router?
- Is the router for the wired connection the same as the one you're using for the wifi?
- are the squeezecenter services started on your windows machine (I don't know exactly how it works on windows, but in cmd you can run "netstat -na" to see if your pc is listening to port 9000)

cheers,

[urbo]

Thanks,
- Yes DHCP activated (and player visible with IP number received in router admin)
- Yes, the same router used for both player, PC and storage. (Wifi used for other computers, but only wired cabling for these devices.)
- Don't know about the service issue, but the command you suggest seems to indicate that the PC is "listening" to port "0.0.0.0:9000" among others.

[Pete Fowler]

I was in the same boat yesterday but for different reasons. I went through every combo I could think of or read about. Same symptoms you have.

Then on a hunch I unplugged the receiver from the ethernet cable and hooked it back up again. Apparently my router was hung on that connection because after the reconnect the receiver synch'ed up and was able to connect to SNetwork on the next try. Been fine for 18 hours now.

Worth a shot...

Pete

[camore]

How was the controller set up.

Has it been installed via your wifi or are you trying to install in bridge mode?

If you are trying to install in bridge mode it should work as it is.
If the SBC has already been installed via the wifi router, then it won't work.

Don't ask me why. Apparently the information which are sent from the controller to the receiver concerning the connection to the squeezecenter, are based on the topology which goes via the wifi router.

There is the following treat which poposes a solution: http://forums.slimdevices.com/showthread.php?t=57991

[urbo]

I unplugged the receiver from the ethernet cable and hooked it back up again. Apparently my router was hung on that connection because after the reconnect the receiver synch'ed up and was able to connect to SNetwork on the next try. Been fine for 18 hours now.


Thanks! I think I tried it already, but will give it another shot! All the best, /J.

[urbo]

Has it been installed via your wifi or are you trying to install in bridge mode?

Yes it was installed via wifi previously, but after the hard reset of player & controller no wifi - only bridge - was used.


Apparently the information which are sent from the controller to the receiver concerning the connection to the squeezecenter, are based on the topology which goes via the wifi router.

There is the following treat which poposes a solution: http://forums.slimdevices.com/showthread.php?t=57991

Thanks, however I don't think I understand this, or what you think I should try?

All the best, /J.

[urbo]

After a long time of troubleshooting, I've finally solved it by adding a simple Netgear Switch between the sqeezebox and the in-wall cabling. Although the cabling was fine for a PC, obviously the signal was too low for the Squeezebox.

Any plans for improving the squeezebox's Network Interface Card for future models?

/J.

[Lou1z]

my duet is running fine at 21m and is far more responsive than when the receiver was on wireless. i wouldn't have thought that 25m was too far for the receiver as its well within the limits of cat5.