Duet Wouldn't Connect Until I Unplugged Touch -- Why Why Why?

[toby10]

Yeah, network printers in particular need the same IP every time, or else your networked computers will be sending print commands to your SqueezeBox.
Same idea is being proposed here, get your SqueezeBox players & server to always have the same IP's. Whether this is accomplished by fixed, static, reserved, etc... is really irrelavent.

[garym]

Hey Gary & Mnyb, I found your comments over in this thread http://forums.slimdevices.com/showth...ting+static+ip

and they've been helpful. Thanks, I appreciate you taking the time to comment on thus same issue again in the thread I started. I do have a question. Mnyb you said "what's important is the to have the range of dchp adresses outside of the ones you use for static ip , otherwise you risk making things even worse. Most routers have a setting for dchp range/pool."

A guy I know who is more tech-savvy than me helped me get a Brother wireless printer going that was causing all kinds of trouble, and I see he gave it a fixed address of 192.168.xx.xx [edit]. Does this give me a clue about the kind of IP address I should choose?


I hope to be able to get time to work on the IP address setup tonight, because if I don't, it may be a couple of weeks with my schedule ahead. I will report back when I get something tried and (hopefully) accomplished.

[edit: I had the IP address of the printer showing. Maybe that's not a good idea for security reasons?]

That's a local ip address so no security issue. My LAN is also all 192.168.1.xx. I suspect your router is handing out dhcp addresses starting at 192.168.1.100. (mine does). So something like 192.168.001.065 would work. But it would be better if you could log into your router to see for sure. Or just get your friend to come back over. This is literally a 3 minute job.

[Please Me Squeeze Me]

Gary, I think I have it figured out--mostly. I logged into my wireless router. Its address pool starts at 11.2, for up to 64 addresses. So, I'm reading that to mean, stay away from anything 65 or below. Anything above 65, except 75 which is the printer, would work.

My only question at this point, I think, is how I get the DNS server IP? Is this the same as the wireless router's IP address, or is it the DNS server 1 (and 2) I see listed as coming from the WAN (I assume this is the Comcast modem upstream from the wireless router) while I am logged into the router? I don't see any other DNS addresses listed anywhere.

OK, I just thought of another question. While I'm doing this, I assume I should do the same thing for the SBT. What about the Duet handheld controller, that too? And while I'm at it, should the two wireless laptops be configured like this, too? They've never had any problems, but does it make sense--that is, is there a reason why it's better--for eveything on a LAN to have a fixed address?

If I don't stop goofing around here (which is what wife would say I'm doing) and start working on the fence outside, I'm going to be in the doghouse.

[garym]

Gary, I think I have it figured out--mostly. I logged into my wireless router. Its address pool starts at 11.2, for up to 64 addresses. So, I'm reading that to mean, stay away from anything 65 or below. Anything above 65, except 75 which is the printer, would work.

My only question at this point, I think, is how I get the DNS server IP? Is this the same as the wireless router's IP address, or is it the DNS server 1 (and 2) I see listed as coming from the WAN (I assume this is the Comcast modem upstream from the wireless router) while I am logged into the router? I don't see any other DNS addresses listed anywhere.

OK, I just thought of another question. While I'm doing this, I assume I should do the same thing for the SBT. What about the Duet handheld controller, that too? And while I'm at it, should the two wireless laptops be configured like this, too? They've never had any problems, but does it make sense--that is, is there a reason why it's better--for eveything on a LAN to have a fixed address?

If I don't stop goofing around here (which is what wife would say I'm doing) and start working on the fence outside, I'm going to be in the doghouse.

I use the router ip address for DNs. 192.168.1.1. You can also use the google public Dns address. I think it is 8.8.8.8. But look that up. Id set up fixed ip addresses for all SB players includiing touch and the controller. I wouldnt do this for the laptops.

[Please Me Squeeze Me]

OK, thanks for the advice. If I have DHCP disabled on the router, when I turn the Duet controller on, it is going to prompt me for network name, key, subnet mask, gateway, DNS, etc., just like the instructions here for the SBT? http://logitech-en-amr.custhelp.com/...ail/a_id/16721

Because--and this may be a stupid noob question--if the controller isn't already connected and working, I'm not going to have anything to input the required info for the Duet receiver, right? That is, right now I'm assuming that when I turn DHCP off on router, the controller is going to lose its connection. (But maybe I'm wrong about that if it's already connected?)

So, I guess what I'm asking is should I: 1) turn controller on, let it acquire IP address from router using DHCP, then turn DHCP off on router and configure Duet? Or should I: 2) turn off DHCP on router, turn on controller and configure it, then configure Duet receiver? Is there a preferred sequence or does it not matter at all?

[garym]

Connect controller with dhcp on, then turn off and setup receiver. Then later reset controller ip address.

[Please Me Squeeze Me]

Disregard above and bracketed portion below. Correction: JOY!!!!!!!!


Here is the secret. I hope this helps someone else. Have DHCP off on router. Hold down button on front of receiver until you get fast flashing red LED (it flashes slow first, then fast). Then on controller go to settings-advanced-perform factory reset. After doing that, first it will walk you through setting up the controller, then it will search for your players (and it gave the Duet some kind of funky numeric name, but I figured that had to be it) and let you assign a static IP address to it. Done! Thanks for all the help, I appreciate it. Hopefully my connection problems are over.


[I have successfully assigned the controller and the SBT static addresses, but no matter what I do with the Duet receiver, I can't figure out how to get it to prompt me to enter a static address. With router DHCP on, it just connects. With router DHCP off, it stays stuck on blue, and I can't find any screen in the controller that lets me enter a static IP address for it. Note that I am attempting to do this wirelessly--which worked with the controller and the SBT. Does the Duet rcvr need an ethernet cable to set up this way? Can't figure out what I'm doing wrong.

Tomorrow I'm going backpacking for a week, so if you post a suggestion and don't get a reply, please don't think I'm being rude. I'll check in and reply sometime next weekend when I'm back. Thanks!]

[garym]

Great news. I hope your connection problems are over too. Do keep in mind that fixed IP addresses don't magically make wifi network interference disappear or solve every LAN issue. However, some of the SB players do have sorta flaky interactions with DHCP servers, so it certainly can't hurt (and may help) to have fixed IP addresses on all the things that don't leave your network.

Disregard above and bracketed portion below. Correction: JOY!!!!!!!!


Here is the secret. I hope this helps someone else. Have DHCP off on router. Hold down button on front of receiver until you get fast flashing red LED (it flashes slow first, then fast). Then on controller go to settings-advanced-perform factory reset. After doing that, first it will walk you through setting up the controller, then it will search for your players (and it gave the Duet some kind of funky numeric name, but I figured that had to be it) and let you assign a static IP address to it. Done! Thanks for all the help, I appreciate it. Hopefully my connection problems are over.


[I have successfully assigned the controller and the SBT static addresses, but no matter what I do with the Duet receiver, I can't figure out how to get it to prompt me to enter a static address. With router DHCP on, it just connects. With router DHCP off, it stays stuck on blue, and I can't find any screen in the controller that lets me enter a static IP address for it. Note that I am attempting to do this wirelessly--which worked with the controller and the SBT. Does the Duet rcvr need an ethernet cable to set up this way? Can't figure out what I'm doing wrong.

Tomorrow I'm going backpacking for a week, so if you post a suggestion and don't get a reply, please don't think I'm being rude. I'll check in and reply sometime next weekend when I'm back. Thanks!]

[w3wilkes]

@OP, just so you know... That "Funky number" you said shows on the controller durring setup is actually the receivers' MAC address. You will find that Funky number on the bottom of the receiver. Every ethernet device has a unique MAC address whether it is wired or wireless.

[Swiftie]

Don't worry about the address of the printer. It's no more of a security issue than my saying that I keep my cash in the room upstairs. The local IP address only says where stuff is within your house (within your network, actually), not how to find your house.

It might help if you told us what sort of router you have. Then someone with the same (or similar) router could take you through the configuration choices.

Having said this, most routers are configured for two distinct ranges of IP addresses for static and DHCP, and people don't normally fiddle with that stuff without knowing exactly what they are doing.