Just one request to the OP: please change the subject of this thread to
reflect the current problem status :)
--
ymilner
ymilner's Profile: http://forums.slimdevices.com/member.php?userid=1370
View this thread:
I was able to get multiple receivers working properly after ensuring
all receivers and the PC running SqueezeCenter were on the same
subnet.
IMHO a note of apology to the Slimdevices team would be appropriate,
after claiming their product set-up was 'horrific' and that you
'imagine the average
Good Point - perhaps you could change the thread title to
horrific experience caused by self-inflicted injury to my
network...or something like that :o)
--
Phil Leigh
You want to see the signal path BEFORE it gets onto a CD/vinyl...it
ain't what you'd call minimal...SB3+Stontronics PSU -
Good news! I was able to get multiple receivers working properly after
ensuring all receivers and the PC running SqueezeCenter were on the
same subnet. Thanks to everyone for your kind help.
--
doggieflyer
doggieflyer's
doggieflyer;316345 Wrote:
Good news! I was able to get multiple receivers working properly after
ensuring all receivers and the PC running SqueezeCenter were on the
same subnet. Thanks to everyone for your kind help.
Hurray - another success story. Good news.
Another one for the How to
doggieflyer;316077 Wrote:
Good info everyone. Fortunately I do understand all you're saying.
Putting on my generic user hat, Logitech needs to simplify network
handling because most users won't know DHCP from ABC. I'd have no clue
that I was running two DHCP servers if I didn't have a
maggior;316415 Wrote:
I have a DSL modem connected to a Linksys wireless router. I have a
Verizon DSL gateway (DSL modem, router, and wireless access point all
rolled into one) that they sent me. I needed a hub to expand my
connections and decided to see if I could configure the Verizon
JJZolx;316429 Wrote:
If you just needed additional network ports you should have added a
network switch, not a router.
Quite true, but if you need a switch but have a spare router sitting in
the loft, why not use its built in switch.
I had exactly this situation - I needed a switch to make
JJZolx;316429 Wrote:
If you just needed additional network ports you should have added a
network switch, not a router.
Yes, you are right. However, as Chill pointed out, you can use a
router in a pinch - as long as you configure it correctly. It was
sitting around collecting dust so I
maggior;316476 Wrote:
Yes, you are right. However, as Chill pointed out, you can use a router
in a pinch - as long as you configure it correctly. It was sitting
around collecting dust so I figured I'd put it to some good use.
This was a temporary arrangement as well as a learning
JJZolx wrote:
It's easy to screw up something
that would otherwise be extemely simple with the right (and less
expensive) equipment.
To be clear, I think what Jim is trying to say is:
Sometimes fancy equipment can make an easy job hard. Many times, a dumb
switch or even a simple hub is a
doggieflyer;315933 Wrote:
#2 Why is the product so stubborn about using wireless when an Ethernet
cable is attached? Even the controller wording tells you to get within
reach of a wireless network when an ethernet connection attempt fails.
Why on some setup attempts do I not get the option
I have a D-Link broadband router to which all the cables are
wired...The Squeezebox system gave me many fits without a wireless
router so I went and bought a new wireless router
Have you ensured that only one of the routers is a live DHCP server and
that the devices aren't otherwise in conflict?
doggieflyer;315933 Wrote:
I've spent 14 hours over the last two days trying to get this system to
work. I can't begin to explain the amount of inconsistent behavior
I've experienced.What you've described in your post is more or less identical
to the
behaviour I've been experiencing with my
egd;315991 Wrote:
What you've described in your post is more or less identical to the
behaviour I've been experiencing with my Controller and Receiver, wired
and/ or unwired.
I don't have any answers, but I share your frustration - and have
shelved the Duet hoping that in around 6 months
Thanks for all the responses and ideas. One that a couple of you hit on
I will definitely try.
The wired and wireless routers I think both are providing DHCP. I can
tell because the IP range on the wired is 192.168.0.x while those
connecting to the wireless show 192.168.2.x. I will try to
doggieflyer;316039 Wrote:
Thanks for all the responses and ideas. One that a couple of you hit on
I will definitely try.
The wired and wireless routers I think both are providing DHCP. I can
tell because the IP range on the wired is 192.168.0.x while those
connecting to the wireless
Phil Leigh wrote:
oh - I think you only want one device handing out DHCP on your
network...and you want everything on the same subnet (well at least you
need to guarantee that your SC server, router and duet are all on the
same subnet)
Other than that it's the default setting on most network
Phil Leigh wrote:
oh - I think you only want one device handing out DHCP on your
network...and you want everything on the same subnet (well at least you
need to guarantee that your SC server, router and duet are all on the
same subnet)
I'll be stronger than Phil. You really *must* have only
ftlight;316047 Wrote:
Phil Leigh wrote:
oh - I think you only want one device handing out DHCP on your
network...and you want everything on the same subnet (well at least
you
need to guarantee that your SC server, router and duet are all on
the
same subnet)
Other than that it's
Phil Leigh;316044 Wrote:
you need to guarantee that your SC server, router and duet are all on
the same subnet
Before someone reads that and takes it as gospel, you don't _need_ to
have SBC + SBR + SC all on the same subnet, it just makes things easier
if they are.
--
andynormancx
Yes, it
Phil Leigh wrote:
ftlight;316047 Wrote:
Phil Leigh wrote:
oh - I think you only want one device handing out DHCP on your
network...and you want everything on the same subnet (well at least
you
need to guarantee that your SC server, router and duet are all on
the
same subnet)
Other than
andynormancx wrote:
Pat Wrote:
you*must* be on the same subnet.
Before someone reads that and takes it as gospel, you don't _need_ to
have SBC + SBR + SC all on the same subnet, it just makes things easier
if they are.
OK, I'll let your weakening hold, I'll just say it
If you don't have
pfarrell;316060 Wrote:
it sometimes becomes impossible for mortals to make work.
Thankfully most mortals aren't going to have more than one subnet ;-)
--
andynormancx
Yes, it will. Yes, all of them. Yes, SoftSqueeze as well. What ?
I SAID ALL OF THEM !
andynormancx;316054 Wrote:
Before someone reads that and takes it as gospel, you don't _need_ to
have SBC + SBR + SC all on the same subnet, it just makes things easier
if they are.
Andy - I know it is not mandatory...I'm just trying to simplify things
for a few people. When do you REALLY
Good info everyone. Fortunately I do understand all you're saying.
Putting on my generic user hat, Logitech needs to simplify network
handling because most users won't know DHCP from ABC. I'd have no clue
that I was running two DHCP servers if I didn't have a bit of networking
experience in
doggieflyer;316077 Wrote:
Putting on my generic user hat, Logitech needs to simplify network
handling because most users won't know DHCP from ABC. I'd have no clue
that I was running two DHCP servers if I didn't have a bit of networking
experience in my day job.
I imagine my setup is
Keep in mind I'm trying to create an all-wired network. All the
squeezeboxes are wired to the same Ethernet router. Some of the
receivers insist on connecting via wireless even though I wish them not
to. I've unplugged the wireless outright and then the controller fails
to connect to the
doggieflyer;316091 Wrote:
Keep in mind I'm trying to create an all-wired network. All the
squeezeboxes are wired to the same Ethernet router. Some of the
receivers insist on connecting via wireless even though I wish them not
to. I've unplugged the wireless outright and then the
For a 'senior software engineer with networking experience' you don't
seem to have much of an engineering approach to problem solving. Just
an observation.
--
amcluesent
amcluesent's Profile:
Amcluesent, your response is just negative and not useful. It's easy to
judge when things are working well for you but my experience has been
extremely painful. If you saw the thought process going into all the
troubleshooting I've done, you would understand. I didn't come on to
the forum and
doggieflyer;316098 Wrote:
Amcluesent, your response is just negative and not useful. It's easy to
judge when things are working well for you but my experience has been
extremely painful. If you saw the thought process going into all the
troubleshooting I've done, you would understand. I
Not for you Phil. Someone posted a nasty response after yours but it
looks like a forum admin deleted it.
--
doggieflyer
doggieflyer's Profile: http://forums.slimdevices.com/member.php?userid=18462
View this thread:
doggieflyer;316101 Wrote:
Not for you Phil. Someone posted a nasty response after yours but it
looks like a forum admin deleted it.
Ah...OK. Sorry.
--
Phil Leigh
You want to see the signal path BEFORE it gets onto a CD/vinyl...it
ain't what you'd call minimal...SB3+Stontronics PSU -
I've spent 14 hours over the last two days trying to get this system to
work. I can't begin to explain the amount of inconsistent behavior
I've experienced. I'm going to describe the latest steps I documented
over the last hour and really appreciate any constructive advice.
I've just built a
Wow - your experience is definitely not a common one or the entire forum
would be lit up with posts similar to yours. I would highly recommend
actually *calling* tech support so they can get your sorted.
BTW, no Internet connection is needed if you are running SqueezeCenter
on an always on
Thanks for the response. I'll definitely give the support team a try on
Monday. I persevered on my own since they were unavailable on the
weekend.
I also plan to bring the system in on Monday to a friend's place that
has a connection to perform the controller upgrade. I've seen a
message on
Great to hear you've had some luck. I was going to recommend not giving
up, as the SqueezeCenter/Duet/Squeezebox product is a superb piece of
kit. I've been an owner for a few years now and can't imagine (music)
life without it.
I know I've updated my Controller/Duet firmware a coupe of times
doggieflyer wrote:
I'm a senior software engineer with networking experience. I've spent
14 hours with this system. I can't imagine the average consumer not
returning this product immediately.
What's providing DHCP on your network?
Are all the devices, SqueezeCenter PC, Receivers, and
39 matches
Mail list logo
