Helpneeded, no servers found

Hi KIBA, I'll take a shot at this.  (I've got about 40 mins before I have to leave to pickup my daughter from exams .  Why did the modem get swapped out?

My internet supplier is preparing for faste gbit connections, even if I just kept my 120 mbit rate, doing this they were also swappping modems, to a newer model supporting docssis 3.1

272 is working fine, iradio, but cant finde the US

Old modem was netgear, now its sagemcom, pack fast 3890we

I have just scanned for HD players using Naim desktop client, and it didn't find any.

Old US IP was 192.168.1.15, now my modem range is 192.168.0.1, giving 272  new ip 192.168.0.10 and NAS 192.168.0.8. Could it be that US somehow is fixed on the 192.168.1.xx range ??, and if how can I change this ??

Ok, I'll assume the modem is the DHCP server, and I'll make a guess it's served up a new IP address range which isn't the same as the old one.  The modem is also I'll assume, doing the local DNS duties for your subnet.

Your 272 finds the internet ok, so it has good IP address, gateway and dns settings.  Leave it alone.

Check your US and ensure it is using DHCP and does not have a manual (hard-coded) ip address, gateway and dns server.  Once that's set, shut it off completely ( not standby ), and reboot it.  It should pickup the ip address, and register with the modem's dns server. It should then be able to talk to the 272.

Then, do the same thing with the NAS.

If still no joy, reboot your switch. This will flush it's cache.  Just in case.

Let us know.. gotta go.. be back later..

kiba posted:

I have just scanned for HD players using Naim desktop client, and it didn't find any.

Old US IP was 192.168.1.15, now my modem range is 192.168.0.1, giving 272  new ip 192.168.0.10 and NAS 192.168.0.8. Could it be that US somehow is fixed on the 192.168.1.xx range ??, and if how can I change this ??

yes, you beat me to it.

If your NAS has the new address, leave it, it should be reachable.

But check to ensure it's DNS and gateway are pointing to the new modem.  It needs this.

Can you connect to your new router and view the DHCP server - to show you what devices are visible to it, and what IP address they have? Alternatively, use the Net Analyzer app or similar, which might give you some useful info. I'm guessing that the Unitiserve has not yet received a new IP address, and will not appear in the list.

How can I check the US, as it not showing up anywhere on my network ?, I would like to check if it has a hardcoded IP address (everything was working for years before this new modem, whit a new IP range. (and I have tried to remove power from US, and boot up again, logo blinking, and then get soli

I use the PC, to check the network, and there is the modem, 272, and NAS, not the US

If the US had a fixed (static) IP address, you would have used the Naim SetIP tool to do it, so presumably you would have some memory of this? 

Is the US connected directly to the new router (into a LAN port, not a WAN port, if it has one?) or is it connected via a switch? Worth checking for correct connections and faulty cables before you start tearing your hair out over settings. 

If you put fing on your iPad it will tell you what address the US is using. Go into it via the web interface and check if it has a fixed IP. If so, change to DHCP. Then reboot everything. I do suspect that this may not be possible if the router does not recognise the old number, but try it first. 

Kind of sorted it, went into the new modem, and in "setup" changed the ip range back to the "old" range 192.168.1 and then it worked. My conclusion, US have a fixed 192.168.1.16, Anyone know how to setup a US

It is only fixed if it has been fixed with the Set IP tool. As standard, the US is set to get its IP from the router using DHCP. 

Just found how to handle the US, In the system status I can see that "Address mode = Static", is this the problem, and it should be changed to ???

You can’t configure this from within the US settings. If you can now see the US in the router LAN settings, can you reserve it an IP address there, using a number that is within the normal range that the router was using? Then you can go back to using the original range of IP address numbers, and the US should still be visible. 

You’ll probably have to restart your streamer and router to see if this has worked. 

kiba posted:

Just found how to handle the US, In the system status I can see that "Address mode = Static", is this the problem, and it should be changed to ???

Did your dealer set this up for you?

You need to use the SetIP Tool on a PC (not a Mac) to use DHCP again.

kiba posted:

Just found how to handle the US, In the system status I can see that "Address mode = Static", is this the problem, and it should be changed to ???

I'm back.. Yes, change it to automatic, save, then reboot. Test again, let us know..

SB955i posted:

kiba posted:

Just found how to handle the US, In the system status I can see that "Address mode = Static", is this the problem, and it should be changed to ???

I'm back.. Yes, change it to automatic, save, then reboot. Test again, let us know..

Can you do this in the DTC? I didn't think it was possible, but as a Mac user, I use the Browser Interface and N-Serve for OSX, and these certainly won't change DHCP settings, only show you what they are. Address mode should show as DHCP, but I still think the SetIP Tool will be required to make the change.

I just found the NaimSetIP tool, and yes US it set to static 192.168.1.16, and as the new modems range was 192.168.0.1 (I changed it to 198.168.1.1) , we had the clash. 

So what to do: 

1. Use the Ipset tool to set US to DHCP (automatic) + reset the modem back to the default range at 192.168.0.1 (It was actually Naim Tec Phill, setting the static IP, as I recall it years ago, due to issues in maintaining a stable connection )

2. Use Ipset tool to set a new rang static 192.168.0.1 and then again the modem back to default

3 Leave it as is - everything is working now, but I do not know why new mode had 198.168.0.1, could this in the future give issues??

ChrisSU posted:

SB955i posted:

kiba posted:

Just found how to handle the US, In the system status I can see that "Address mode = Static", is this the problem, and it should be changed to ???

I'm back.. Yes, change it to automatic, save, then reboot. Test again, let us know..

Can you do this in the DTC? I didn't think it was possible, but as a Mac user, I use the Browser Interface and N-Serve for OSX, and these certainly won't change DHCP settings, only show you what they are. Address mode should show as DHCP, but I still think the SetIP Tool will be required to make the change.

I've just looked at rthe DTC - you can see it (DHCP) but you can't change it.  It'll have to be the Naim address setting tool, I'm afraid (a tool I've never used, so won't try to advise upon )

I know nothing about US,  but it really is best to use DHCP on any home network, it what it's designed for,  static IP is best left to IT people with large installations.    Naim factory set the US to DHCP (default) 

Once all the network is set to DHCP & each component will need a reboot to make it stick,  then power off & reboot the whole system starting each component one at a time, first router/modem,  then US the 272 & finally the control app.   

I Kiba, every service provider uses different base configurations for their modems. You just got unlucky.

You can set this up either as a static network, a dynamic network, or some mix of both.  Each has advantages and disadvantages.

The thing to remember is that your equipment will try DNS first, for a name-ip mapping, then it will look at it's onboard ARP table, to see if it's seen that address before. If it has, it will send the packet to the destination. If it hasn't, it will ask all the devices on the network to answer if they are that ip.  Once it gets an acknowledgement, it will then send the packets.  The onboard ARP table holds a host-ip-mac addr record of the last seen hosts.  In your case it was holding the old US address and didn't have the new one.

Static Addressing:  Good for stability. You need to do everything manually.. update your devices, update the reservations on the modem manually, keep them all in sync.  Reboot your devices after a change so the ARP tables are cleared to start rebuilding again. Reservations on the modem are needed as they will be bound to the DNS server there.

Dynamic: Good for ease of use.  Set devices to automatic.  The modem. will handle the ip-address to hostname mappings and keep DNS in sync.  BUT, if the lease duration is long, and you make changes to the network, the actual addresses on the device won't change until they see their lease is up.. so things could get out of sync until things are rebooted.

Dynamic with Reservations: Good for ease of use. Good for changes.  You will set the devices to automatic.  You will then go into the modem and make "Reservations" in the DHCP Reservations table.  This gives you control on your addressing scheme, but you don't need to make changes on the devices, only the modem.  It also keeps the modem's DNS in sync. You will need to write down your MAC address-IP Address table to reference when you enter this all in.  MAC addresses usually are labelled on the device.

kiba posted:

I just found the NaimSetIP tool, and yes US it set to static 192.168.1.16, and as the new modems range was 192.168.0.1 (I changed it to 198.168.1.1) , we had the clash. 

So what to do: 

1. Use the Ipset tool to set US to DHCP (automatic) + reset the modem back to the default range at 192.168.0.1 (It was actually Naim Tec Phill, setting the static IP, as I recall it years ago, due to issues in maintaining a stable connection )

2. Use Ipset tool to set a new rang static 192.168.0.1 and then again the modem back to default

3 Leave it as is - everything is working now, but I do not know why new mode had 198.168.0.1, could this in the future give issues??

I would use the tool to revert to DHCP, and return the router to its default range of addresses (option 1. on your list.) Also, give Phil a call, my guess is that he would say the same, but he knows more about this stuff than all of us put together, so go with what he recommends - which may be different with your current setup to what he did originally.