I recently moved my NDX to a room which is served by a CAT6 cable which goes to the ADSL modem in another part of the house. Because I want to use the streaming capability and the Minim Server that I have running on my Mac in the Music room I needed to get a network switch. I chose a Netgear GS105 v5 5 port Gigabit switch.
When I connected the NDX to the switch it was able to play CD rips (44.1 kHz at 16 bits) quite well. However, I discovered that all high resolution files from the Minim Server would “stutter”. They would play around 5 seconds of music and then pause for 5 seconds. This made it impossible to listen to high resolution music.
So I started researching what might be going on. The problem seemed to be the speed of connection being passed from the Mac to the NDX. In the process, I discovered that network switches work at different speed on different ports. Why on earth wouldn’t you run flat out at the fastest speed you can at all times? I never got an answer to this.
But I did discover this website that told me how I could “log into” the switch using a web browser and set the speeds to the highest setting. It was quite a complicated thing where you have to set your computer IP address and subnet address to some magic value and disconnect the internet from the switch.
Unfortunately, it didn’t work. The thing resolutely refused to accept any attempt to connect. Upon further investigation it transpired that the switch I bought was an “Unmanaged” switch which means that you can’t set anything on it. Why on earth would you make such a thing? I did find the answer to this one, these “Unmanaged” switches automatically adjust the speed of the port to match the speed of what it is connected to. So if you are lucky and the devices broadcast the right speeds to the switch all should be well.
But it was still stuttering when I set the computer back to automatic IP addresses (the so called “DHCP”) and reconnected the internet.
Then I thought I would try turning off the switch and starting it up again. Hallelujah! I could now listen to high resolution files. Because I had the switch running before I turned on the computer or the NDX it didn’t know that the two could communicate at high speed it defaulted to ridiculously slow speed. When I restarted the switch while the NDX and computer were running it picked it up and adjusted itself accordingly.
So, if you have stuttering on any network device be it NDX, ND5XS, Muso etc first try disconnecting and reconnecting the power to your switch and see if that does it for you.
Now I have one remaining question: Why does one of the lights on the right side of the Ethernet port on the NDX glow orange instead of green like every other device known to man?
Posted on: 24 March 2017 by ChrisH
Jack from Adelaide, strange that you posted this now. I also have an NDX, hard wired to the network via a managed switch.
I have had the symptoms you described several times over the last couple of years, streaming CD's no problem, but move to High Res files, constant buffering, most recently on Monday this week. By a process of elimination I also found that by turning the switch off and then switching it back on again always cleared the problem.
I started off powering the whole Naim system & network down before systematically rebooting, which was a real pain, but eventually came to the realisation that it was just the switch that needed rebooting. It still reoccurs from time to time, not often, but enough for me to remember what I need to do.
Its almost as if the switch goes out of sync for some reason, and I have had it happen on my GS105 as well as on my 'new' (2nd hand!) sooper dooper Cisco switch, so I cant say its one switch or another that suffers with it. Maybe I should try and log in to the switch to see if I can adjust the speed as you mentioned, see if that stops it from happening for good.
Posted on: 24 March 2017 by Bart
As mentioned, NDX is not "gigabit" capable. And it doesn't need to be. A 100Mbps ethernet is plenty fast for hi res music, and a modern standard switch can handle this. Something is amiss with the network hardware; the switch or the cables . . .or something!
It can also be something else on the network that is causing conflicts, such as an Amazon Echo, or a faulty Apple Time Capsule.
To remove the latter possibility, strip down the network so that all extra devices are removed, and if you're no longer getting dropouts, add them back 1 by 1 until you find the offensive device.
Posted on: 24 March 2017 by ChrisH
For me at the moment Bart it is an infrequent occurrence, so a simple disconnect / reconnect of the switch does the trick and is fine. I guess if it was a regular occurrence it would be a different story and 1x1 solution you mention would be the way to go, though I don't have any such devices as mentioned.
Seems like Jack from Adelaide is also sorted by the sound of his post.
But its worth noting in case anyone else should have a similar circumstance.
Posted on: 24 March 2017 by Jack From Adelaide
Hi all,
Yes, I notice that most people who post on forums are asking questions but few are offering solutions. So I thought I would redress the balance!
As Chrish said, it's simply a matter of powering off the switch while it is connected to the NDX, Computer and the ethernet to the outside world.
Incidentally, here is an interesting observation that I made during my troubleshooting: You would think that one configuration which would HAVE to work would be just your computer connected to the NDX wouldn't you? Actually it doesn't work at all because all the ethernet devices have an address which is assigned by a thing called a DHCP server and when you aren't connected to the ethernet (and your ADSL modem) there is nothing to assign the addresses so everything just sits there in a state of confusion. I haven't tried it but I would hazard a guess that if you were on a mountain top in the Himalayas without internet connection you could probably assign a so called "static" IP address to your computer and the NDX. I am sure Naim would have thought about this. (I heard the Hi Fi market in the Himalayas was sky high...)
Incidentally Chrish, by an amazing coincidence I pronounce the name Chris exactly the same as your member name after I have had a few glasses of Coonawarra Reds...