IP for Squeezebox Server

[tcutting]

One thing you want to be careful of is setting a static IP which is not in the range of IPs which your router will allocate via DHCP. There is typically a setting in the router to control the addresses it will serve - could be starting address and number of addresses available. You do, however, want the static IP(s) to be in the same subnet as those served dynamically by your router.

[Mnyb]

Don't forget to manually set DNS if you use static, many routers do DNS or otherwise use the your ISP's DNS servers .

[JJZolx]

Don't forget to manually set DNS if you use static, many routers do DNS or otherwise use the your ISP's DNS servers .

I'm not familiar with the Mac, but the setting shown above, "Use DHCP with manual address," may mean that DNS servers and some other DHCP settings are still picked up from a DHCP server, and that only the IP address is set manually. It should be simple enough to figure out. After applying the settings shown above, either the iMac will be able to resolve and access web sites by name, or it won't.

Like tcutting said, make sure you find the management interface for your router (usually a web interface on the router, so try http://192.168.1.1) and find the DHCP server settings. Make sure the 192.168.1.2 IP address that is being given to the iMac isn't also being given out by the DHCP server or you could end up with an address conflict.

[auronthas]

I'm not familiar with the Mac, but the setting shown above, "Use DHCP with manual address," may mean that DNS servers and some other DHCP settings are still picked up from a DHCP server, and that only the IP address is set manually. It should be simple enough to figure out. After applying the settings shown above, either the iMac will be able to resolve and access web sites by name, or it won't.

Like tcutting said, make sure you find the management interface for your router (usually a web interface on the router, so try http://192.168.1.1) and find the DHCP server settings. Make sure the 192.168.1.2 IP address that is being given to the iMac isn't also being given out by the DHCP server or you could end up with an address conflict.

Thanks for the feedback. But when I typed in 192.168.1.2 manually without DHCP on IPv4 configuration (see photo attached), I can no longer access to internet (using wireless router). I have to roll back to 'Use DHCP with manual address'.

[auronthas]

Thanks for the feedback. But when I typed in 192.168.1.2 manually without DHCP on IPv4 configuration (see photo attached), I can no longer access to internet (using wireless router). I have to roll back to 'Use DHCP with manual address'.

Mnyb, you are right, after checking my primary DNS server (from ISP DNS Server) from router setting. Manually typed in DNS (as photo attached), finally it works.

[bleakcomb]

Auronthas,

After doing all that you might reconsider reserving an IP address on your router for your Mac. It would mean your Mac IP configuration would revert to Automatic DHCP as it was before.

Mnyb, you are right, after checking my primary DNS server (from ISP DNS Server) from router setting. Manually typed in DNS (as photo attached), finally it works.

What Mnyb was talking about was using your router's lan IP as the DNS address in your Mac and elsewhere on your network. Sometimes routers perform DNS relay to your ISP (or other) DNSs. Just specify your router IP address in the DNS address on the Mac and give it a try. Easier than having to track IPs of outside DNSs when they change. This is just for a static IP setup.

Seriously reconsider reserving an address for your Mac on the router, though. Much easier. Edit: This link explains things. http://www.tuaw.com/2009/10/16/using...-bonjour-woes/

[Mnyb]

DNS is matter of taste I use my router as DNS 192.168.1.1 but Using the ones you dsp provides can bypass trouble in the router, and they change very rarely.
However normal ips use one primary and one secondary DNS punch in both of them you can have more than one DNS. Or you can use any other free DNS service as backup.

Reserved DHCP still use the routers DHCP function and he is sometimes getting this address 169.254.188.117 (he not not getting any real address) ?? so something can get weird with his router? I's not uncommon with slightly buggy routers, especially in the price range where non professionals shop (reboot of router now and then can make wonders )

I use DCHP for the range 192.168.1.100 to 149 so I can connect my laptops and other mobile stuff.

For all things that are fixtures to my home I use static ip, well my server is not going anywhere soon I think things get more stable this way , so server desktop and all squeezeboxes have static ip.

[auronthas]

Bleakcomb,

Thanks for further clarification.

I have changed back my DNS setting similar to router's IP, i.e. 192.168.1.1, I did not encounter internet interruption as post #14 above, I do not know why. I have manually set my TCP/IP for my iMac server at 192.168.1.2, after checking Squeezebox Server Information, it appears the same IP address and the host name is my iMac name. I hope everything is in order now.

[auronthas]

One more question, I noticed that current Player IP address is 192.168.1.6, previously it was at 192.168.1.3, is it possible to set static IP for player(Squeezebox)?

[bleakcomb]

I am not sure that you have it sorted just yet.

One more question, I noticed that current Player IP address is 192.168.1.6, previously it was at 192.168.1.3, is it possible to set static IP for player(Squeezebox)?

To answer your last question, yes, you may give a Squeezebox a static IP, but you really don't need to. You are making life unnecessarily difficult for yourself by doing so. IP addresses allocated by DHCP to a host will change and that is OK. Let DHCP allocate the address to the Squeezebox and enjoy the music. ;-)

Really, the computer running Squeezeserver doesn't need a static IP, either. It is possible that a DHCP lease expires and the server renews the IP address and the IP address actually changes (as happened for you). But as others have alluded, this is unusual and if this occurred while you were using the Squeezebox, the worst that would occur is you may need to reconnect the Squeezebox to the server at its new address - a couple of buttons to push. The Squeezebox should do this fairly automatically, though.

The usual reason for allocating a static IP is not to locate the host on the LAN (there are name resolution services for that) but to allow the router to forward connections from outside the LAN to one fixed, known IP address, known as port forwarding. You may have a requirement to connect to the host running your Squeezeserver that is unrelated to the Squeezeserver system ie remote access or a mail server. This will be coincidental to the operation of Squeezeserver and Squeezeboxen on the LAN and its OK to set a static IP or reserve a dynamic address for those reasons.

Also something from Mnyb's last post concerning the 169... address that you saw. That is a problem that would normally require attention. An address in that range is a link-local address and implies that there is no DHCP server operating on the LAN subnet and a host requests a dynamic address from DHCP. If you see 169... addresses, you need to get the cause and resolve it.

Now back to the static IP on your iMac. It's not quite right. You shouldn't allocate a static IP (192.168.1.2) in the range that your DHCP server is allocating. It will eventually (sometimes very quickly) lead to conflicts on your LAN and tears before bedtime. Again, I suggest configuring your DHCP server (probably on router) to reserve your favourite address for the iMac. Otherwise, if you are adamant about the static IP you need to find out the range of addresses allocated by your DCHP server and allocate your static IP OUTSIDE that range to avoid conflicts. If you need help with the DHCP server, post details of your router and we'll go from there. Hope all that helps!

Also your are right Mnyb, external DNSs don't usually change very often, but they can (mine ISP has changed twice) and because it occurs so infrequently it is usually the last thing you think to check! If you are going to set up static IPs and abandon a perfectly good DHCP server it is best to avoid relying on hard coded external addresses that normally would be served automatically by your DHCP. My 2 cents.