changing of i.p address by the HDX?

Posted by: David Leedham on 30 December 2008

I have been the proud owner of a new HDX as from Xmas eve. I have found the connection to the internet working straight from the box. I use a mobile broadband internet access with 3 G, a wireless router and mains based Ethernet connection from the router to the HDX. I intend to use a dedicated ethernet cable in the fullness of time just in case there may be “noise” introduced to the mains for the Naim system. Certainly not noticeable at the moment. All sounds very good indeed on par with my previous CDX2 XPS2. I have managed to access the HDX controls via the internet ip address and a laptop. The desktop client controls will only manage to connect via a desktop pc. This has been a very nice system to use. Ripping discs has been taking approx 3 minutes per disc. I have now ripped 400 discs so far.. One or 2 discs in the last 20 or so have been taking rather longer, long pauses between successful AMG data look up and slow ripping. I wonder whether this is a feature of a hard disc getting “fuller”.
Yesterday I found that I could no longer access the HDX via desktop client or via ip address. I restarted the HDX and router. No joy. Today I used the HDX screen to check the i p address and have found that it has changed! by 1 terminal digit. Using this new address I have restored connectivity. Big sigh of relief.
During this loss of connectivity to url and desktop client the HDX would still rip and access the online datqabases. Has anybody else experienced an apparent changing of i.p address by the HDX?
Posted on: 30 December 2008 by gary1 (US)
David, I have not experienced this ip address phenomenon. I am using not the preset IP address, but my own configuration that works well in my home since I have other devices on the intranet.

I'm surprised at the speed of your ripping with the HDX, it does not sound right. The information says 7-8 minutes per rip on average and this is what I have experienced through 350+ rips, as well as, seen others posted and at my dealers.

The longer ripping at this time may be due to the fact that the HDX was performing a back/up while you were trying to rip. Check "system" and back-up settings to confirm.
Posted on: 30 December 2008 by Manu
The address may change if the HDX is set on DHCP. If you prefer this not to happen again, set the address as static, out of the your router DHCP range.

Your ripping time is way too short. As Gary said, it should take about 7-8 minutes per disk. Quite strange...
Posted on: 30 December 2008 by AV@naim
Its probably because your router (with onboard DHCP server) is not permanently on and the HDX was in standby.

(Remember if you turn off your router, the table containing all of the existing devices DHCP IP's on your network is usually lost and thus there is a protocol for re-enumerating this info).

If the HDX is off when you repowered the router, its original IP address(s) is still held on board (like a normal PC). Now, when you turned on your router all of the devices on the network in DHCP mode grabbed the next available IP address and carried on their merry way. Problem is, when you then power up the HDX its existing lease is still valid, so the unit tries to use the old addreses.

What happens next is that another device will probably complain that the (HDX's) IP is now already in use (due to the router being ignorant of the HDX still having a valid IP, when it was off), so after many milliseconds of shouting at each other, the HDX realises it needs a new IP address and asks the DHCP server for another...thus it can get a different IP address.

The two options are:

1) Some routers can be set to give out a specific address to the device in question, if you give the MAC address, see router documentation.

2) Set a static IP address for the HDX (and its front panel) using the supplied SETIP tool. Any devices requiring a static address must not be in your current DHCP range (this is standard network protocol for any network setup), thus you will need to change the DHCP range (see comment on reading documentation below). Ideally the unit should be used in DHCP mode where possible.

I strongly recommend you (and anyone else wishing to set the HDX to a static IP) to read all the documentation in the Public->HDX section of the naim download site here, before attempting this:

http://www.naim-audio.com/download/
Posted on: 31 December 2008 by David Leedham
Thank you Paul

Some carefull reading and inwardly digesting required to get my head round this! A very full and succint explanation.
Posted on: 31 December 2008 by gary1 (US)
David, interesting reading. I think that DHCP was chosen as the standard as it didn't require any set-up. From conversations I've had with NANA the static really is the preferred method so you don't run the risk of having what happened to you occur on a regular basis. This however as stated above requires some set-up using the DTC software.

I have numerous devices in my home using DHCP and while for the most part it's fine even when devices are turned off or the router goes out in a power outage the HDX having 2 IP addresses for the front and back panels as shown in the diagram from the download can create this problem.

It takes only a few minutes to set up but you need some familiarity with IP protocols and how to obtain the DNS, Net Mask, and Gateway from either your router or from a computer connected to your router. Once this is obtained the set-up is straight forward using the static tool on the DTC.

If you are not familiar or do not have a friend or IT person to assist you, I'm sure that the people at Naim would give some assistance. Because of the set-up issue and calls it would generate, I'm sure that this is the reason for using DHCP as opposed to static. Makes sense.
Posted on: 31 December 2008 by gary1 (US)
David, this will tell you how to identify the information you need to do the set-up. The only other information is you DHCP range as the HDX must be programmed "outside" of the DHCP range and you should give the HDX 2 addresses which are consecutive in the last 3 numbers.


http://www.more.net/technical/netserv/tcpip/viewip.html
Posted on: 31 December 2008 by David Leedham
Thank you Gary,

The HDX files referred to by Paul have dire warnings:

Incorrect settings can result in the unit failing to work correctly and it may be
necessary to return the unit to Naim for recovery.

I will tread carefully Roll Eyes
Posted on: 04 January 2009 by AV@naim
quote:
Originally posted by gary1 (US):
This however as stated above requires some set-up using the DTC software.


To be clear here:

Only SETIP tool should be used to change HDX/NS01/2/3 IP addresses, not DTC (the older V1 DTC did allow you to do this for NS01 and 2, as they have no front panel).

To be safe ONLY use SETIP tool to change from/to DHCP/Static.

Also, anyone using Desk Top Client should not be using a DTC older than 2.0.5.1122 anyhow (see DTC Help->About Desk top Client menu)

Setting a static IP in the DHCP range is definitly a nono in network-land.
Posted on: 04 January 2009 by gary1 (US)
quote:
Originally posted by AV@naim:
quote:
Originally posted by gary1 (US):
This however as stated above requires some set-up using the DTC software.


To be clear here:

Only SETIP tool should be used to change HDX/NS01/2/3 IP addresses, not DTC (the older V1 DTC did allow you to do this for NS01 and 2, as they have no front panel).

To be safe ONLY use SETIP tool to change from/to DHCP/Static.

Also, anyone using Desk Top Client should not be using a DTC older than 2.0.5.1122 anyhow (see DTC Help->About Desk top Client menu)

Setting a static IP in the DHCP range is definitly a nono in network-land.


Sorry, you are correct, I meant to put "set-up IP tool". David, it is found using your computer start menu in case you have gotten confused.

Start-->programs->Naim-->Naim Setup IP tool
Posted on: 04 January 2009 by jon h
quote:
Originally posted by AV@naim:

Setting a static IP in the DHCP range is definitly a nono in network-land.


You could set a reservation in the dhcp tables for the hdx
Posted on: 04 January 2009 by AV@naim
quote:
Originally posted by jon honeyball:
quote:
Originally posted by AV@naim:

Setting a static IP in the DHCP range is definitly a nono in network-land.


You could set a reservation in the dhcp tables for the hdx


see note 1) in my first post above, I was a bit vague I admit.
Posted on: 04 January 2009 by David Dever
quote:
Originally posted by David Leedham:
I have been the proud owner of a new HDX as from Xmas eve.... This has been a very nice system to use. Ripping discs has been taking approx 3 minutes per disc. I have now ripped 400 discs so far.. One or 2 discs in the last 20 or so have been taking rather longer, long pauses between successful AMG data look up and slow ripping. I wonder whether this is a feature of a hard disc getting “fuller”.
Yesterday I found that I could no longer access the HDX via desktop client or via ip address. I restarted the HDX and router. No joy.


Newer HDX units have a slightly faster disc loader mech, which takes a little bit less time than the previous one to rip a Compact Disc. They cannot be fitted to older units.

However, the problem you indicated about the delay incurred before ripping sounds to me as if your internet connectivity had been interrupted, whereby the unit would try to access AMG first (no luck due to lack of outbound connectivity), FreeDB second (similarly no luck), and the internal cached copy of FreeDB last (successful if found).

I always recommend static IPs for permanent installation, by the way–depending on your router, this inside (LAN) address can be independent of whatever scheme your ISP uses to assign outside (WAN) addresses.
Posted on: 04 January 2009 by Roy Donaldson
Shouldn't make any real difference if you use DHCP or assign a static IP to a unit on an IP network. Only real difference is if you need to use a IP address to connect to it and then having a static can help with that. But, if all you are doing is sourcing data from the device, then DHCP or static should make no difference.

AV, most DHCP servers should ARP for addresses before assigning then, so you are usually safe assigning within the DHCP pool range. Though, outside is safest.

Roy.
Posted on: 04 January 2009 by jon h
quote:
Originally posted by AV@naim:
see note 1) in my first post above, I was a bit vague I admit.


Apologies, I missed that.
Posted on: 04 January 2009 by AV@naim
quote:
Originally posted by Roy Donaldson:

AV, most DHCP servers should ARP for addresses before assigning then, so you are usually safe assigning within the DHCP pool range. Though, outside is safest.

Roy.


yes they "should"...

But hey, I'm certainly not going to argue with you of all people on networking protocol Roy! Winker
Posted on: 05 January 2009 by Roy Donaldson
Available for work on very competitive consultancy rates Winker

IP routing's kinda basic stuff not that hard. My speciality is in Voice over IP.

Roy.
Posted on: 05 January 2009 by David Dever
quote:
Only real difference is if you need to use a IP address to connect to it and then having a static can help with that.


Precisely. In an environment where one needs to know that a device is exactly at the address where it is purported to be, this seems to be the most intelligent approach.

I don't understand why people fight for the right to DHCP, really–reminds me of life in a caravan.
Posted on: 06 January 2009 by Alan A
Just a brief note to remind eveyone that the HDX should only be powered up after it has been connected to a working ethernet environment to avoid default IPs being established. So connect to network, then apply power.
Posted on: 08 January 2009 by Jay
quote:
Originally posted by Roy Donaldson:
Available for work on very competitive consultancy rates Winker

IP routing's kinda basic stuff not that hard. My speciality is in Voice over IP.

Roy.


....And we know what a massive audio upgrade voice over IP is Smile