Agreed. I’ve officially given up, but before doing so, I did one last hard factory reset which did nothing differently, unfortunately. I’d think it odd that internal wiring would be faulty, as I’d think the rear port LED lights would indicate a fault in functioning. As it stands, everything checks out. It makes zero sense to me for this unit to be recognized wirelessly but not wired. I just don’t get it, even layman as I am.
Regardless, I’m out of options here, as everything I can see, even looking at LanScan, points to, this thing should be working.
I think, unless you’ve told it not to, the google hub will be providing ip addresses to everything wireless connected to it, and the satellite box will be providing ip addresses to everything wired to it, but they will be different networks and discovery will (may) not work between them. The satellite box, if it’s also providing a wireless network (and you haven’t turned it off) will provide ip addresses to anything wireless connected to it - but in this case it’s the same range as the wired, and discovery should work.
If this is all true (big if), you could open your iPhone settings, go to WiFi, tap on the active connection, and tap ‘forget this network’. Then select the satellite box WiFi, and connect to that. Open the Naim app. See if it works…
Of course - I could be completely misunderstanding how your network is set up…
If your iPhone predates the google mesh, it’s maybe possible that it was still connected to the satellite wireless when the NDX was working.
Yes, you’ve done everything you sensibly can and you really shouldn’t need to fanny around like this. It should just work. See if the dealer will let you try another.
Can LanScan see any devices on the wired side of the network?
How can one tell on LanScan which are wired? It really only shows IP and mac addresses, DNS/mDNS names.
Also, I tried what you suggested with my iPhone and it didn’t work, either. Thanks for that, though. AFAIK, my iPhone has always been with this (mesh) network, as was the NDX. Never does it ‘see’ the other unless I ask to join it.
Perhaps @Bart could help. He uses google mesh WiFi with his Nd555. Encountered a similar problem apparently:
My ND555 didn’t want to connect to my Google mesh wifi when I first installed the Google devices. I turned off the Naim player…rebooted the Google network…and then turned on the Naim player. All was well after that.
The Google devices use an entirely different subnet set of addresses than are typical; the Nest will need to be restarted to find that network properly.
Does not anyone know what DAC is in the XS2 streamer?
I believe it’s a Burr-Brown 1791A chip. Why?
Was his issue with wifi or wired?
Thanks @jsawyer09 for the clarification. I know that a DAC is really not the basis for understanding the sound signature of a DAC, but DAC chips do tend to have some form of sound signature. And Delta Sigma vs R2R can also have different sound signatures.
I once read that Naim were doing R2R at some point, so was unsure if this was the basis of their DAC architecture.
1 Like
That’s not a stupid question at all. I have not yet; I was only going to do that as a last resort. I typically try to remove every feasible possibility first before going that route. Luckily, this forum and its members have been an invaluable resource for me to eliminate some of those possibilities. I’ll likely try that after yesterday’s series of no-gos. Thank you!
I finally got this figured out! It was driving me nuts, so had to spend much of last night and over lunch today to get it sorted. I completely shut down and disconnected everything from the downstairs utility room where everything resides. I began to piece it back together and in the process, it occurred to me the Ethernet lead that had once been in the ‘cube’ router (this is the satellite wifi) should possibly go into the Google Nest router, instead. From there it went to the first open ports in the Cisco Catalyst (2960) switch, and the Ethernet lead coming from the music room wall plate (which was incidentally terminated by myself when we had finally finished our house) went to the 10/100/1000 port at the far right. The lights blinked green so felt I was good-to-go.
I then went to the music room and connected an AQ Ethernet cable from the ND5 to the wall plate and opened the Naim app. It recognized it! I went into Network Settings and the WIRED connection was confirmed and Tidal ready to play. It has been playing for the last couple of hours as background while working.
Just to let all of you know who have contributed here that there’s no way this would’ve been possible without your contributions and making me think outside the box a bit. The LanScan helped somewhat, but what really did it was a reminder from this thread:
Lost the lot when connected to router via ethernet and what @Simon-in-Suffolk had pointed out using the Net Analyser app. That’s when things sort of clicked. I kept changing settings in the Google Home app and rescanning on the Net Analyser app to see what differences were being made. None of the changes netted the network to see when I attempted to wire the ND5, but did when wireless. That’s when advice given here prompted me to just go for broke and disconnect everything…that’s when the new connection idea occurred to me.
That said, it is really odd how the old Ethernet connections worked, even though the NDX and app were on the Google mesh system. That is the part that I don’t think I can ever resolve, and at this point I can live with not knowing definitively. The current system works both wired and wirelessly! Thank you again to everyone!
5 Likes
Glad you got it sorted.
I would have used one of the 10/100 ports on the switch to connect your streamer, as it doesn’t have a GB port. Save the GB port on the switch for something that can potentially use the extra speed. (Or just leave it as it is, either way it will work.)
1 Like
1 Like
That’s great.
Please let us know how it sounds when it all settles down and beds in.
2 Likes
Will do! Thank you.
Nice one, well done. Time to enjoy the music.
2 Likes
Happy to help if I can. My ND555 was wired, and the Naim App of course was wifi. Google Nest absolutely works just fine; you just need to have your entire home network – wired as well as wifi – on it. Again, happy to help!
1 Like
Yes - you did indeed fix what was wrong. The Google Nest ‘base’ MUST be your in-home router/dhcp server, for wired as well as wifi.
1 Like
Thanks, Bart!
I, personally, think the Nest is great in every way. The house we just built is three stories; we have a Nest satellite on each floor and the coverage is always ‘excellent’ according to the Home app when running a test.
Admittedly, my problems were self-inflicted, as I simply hadn’t ruled out the then-current Ethernet cabling situation. It wasn’t until it went into the ‘base/router’ to Cisco 2960 and Cat5e wall from top floor music room to an open port on the Cisco did things get sorted. It seems so trivial now, but at the time it simply eluded me.