New router and connection - Naim Uniti not being 'found'

Yes - make sure all are on the same network, and that the router is running DHCP for assigning IP addresses.

Also check that your Uniti is set to get its IP address by DHCP. If it has a fixed IP address then the fixed address may not be in the allowed IP range in your new  router. In which case you would need to change the settings in the Uniti.

best

David

Can you see the device connected from your router? Open a web browser, it's likely that the IP address would be 192.168.0.1, User Name: Admin, Password: Admin if its new.

Hi Robert, perhaps you can describe what you mean by your iPad can’t find your Naim initi... if it’s a case of when running a programme like NetAnalyzer (From App Store) and you can see the Uniti do indeed check the Uniti is set for DHCP (and not manual) use and your Wifi router is  enabled and actively offering DHCP. 

If the Uniti appears on NetAnalyzer and has an IP address that starts the same as your other addresses (and does not start with 169.254.x.x)  but is still not shown in the Naim App, then check to see if you have a setting called ‘IGMP Snooping’ on your Wifi router... if it’s enabled then try disabling.

Simon

Thanks, all. Going back into the Naim interface and resetting the DCHP worked. Any idea how to get the QNAP NAS drive to do the same?

QNAP NAS:

I’d recommend shutting it down completely, via it’s web-based interface; waiting 5 minutes and re-starting it.

Robert Daoust posted:

Thanks, all. Going back into the Naim interface and resetting the DCHP worked. Any idea how to get the QNAP NAS drive to do the same?

Qnap Finder app will allow you find the Qnap and shutdown gracefully and also change IP if your new router is on a different IP range and you set the the Qnap to a static IP that's on the old range

When you have done as Hifiman suggests to get into your QNAP setup, you should set it to get its IP address from your router by DHCP. Using fixed IP addresses is totally unnecessary in a simple home network and has the downside that you can get this sort of pain when you change something.

best

David

The fun begins if the Qnap was on a static IP and you added the extra level of security within the Qnap to only allow access from certain IPs but I'm sure the OPs Qnap just needs a reboot, good luck

We have our Qnap on a static IP, or whatever the Airport equivalent is. We have the Qnap and Asset as icons on the iPad, which makes rebooting it easy, and also gives easy access to Asset when needed. When it was on DHCP and the address changed, the iPad access had to be redone. It’s only really an issue if you change the router and forget to unfix things first. 

Hungryhalibut posted:

..................   When it was on DHCP and the address changed, the iPad access had to be redone. It’s only really an issue if you change the router and forget to unfix things first. 

I read this/similar comments on this forum & others,  it makes me wonder why I haven't had the same.   I once had all my home set to static (using the IP addresses within the ISP licence range)  It worked OK but was persuaded to go back to DHCP by an IT friend.  I've since had a few different broadband hubs,  one would set the IP addresses & never change them,  the next changed them each time it was powered off or the ISP did a reset,  but it never caused a problem, it was invisible to all but nerdish & similar sad afflicted types.      The BT HH6 hub I have now set the IP addresses according to the order in which each device was first 'introduced' when new.   I've since reset all the audio IP's (still on DHCP) to a group of numbers at the 'far end' of the ISP licence range (my OCD);     Its been that way for 7 months,  after various power off's from minutes to weeks & a mix of manual & ISP resets,  no IP numbers have changed.           I've also noticed when I plug in my laptop to ethernet & when family & friends visit, the laptop, phones & tablets all get allocated the same IP address as before.   

I think it must depend on the router. My VM Superhub 2ac also assigns the same ip numbers to devices (iPhones etc) as they come and go. But interestingly it seems to have used four different IP addresses over the last year for my Uniti Core and all of them show up in the Naim tools beta app as being current Cores, albeit the three old ones not in quite the same way as the real one, despite the router being restarted and so on. Maybe the firmware updates have changed the way the Core looks to the router and so it's keeping the earlier IP addresses against the possibility of a reincarnation of my Core with early firmware!

best

David 

Indeed I agree with an earlier post, for home networks, and many other networks, DHCP is the best method for assigning addresses to the clients, and DHCP does more than just assign an IP address.

As far as assignments, when renewing an address lease, the DHCP will typically reuse the previous assigned address. For new devices, that have just reconnected DHCP can use what ever address is in the DHCP scope, and most devices seem to fill in from the lowest address. There are many methods for consumer applications to find each other and reference each other via changing ip addresses, such layer 2 discovery, local DNS, mDNS, SSDP etc. If you need a fixed IP address such as for an internal secure connection etc, then still use DHCP, but assign the IP address via DHCP.. so it is the same each time... it’s what I do for my servers which rely on SSH for connection.

Underneath the covers DHCP will anyway use an ARP type request to see if any device responds saying it owns the address, before assigning it... so even if there is a manually assigned IP address on the subnet, a proper DHCP implementation should not assign a duplicate address assuming the statically assigned host responds/is powered up.

Mike intrigued by your reference to ISP licence addresses... nearly all home networks use PAT/NAT via the home router from single ISP Internet address to the private subnet such as 192.168.1.x ... so there is necessarily no correlation between your private address subnet(s) and your ISP assigned Internet address.

Simon-in-Suffolk posted:

 

Mike intrigued by your reference to ISP licence addresses... nearly all home networks use PAT/NAT via the home router from single ISP Internet address to the private subnet such as 192.168.1.x ... so there is necessarily no correlation between your private address subnet(s) and your ISP assigned Internet address.

I mean the range of IPS allocated IP addresses,  I understood that to be known as ISP licence range.  

I think this is nothing to do with the ISP. Some routers come with one range set and some with another. Either will work with any ISP....

best

David

OK I understand (I think)    My ISP is BT & I did understand that their hubs come with a (licenced) IP address range 

Simon will no doubt confirm one way or the other, but my experience is that routers usually have 192.168.0.x or 192.168.1.x where x can be between 1 (normally the LAN side of the router) and something much larger that does vary, but typically is 99 or more even.

With virgin media I have encountered both IP number ranges and everything worked in both cases except that I had a fixed IP address on a network printer and sorting that out when the new router had a different IP range was a bucket full of pain for reasons not to do with the router or anything audio-related.

You can usually change the default IP address range in a router within limits, incidentally. But there is no point or need if you use DHCP everywhere.

best

David

Mike-B posted:

OK I understand (I think)    My ISP is BT & I did understand that their hubs come with a (licenced) IP address range 

Hi Mike, no there are no licensed IP addresses on the hubs. BT along with all ISPs have their Provider Aggregatable (PA) adress ranges that are obtained from  the global regional internet registries (RIR) of which there are five in the world. In Europe we use RIPE as our RIR.

These PA address ranges obtained by the ISP are then assigned to edge routers connected to the internet via the ISP. Consumer broadband typically has an address assigned by the core ISP DHCP and will vary each time your broadband router resyncs or is power cycled.

The Homehub router therefore will be given a globally unique internet address when it is switched on from the BT Internet address range. (Typically this will a random address from a regional subnet provided by BT). Now the addresses we have on our internal home networks are quite different. These addresses are private and only exist in our home network such as 192.68.x.x, 172.16.x.x  or 10.x.x.x. You can not use these addresses on the internet.  The job of the router is to route packets between these two networks... in this case the public internet provided by the ISP and the local home network.

Thanks Simon 

David Hendon posted:

....., but my experience is that routers usually have 192.168.0.x or 192.168.1.x where x can be between 1 (normally the LAN side of the router) and something much larger that does vary....

I believe 0 to 255 is the standard, at least on any router I’ve seen. I’ve noticed on one or two where this appears to be user reconfigurable although I’ve never felt the need to try. 

Chris, the 0 To 255 is simply the range of the subnet mask, and on a class c address  that starts 192.168 then the last octet of the subnet mask governs the size of the network.  iSo if the last subnet mask octet is 0 then the address range for that octet  will be 0 to 255, with 254 host addresses within the 256 addresses. The 255 address is typically the broadcast and the 0 is the network address. Therefore a class c network address of 192.160.1.0 with a subnet mask of 255.255.255.0 means there will be 254 host addresses between the  network address of  192.168.1.0 and broadcast address of 192.168.1.255

If the subnet mask is 255.255.255.248 for example and say the class c network address is 192.168.1.8, the there will be 6 host addresses between 192.168.1.9 and 192.168.1.14 with 192.168.1.15 being the broadcast address.  

So the range of the addresses offered by the router  is based on the subnet mask and network class.... and some home routers allow you to fully specify the subnet mask for correct operation and routing functionality with other subnets you may have... especially with more capable routers. Cheaper more basic home routers may constrain the subnet mask options and may constrain the network classes types.. perhaps only to class c. 10.0.0.0 is a class a,   172.16.x.x is a class b and 192.168.x.x is class c. Apple tends to support all three classes with constrained subnet mask options.

Simon-in-Suffolk posted:

Chris, the 0 To 255 is simply the range of the subnet mask, and on a class c address  that starts 192.168 then the last octet of the subnet mask governs the size of the network.  iSo if the last subnet mask octet is 0 then the address range for that octet  will be 0 to 255, with 254 host addresses within the 256 addresses. The 255 address is typically the broadcast and the 0 is the network address. Therefore a class c network address of 192.160.1.0 with a subnet mask of 255.255.255.0 means there will be 254 host addresses between the  network address of  192.168.1.0 and broadcast address of 192.168.1.255

If the subnet mask is 255.255.255.248 for example and say the class c network address is 192.168.1.8, the there will be 6 host addresses between 192.168.1.9 and 192.168.1.14 with 192.168.1.15 being the broadcast address.  

So the range of the addresses offered by the router  is based on the subnet mask and network class.... and some home routers allow you to fully specify the subnet mask for correct operation and routing functionality with other subnets you may have... especially with more capable routers. Cheaper more basic home routers may constrain the subnet mask options and may constrain the network classes types.. perhaps only to class c. 10.0.0.0 is a class a,   172.16.x.x is a class b and 192.168.x.x is class c. Apple tends to support all three classes with constrained subnet mask options.

 

Simon, thanks for the Subnet Mask primer! I am dimly aware of all this, but as time goes by, and DHCP continues to work smoothly for me, I feel I am gradually forgetting what little I know.

You are welcome Chris, and of course the benefit of DHCP, is for standard home networks one doesn’t need to understand this.

Reading my post again, I can see the mapping of subnet mask might not be clear. The easiest way is to write out the octets of the address and masks in binary... and then it makes more sense.  

A mask of 255.255.255.0 = 11111111.11111111.11111111.00000000

The zeros of the mask define the bits of the addresses within the subnet... in this case the full octet, 256 addresses... a typical home network class c network, and the 1 represent the values of the network address such as 192.168.1

A mask of 255.255.255.128 = 11111111.11111111.11111111.10000000

Here the most significant bit of the last octet is masked off, therefore in this case the last octet is divided into 2, and therefore allows two possible network addresses. x.x.x.00000000 and x.x.x. 1000000 and each of the subnets will therefore have 128 possible addresses indicated by the 0’s in the subnet mask last octet  .10000000 (seven binary digits gives a total of 128 values).. so valid class c address here given by subnet mask 255.255.255.128 are 192.168.1.128 and 192.168.1.0 with each subnet having 128 addresses.