Can't connect HDX to LAN network
Posted by: Brando on 27 October 2009
Hi everyone!
Just wanted to say that I decided to sell my CD5xs (which was great, by the way) and Flat Cap XS. The convenience of listening to music with playlists, browse the songs on my PC, great player, lots of space (at least enough for me), a good start for some better amp (I have XS at the moment) are the reasons for changing my mind about CD5xs and get HDX.
I have one problem, don't know how to connect it on the LAN. I have a router and tried to connect the LAN cable directly to HDX but it didn't recognize anything.
Does anyone know the procedure of connecting HDX to the internet?
Step by step one
I have no clue what to do.
Thanks!
Brando
Just wanted to say that I decided to sell my CD5xs (which was great, by the way) and Flat Cap XS. The convenience of listening to music with playlists, browse the songs on my PC, great player, lots of space (at least enough for me), a good start for some better amp (I have XS at the moment) are the reasons for changing my mind about CD5xs and get HDX.
I have one problem, don't know how to connect it on the LAN. I have a router and tried to connect the LAN cable directly to HDX but it didn't recognize anything.
Does anyone know the procedure of connecting HDX to the internet?
Step by step one
I have no clue what to do.
Thanks!
Brando
Posted on: 28 October 2009 by nocker
Posted on: 28 October 2009 by Svetty
?? posting in the distributed audio forum more likely to get a response?
Posted on: 28 October 2009 by Brando
Thanks both of you!
Been very useful. I never really realized that forum before.
Been very useful. I never really realized that forum before.
Posted on: 28 October 2009 by garyi
Brando, did the unit come to you second hand?
Its possible one of two things is happening (amongst others),
1. The hdx is second hand and currently has a set IP address in it.
2. The network you have is not DHCP enabled but the HDX is.
Please explain how you usually connect things to your network.
I assume you have installed the software that comes with. Once the hdx is fully powered up it must have settings somewhere to establish what IP its using, apparently it uses two so you need to find the one its using to get on your network (or not)
Its possible one of two things is happening (amongst others),
1. The hdx is second hand and currently has a set IP address in it.
2. The network you have is not DHCP enabled but the HDX is.
Please explain how you usually connect things to your network.
I assume you have installed the software that comes with. Once the hdx is fully powered up it must have settings somewhere to establish what IP its using, apparently it uses two so you need to find the one its using to get on your network (or not)
Posted on: 29 October 2009 by Brando
Yes it is second hand, Garyi!
First I installed the software (IP tool and Desktop client) and than I just plugged the LAN cable from my router into the HDX. Than I started the IP tool and tried to recognize the HDX but nothing happened. Keeps saying that it took the device too much time to reply or smth.
I also managed to affect my wireless printer. Now it doesn't work except with usb cable...
And how I usually connect devices to my computer... when I installed the HP printer, I just did the recognition of the network on the device itself.
Please I need help, I am totally new to this matter!
Thanks!
Brando
First I installed the software (IP tool and Desktop client) and than I just plugged the LAN cable from my router into the HDX. Than I started the IP tool and tried to recognize the HDX but nothing happened. Keeps saying that it took the device too much time to reply or smth.
I also managed to affect my wireless printer. Now it doesn't work except with usb cable...
And how I usually connect devices to my computer... when I installed the HP printer, I just did the recognition of the network on the device itself.
Please I need help, I am totally new to this matter!
Thanks!
Brando
Posted on: 29 October 2009 by AV@naim
quote:Originally posted by Brando:
Yes it is second hand, Garyi!
First I installed the software (IP tool and Desktop client) and than I just plugged the LAN cable from my router into the HDX. Than I started the IP tool and tried to recognize the HDX but nothing happened. Keeps saying that it took the device too much time to reply or smth.
I also managed to affect my wireless printer. Now it doesn't work except with usb cable...
And how I usually connect devices to my computer... when I installed the HP printer, I just did the recognition of the network on the device itself.
Please I need help, I am totally new to this matter!
Thanks!
Brando
Can you please give some more information on the network. On your PC (I assume this is an XP Windows box??):
-go to the Start menu
-go to Run (On Vista you can use the Start Search box instead)
-In the box type CMD and press enter
-a black window opens type IPCONFIG /ALL and press enter
Some network details should appear.
Please tell me what it says next to these sections:
DHCP Enabled:
IP Address:
Subnet Mask:
Default Gateway:
Then go to the HDX front panel (System Setup->System Status page) and tell me what it says under:
IP Address:
Subnet Mask:
Gateway:
Address Mode:
Front Panel IP Address:
Posted on: 29 October 2009 by Brando
Thanks for reply Naim HQ!
It's Vista and I have just checked those parameters.
Now, I see different parameters. First for
1. Wireless LAN anapter Wireless Network Connection:
DHCP Enabled: YES
IPv4 Address: 192.168.1.101
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.1.
But I don't see those parameters for other connections.
2. Ethernet adapter Local Area Connection:
DHCP Enabled: no
3. Tunnel adapter Local Area Connection 6:
DHCP enabled: no
and so on for Local area connection 7, 9, 10 and 11
Will send for HDX in couple of minutes...
It's Vista and I have just checked those parameters.
Now, I see different parameters. First for
1. Wireless LAN anapter Wireless Network Connection:
DHCP Enabled: YES
IPv4 Address: 192.168.1.101
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.1.
But I don't see those parameters for other connections.
2. Ethernet adapter Local Area Connection:
DHCP Enabled: no
3. Tunnel adapter Local Area Connection 6:
DHCP enabled: no
and so on for Local area connection 7, 9, 10 and 11
Will send for HDX in couple of minutes...
Posted on: 29 October 2009 by Brando
HDX:
IP Address: 192.168.0.9
Subnet mask: 255.255.255.0
Gateway: 192.168.0.94
Address mode: static
Front panel IP Address: 192.168.0.8
Thanks for help again!
Brando
IP Address: 192.168.0.9
Subnet mask: 255.255.255.0
Gateway: 192.168.0.94
Address mode: static
Front panel IP Address: 192.168.0.8
Thanks for help again!
Brando
Posted on: 29 October 2009 by Brando
Any idea what should I do next?
The previous owner used HDX with MacBook, if that is relevant to you.
The previous owner used HDX with MacBook, if that is relevant to you.
Posted on: 29 October 2009 by AV@naim
I suspect your LAN netmask is the issue. In reality 192.168.x.x ranges require a 255.255.0.0 mask. Commonly this is set to 255.255.255.0 as your's is. That mask is blocking SETIP Tool from "seeing" the HDX on the alternate subnet.
There are 2 ways around this:
Either (you will need to refer to your routers manual):
-go in to your routers LAN setup section (I don't know what make or model so I can't help with this bit)
-set the LAN IP range netmask to 255.255.0.0 and apply the setting
-restart you PC (just to make sure new setting sticks)
-run SETIP tool again and it should find the HDX
-set the HDX to DHCP
-set the mask setting on the router back to 255.255.255.0 if you require
Or, the other way requires you setting the PC to a static address/mask that is compatible with the HDX's current settings and directly connecting the HDX to the PC Ethernet-wise (which requires a few more steps). I think if you want to try this way you should contact the factory.
(This is another reason why we suggest HDX's are run in DHCP mode. Moving a unit with a static IP setting, to another location with a different LAN IP range is grounds for misery)
There are 2 ways around this:
Either (you will need to refer to your routers manual):
-go in to your routers LAN setup section (I don't know what make or model so I can't help with this bit)
-set the LAN IP range netmask to 255.255.0.0 and apply the setting
-restart you PC (just to make sure new setting sticks)
-run SETIP tool again and it should find the HDX
-set the HDX to DHCP
-set the mask setting on the router back to 255.255.255.0 if you require
Or, the other way requires you setting the PC to a static address/mask that is compatible with the HDX's current settings and directly connecting the HDX to the PC Ethernet-wise (which requires a few more steps). I think if you want to try this way you should contact the factory.
(This is another reason why we suggest HDX's are run in DHCP mode. Moving a unit with a static IP setting, to another location with a different LAN IP range is grounds for misery)
Posted on: 29 October 2009 by Brando
I managed to find the LAN configuration (via web browser) and here is what I see:
For LAN configuration I see IP address: 10.0.0.2
Subnet Mask: 255.0.0.0 which I changed to 255.255.0.0
There is also DHCP Server which is enabled and some more about "user defined start and end address"...
I tried to recognize the HDX but nothing worked.
Does it matter when I plug the LAN cable into the HDX? Before turning it on, or while it's still on?
Maybe it's because I have 2 routers, to be precise. One is my modem/router given by my internet provider and the other is Linksys wireless router. So, the cable connecting the HDX is coming from the first router (I also tried the other way). And the PC is always connected via WiFi.
Trying to give you as much information possible to make it more easy...
Thank you for your effort!
I appreciate it!
Brando
For LAN configuration I see IP address: 10.0.0.2
Subnet Mask: 255.0.0.0 which I changed to 255.255.0.0
There is also DHCP Server which is enabled and some more about "user defined start and end address"...
I tried to recognize the HDX but nothing worked.
Does it matter when I plug the LAN cable into the HDX? Before turning it on, or while it's still on?
Maybe it's because I have 2 routers, to be precise. One is my modem/router given by my internet provider and the other is Linksys wireless router. So, the cable connecting the HDX is coming from the first router (I also tried the other way). And the PC is always connected via WiFi.
Trying to give you as much information possible to make it more easy...
Thank you for your effort!
I appreciate it!
Brando
Posted on: 29 October 2009 by Brando
Forgot to mention,
I didn't see any LAN netmask, only this subnet mask.
Is it the same or...?
I didn't see any LAN netmask, only this subnet mask.
Is it the same or...?
Posted on: 29 October 2009 by AV@naim
Ah I see, so, your LAN IP range is on 10.0.0.x and the HDX is statically set to 192.168.0.9. then the above is not relevant.
First set the subnet mask on the router back to 255.0.0.0.
10.x.x.x ranges use a 255.0.0.0 subnet mask
192.168.x.x ranges use either 255.255.0.0 or 255.255.255.0 subnet masks
You must have the Ethernet cable in the rear of the unit before you turn it on - if you are using it on a network
Lan netmask is the same as subnet mask yes
Next step, try downloading and using the latest SETIP Tool from here (Public->HDX Section->Desktop CLient and SetIP Tool htm):
http://www.naim-audio.com/download/
Once this is fixed, I would advise you read the documentation on this site also.
If that fails, contact the factory at this address: info@naimaudio.com
First set the subnet mask on the router back to 255.0.0.0.
10.x.x.x ranges use a 255.0.0.0 subnet mask
192.168.x.x ranges use either 255.255.0.0 or 255.255.255.0 subnet masks
You must have the Ethernet cable in the rear of the unit before you turn it on - if you are using it on a network
Lan netmask is the same as subnet mask yes
Next step, try downloading and using the latest SETIP Tool from here (Public->HDX Section->Desktop CLient and SetIP Tool htm):
http://www.naim-audio.com/download/
Once this is fixed, I would advise you read the documentation on this site also.
If that fails, contact the factory at this address: info@naimaudio.com
Posted on: 30 October 2009 by Brando
So, you were saying to back everything the way things were and to download the newest software.
I did all that and nothing... I will try sending an e-mail to the factory.
Thanks for your help!!
It's probably some small change that needs to be done and I simply don't see it...
I did all that and nothing... I will try sending an e-mail to the factory.
Thanks for your help!!
It's probably some small change that needs to be done and I simply don't see it...
Posted on: 30 October 2009 by AV@naim
I had another thought.
I think the issue here is that you are using your wireless network connected PC (on 192.168.x.x range) to try and talk to a static device (192.168.1.x) that is connected via a 10.x.x.x range. Messy...
The ideal way would be to connect your DHCP enabled PC directly to the 10.x.x.x network via Ethernet cable and then run the SETIP Tool.
Can you try this? I will get someone to contact you via mail anyhow.
I think the issue here is that you are using your wireless network connected PC (on 192.168.x.x range) to try and talk to a static device (192.168.1.x) that is connected via a 10.x.x.x range. Messy...
The ideal way would be to connect your DHCP enabled PC directly to the 10.x.x.x network via Ethernet cable and then run the SETIP Tool.
Can you try this? I will get someone to contact you via mail anyhow.
Posted on: 30 October 2009 by Aleg
You should keep the whole of your home network in just one sub-net, either 10.x.x.x or 192.168.x.x, and not mix both together. That will become, as AV@Naim said, indeed messy and very difficult to maintain.
Wired or wireless doesn't matter, and their should be only one router which acts as a DHCP-server, the other 'routing'-devices should be setup as bridges.
At home I operate a combined wired/wireless network with several switches to join wired branches and 2 bridges to join wireless branches, but they are all part of the same subnet with one DHCP-server and one AccessPoint. Never experienced any problem whatsoever.
Just keep it simple.
-
aleg
Wired or wireless doesn't matter, and their should be only one router which acts as a DHCP-server, the other 'routing'-devices should be setup as bridges.
At home I operate a combined wired/wireless network with several switches to join wired branches and 2 bridges to join wireless branches, but they are all part of the same subnet with one DHCP-server and one AccessPoint. Never experienced any problem whatsoever.
Just keep it simple.
-
aleg
Posted on: 30 October 2009 by Brando
DID IT!!!
50% is done! HDX is on the network and album art is downloaded smoothly.
What is not good is that Desktop client is not working properly. Says it can't connect to HDX even after being recognized by the program.
Will post more about it later...
THANK YOU ALL for help!!
Appreciate it!
Brando
50% is done! HDX is on the network and album art is downloaded smoothly.
What is not good is that Desktop client is not working properly. Says it can't connect to HDX even after being recognized by the program.
Will post more about it later...
THANK YOU ALL for help!!
Appreciate it!
Brando
Posted on: 30 October 2009 by AV@naim
If you are using the Desktop Client via the same method as you were using the SETIP Tool, you will have the same issue. Discovery acroess different IP subnets/ranges is not reliable, if not impossible.
Best option is have one DHCP server on your network, so the Ethernet and WLAN are on the same range.
Best option is have one DHCP server on your network, so the Ethernet and WLAN are on the same range.
Posted on: 31 October 2009 by Brando
I managed to change modem's IP address and subnet to match HDX's parameters.
WiFi router is actually only a bridge because it doesn't have a telephone jack on it and haven't got any instructions for it. Only one press of a button and it is sync with the first modem.
As for desktop client, Phil Harris told me that Desktop client isn't compatible with Vista. And the new version of the software will come out soon (for both Win. Vista and 7).
I will just wait a while for the new software!
WiFi router is actually only a bridge because it doesn't have a telephone jack on it and haven't got any instructions for it. Only one press of a button and it is sync with the first modem.
As for desktop client, Phil Harris told me that Desktop client isn't compatible with Vista. And the new version of the software will come out soon (for both Win. Vista and 7).
I will just wait a while for the new software!