duet getting "lost" on network (no player recognized)

[gordonlw]

strange thing happening here lately and it's very frustrating! first of
all for my set up

duet connected via ethernet to a netgear switch which is connected to a
Linksys E1200 router(problems happen even connected directly to the
router).

squeezebox server v7.5.3 (tried 7.5.4 and had issues and seems 7.6 has
issues) running on windows home server 2003 box I built connected to
the same netgear switch. windows firewall on server allows squeeze
server etc.

I built the server back in may and for the most part everything has
been running fine. the switch has been in use since the server was
built, the router a few weeks after that.

every now and then when trying to use the duet I find that it can not
be found on the network. light on duet is always solid blue when this
happens.

going into my router settings the duet doesn't even show up, can't ping
it etc.

at first I thought it had something to do with the duet having a static
ip (DHCP reservation as my router calls it). changed it back to normal
DHCP and reset the duet (held button till red and reset up via
ethernet).

this worked fine for a few weeks and then all of a sudden the same
thing happened again. player not found and not showing up in router
setting. fwi the diagnostics screen always looks ok as far as ports
etc.

this time I thought maybe it didn't like the home server being a static
IP so I changed it to DHCP. I then unplugged the duet, rebooted the
router and plugged the duet back in. the player then showed up in
router settings and was recognized by the squeeze server. this worked
for a few days.

now today the same thing! the ip of the home server hasn't changed,
there are plenty of free dhcp addy's for the duet just all the sudden
"no player found" and duet not showing up in router settings.
rebooting the router did not work this time. I had to do a reset on
the box and reset up via ethernet. worked fine but who knows for how
long?! and this is hardly an acceptable solution!

fwi I have my main pc, home server, a wdtv, & the squeezebox connected
to the switch and everything else works just fine! only thing not
playing nice is the duet. and again the issue happens even if plugged
directly into the router.

I've had the duet for a few years now and haven't had too many issues.
this one is very frustrating! any thoughts, help etc etc would be
great!

[garym]

first step: unplug duet receiver, turn off computer, unplug router and
switches. then reboot router, let start, turn on switches, turn on
computer, let SbS fully start, then last plug in duet.

Also, you might want to try a true static IP (what you're calling a
static IP is just a DHCP reservation, but still being provided by
DHCP). When you go into the networking menu of the duet, you can set a
static IP. It should be an IP address OUTSIDE the router's IP address
range. In my case, my router has a DHCP range of .100 to .254

My router address is 192.168.1.1
So I give the duet receiver an address (within the duet receiver menu)
of:

192.168.1.25
(the last .xx is just something above 1 and below 100)
Subnet is 255.255.255.0
DNS is 192.168.1.1
DNS2 (if needed) 192.168.1.1

in SB, if it wants 3 digits for "1" enter "001"

[gordonlw]

Post by garym
first step: unplug duet receiver, turn off computer, unplug router and
switches. then reboot router, let start, turn on switches, turn on
computer, let SbS fully start, then last plug in duet.
Also, you might want to try a true static IP (what you're calling a
static IP is just a DHCP reservation, but still being provided by
DHCP). When you go into the networking menu of the duet, you can set a
static IP. It should be an IP address OUTSIDE the router's IP address
range. In my case, my router has a DHCP range of .100 to .254
My router address is 192.168.1.1
So I give the duet receiver an address (within the duet receiver menu)
192.168.1.25
(the last .xx is just something above 1 and below 100)
Subnet is 255.255.255.0
DNS is 192.168.1.1
DNS2 (if needed) 192.168.1.1
in SB, if it wants 3 digits for "1" enter "001"

thanks for the reply! to get to the network settings on the duet do I
need to reset the box and then do the setup again? I don't see
anywhere to change the IP in the remote settings or the advanced web
based settings.

my router address is also 192.168.1.1 and have it set up to give out up
to 15 dhcp addys. so 192.168.1.100 - 192.168.1.115

so would the same settings you listed work for my setup?

[garym]

Post by gordonlw
thanks for the reply! to get to the network settings on the duet do I
need to reset the box and then do the setup again? I don't see
anywhere to change the IP in the remote settings or the advanced web
based settings.
my router address is also 192.168.1.1 and have it set up to give out up
to 15 dhcp addys. so 192.168.1.100 - 192.168.1.115
so would the same settings you listed work for my setup?

1. Sorry, my one duet receiver has been in a drawer since I replaced it
with a TOUCH a few years ago, so I can't check. I recall that you can go
into the menu of the receiver, maybe ADVANCED>Networking. Just not sure.
look at all the options under settings, advanced, etc. But if all else
fails, a factory reset will work for sure.

2. Yes, settings I mentioned would work. Just make sure the IP address
you give the duet receiver is less than .100, so you could use
192.168.1.25 (I recall you'll need to enter 192.168.001.025)
and the rest the same: 255.255.255.0; 192.168.1.1, etc.

[garym]

Post by garym
1. Sorry, my one duet receiver has been in a drawer since I replaced it
with a TOUCH a few years ago, so I can't check. I recall that you can
go into the menu of the receiver, maybe ADVANCED>Networking. Just not
sure. look at all the options under settings, advanced, etc. But if
all else fails, a factory reset will work for sure.
2. Yes, settings I mentioned would work. Just make sure the IP address
you give the duet receiver is less than .100, so you could use
192.168.1.25 (I recall you'll need to enter 192.168.001.025)
and the rest the same: 255.255.255.0; 192.168.1.1, etc.

Another approach is to temporarily turn of DHCP on your router. Then do
a factory reset on duet receiver. It will fail to get IP and then ask to
try again. Say OK. It will fail again, then scroll down the menu on the
controller and you see something like "self assign". Then select this
and give it the static IP stuff....once it is all set, go back to your
router and turn DHCP back to ON.

p.s. (this is how I also set up a static IP address for the CONTROLLER
and TOUCH units as well).

[gordonlw]

hmm. advanced > networking on the remote only shows

choose network (in there are wireless networks available)
remote libraries
switch to mysqueezebox.com

edit: just saw the second post. I'll try that.

[garym]

like I said, I just can't recall. but a factory reset should get you
there too.

[gordonlw]

what happens when you select "choose network"

it just shows mine and my neighbors router. ie it's just finding
wireless networks. gonna mess with this when my 8 month old goes down
for her nap ;)

[garym]

Post by gordonlw
it just shows mine and my neighbors router. ie it's just finding
wireless networks. gonna mess with this when my 8 month old goes down
for her nap ;)

so you ARE SURE that the receiver is connected via ethernet. When you
look at the information tab in SbS > Settings, you'll see your players
listed. If you are on ethernet you will NOT see the wireless strength
listed there....

for example, note my radio is connected via wifi (and it tells me the
strength) but my touch is ethernet and it doesn't mention wifi
strength.

Player Model: Squeezebox Radio
Firmware: 7.6.1-r9468
Player IP Address: 192.168.1.61
Player MAC Address: XXXXXXXXXXXXXXXXXXXX
Wireless Signal Strength: 100%

Player Model: Squeezebox Touch
Firmware: 7.6.1-r9478
Player IP Address: 192.168.1.21
Player MAC Address: XXXXXXXXXXXXXXXXXXxx

[gordonlw]

it's ethernet. verified where you said and it shows as LAN in my
router, not wireless. I've never had it connected wireless (not in a
few years anyway).

[gordonlw]

it's not working. just read may threads where sometimes it works and
sometimes it doesn't for the duet. I turned off dhcp and did a reset.
instead of giving me the option to assign an IP it assigned a APIPA IP
169.254.xx (unusable). tried it numerous times and the same thing
happened.


for the touch logitech tells you how to do it like you said

http://logitech-en-amr.custhelp.com/app/answers/detail/a_id/16721/~/setting-up-my-squeezebox-touch-to-use-a-static-ip



the thing is in theory DHCP reservation should be all I need for it to
lock in the IP and never get "lost" on my network but for some reason
it's happening! gonna go back to reserving it's IP and see how it
goes.

[garym]

it's not working. just read many threads where sometimes it works and
sometimes it doesn't for the duet. I turned off dhcp and did a reset.
instead of giving me the option to assign an IP it assigned an APIPA IP
169.254.xx (unusable). tried it numerous times and the same thing
happened.
for the touch logitech tells you how to do it like you said
http://logitech-en-amr.custhelp.com/app/answers/detail/a_id/16721/~/setting-up-my-squeezebox-touch-to-use-a-static-ip
the thing is in theory DHCP reservation should be all I need for it to
lock in the IP and never get "lost" on my network but for some reason
it's happening! gonna go back to reserving it's IP and see how it
goes.

the ip you mention sounds like it is maybe connecting to
mysqueezebox.com instead of your local SbS. When it is "not connected"
if you go to mysqueezebox.com do you see the duet receiver as
"connected" (you should NOT see it as connected unless it is connected
to mysb.com)

and correct....you should be able to use plain DHCP and have no
issues.....the static IP idea just removes any odd variables with your
router, etc.

[gordonlw]

it's not mysqueezebox.com

it's an appipa ip

Short for Automatic Private IP Addressing, a feature of later Windows
operating systems. With APIPA, DHCP clients can automatically
self-configure an IP address and subnet mask when a DHCP server isn't
available

http://compnetworking.about.com/cs/protocolsdhcp/g/bldef_apipa.htm

it's basically a useless private ip that the router assigns when there
is no dchp.

[garym]

Post by gordonlw
it's not mysqueezebox.com
it's an appipa ip
http://compnetworking.about.com/cs/protocolsdhcp/g/bldef_apipa.htm
it's basically a useless private ip that the router assigns when there
is no dchp.

Interesting. New to me. But odd too, as I have two machines running
Win7 (64), SP1, so I assume as new as you can get, and I can easily
turn on DHCP temporarily in my router so I can assign a static IP
address to something like a SB player. The duet receiver is connected
via ethernet back to your router (maybe via some switches) but not
directly to your computer, correct?

[gordonlw]

the thing I copied must be old ;) it's been around since 2000 or xp at
least.

I'm not alone with this happening

http://tinyurl.com/4yy5de7

[gordonlw]

The duet receiver is connected via ethernet back to your router (maybe
via some switches) but not directly to your computer, correct?

yes. directly to switch. then switch to the router. happened both
ways (switch or direct to router).

[garym]

odd. then should be no problem getting an IP address from your router
and then keeping it. I'm out of ideas. I forget whether you've
reported, but what router are you using?

[gordonlw]

Linksys E1200

[sebp]

Post by gordonlw
it's basically a useless private ip that the router assigns when there
is no dchp.

It's not the router that assigns these addresses, but the devices
themselves.

IIRC (typing a 63 bytes long WPA key with the Controller is a pain, so
I tend to avoid unnecessary tries), you need to reset both the Receiver
and Controller to factory defaults to go from a DHCP to a static IP
configuration, because the Controller "forwards" its configuration to
the Receiver it configures.

Even if you don't go the static IP route, double check that the machine
running the Squeezebox Server has a proper DHCP reservation, and that
you only have one device on your network acting as a DHCP server.

I encountered this problem one time or two when I used DHCP
reservations, but it didn't occur any more since I configured the
server and controller with static IP addresses.

I've also been told that forcing the network_lan_address parameter with
Net-UDAP, even when using DHCP, cured the problem.

[gordonlw]

you need to reset both the Receiver and Controller to factory defaults
to go from a DHCP to a static IP configuration, because the Controller
"forwards" its configuration to the Receiver it configures.
I encountered this problem one time or two when I used DHCP
reservations, but it didn't occur any more since I configured the
server and controller with static IP addresses.

that was it! thank you both so much! didn't realize I needed to reset
and set the remote to static as well. got both done and we're up and
running! never had any issues like this over the years on xp or 7 (not
this frequent anyway). since I built the server (whs 2003) and then got
a new router (7 year old one died) this has happened way too much! I
see no reason why the static fix shouldn't take care of this. only
time will tell ;) thanks again to both of you!

[garym]

Post by gordonlw
that was it! thank you both so much! didn't realize I needed to reset
and set the remote to static as well. got both done and we're up and
running! never had any issues like this over the years on xp or 7 (not
this frequent anyway). since I built the server (whs 2003) and then got
a new router (7 year old one died) this has happened way too much! I
see no reason why the static fix shouldn't take care of this. only
time will tell ;) thanks again to both of you!

Excellent. I hope this is the fix. I guess I set up my duet with both
the receiver and controller with static IP addresses at the same time
so never new about this fall back behavior. I always learn something
new hanging out here....