NDX and Asset

The problem is very likely at the server end.  I take it that Asset is running on your pc?  Have you rebooted the PC, and restarted Asset?  I would focus on that end, vs. repeated restarts of the NDX.

Agreed. Find the Asset UPnP configuration and try a Refresh All

Hi, Bart, yes, Asset is running on a PC (it's a gigabyte Brix running specifically as a music server).  I've rebooted the PC several times and restarted Asset.

I'll try a Refresh All, CDBoy, and see what happens - thanks for the suggestion.

I had problems with other PCs on the network when I returned - they picked up strange IP addresses when re-booted.  I finally got them all working, not sure how.  It seemed to be when I replaced the TP-Link IP-over-mains unit fed from the router (which is why I wondered whether the NDX had a faulty IP address, and so couldn't talk to the PC).

Cheers

Steve

Also check that Asset is configured as "Local Account" rather than as a "Service" or disabled.

If Asset is running on ANY ip address on the network (that the NDX can see), the NDX will find it.  It should not matter if the specific IP address of your server has changed; certainly after a restart of the NDX, which you did several times, the NDX would have found it if it was findable.  

One more thing -- is it the NDX itself that cannot see it, or the Naim App?  You can get inconsistent results if you have some issue with your wifi, etc., you might not see your server with the Naim App but the NDX box itself will see it (when you use the front-panel buttons and display to find it).

Good thought - it is the Naim App that is saying that it can only see the Logitech server.  I will check the NDX when I get home tonight.

Thanks

Steve

I have tried Refresh All on Asset, and then restart asset.  No change.  On the NDX itself if I press Input and get to UPNP it does not give me a list of UPNP servers - just shows a track, and I can then move through the different tracks.  I'm pretty sure that this is going through the Logitech server.  It will play those tracks.

Also, the NDX keeps saying Restoring History 80% and sits on that for ages - not sure what that means.

Cheers

Steve

Can you please describe your network and check the ip-numbers from your devices. Another way to find out what is wrong is to switch all devices off and then start only the devices you realy need. So only the rooter, asset-pc and ndx. If this works you have a problem that don't belong to the music-system. Maybe it is a solution to get a fixed ip for the ndx.

NDX stuck on 80% restoring memory is not good.   Do you have it all set to DHCP ??  if not please do so.     I agree the Reinbert about switching off & restart,  but would add to leave the router off for 5-10 minutes to be sure the ISP knows its offline.  Then start up each part sequentially, starting with the router & let that finish its full start (reboot) process,  then the PC & let it get fully booted up,  then the NDX last.    -  then go buy a proper NAS 

Mike-B posted:

NDX stuck on 80% restoring memory is not good.   Do you have it all set to DHCP ??  if not please do so.     I agree the Reinbert about switching off & restart,  but would add to leave the router off for 5-10 minutes to be sure the ISP knows its offline.  Then start up each part sequentially, starting with the router & let that finish its full start (reboot) process,  then the PC & let it get fully booted up,  then the NDX last.    -  then go buy a proper NAS 

agree with Mike B the order of re booting is important everything but be in order then the NDX should pick up the IP address

If any of your IP addresses start with 169, you may have a network problem. 

Not a  necessarily a network problem as such, but a DHCP problem, essentially your PC or device is looking for a DHCP server, probably on your router, hasn't found one and uses a link local type address (starts with 169.). In some circumstances this is fine, but not for home streaming or web access etc.

Simon

Network consists of a DSL modem/router (was a Billion, now a TPLINK - more on that later), with several PCs connected on ip addresses 192.168.1.nnn.  I am running IP over mains for some things, including the Brix and the NDX.   All was working well before I went on holiday (always knew holidays were risky), and all PCs had problems when I got back.  Fiddled around for ages to get the PCs all working correctly, not sure what got them going.  Booting the router and then the PCs kept ending up with totally different IP addresses for the PCs (169.something) with no gateway showing.  Kept rebooting and eventually all (except the NDX) was working.

Decided that the Billion was acting up so put a TPLink Archer VR2600 in instead.  That is now working using the same 192.168.1.nnn addresses I had before.  Now all PCs are on the network OK, with internet access.  

The only change at the NDX end is that I now have two Logitech media servers showing, plus Windows Media Server and the Archer VR2600 (though there is no music on that, as yet, anyway).  My squeezebox works OK, connecting to the server on the Brix.  But the Asset upnp still doesn't show on the NDX.   The NDX is definitely seeing the Brix (the Logitech server is on there, though I'm not sure why it sees two - probably seeing the one on my main PC).  

Still keep getting the Restoring History thing - starts off at 10%, quite rapidly gets to 80% and no further.

NDX is set to DHCP.

Not sure how an NAS will help - I have several but only used as file stores, not sure how to put Asset on any of them.  

Cheers

Steve

Steve can you temporarily remove the Ethernet over mains devices to see if your DHCP kicks in. DHCP needs a fairly reliable network, and Ethernet over mains sometimes isn't. Not sure why now not working after holiday, but perhaps some other change has happened such as a neighbough starting to use Ethernet over mains as well and it has just made those connections in your house now not sufficiently reliable,

Simon

Thanks Simon - that makes sense.  I guess the Billion (which is a little old) didn't like being turned off.  I know I hate being turned off.  Since being on holiday the network here has been having real trouble, with the various devices losing their IP addresses.  This PC (the main one as far as I'm concerned) is wired directly into the router.  

I'm hoping the TPLink should sort that side of it out.

Unlikely to be a neighbour - nearest one is about a mile away.  The mains to this house comes in via a large transformer on a pole - no-one else is this side of it.  

I could remove some of the mains-ip devices, but the NDX is too far away to be wired directly to the router.  Unless I take it out of where it is and move it into the study for a bit.

Cheers

Steve

Ok, if neatest neighbour  is a mile away it won't be that.. Yes just temporarily move the NDX closer using an Ethernet connection to see if it starts to work with DHCP. If no different then unlikely to be the mains Ethernet adapters.

Simon

I'll try that over the weekend.

Thanks

Steve

One thing that puzzles me is that the NDX is evidently seeing the PC that has Asset on it, because it sees both the Logitech server on that PC, and the Windows Media player.  

i though your NDX wasn't getting an IP address? However I suspect it must be if it can see other servers advertising them selves. 

BTW when you disable the WMP and Logitech on your PC does Asset appear? Sometimes not a good idea running all these similar services on the same machine as the software can get confused with port assignments. I seemed to remember Asset should try and handle this - but just a thought.

If you open File Manager in Windows and expand the "This PC" Section can you see the Asset icon listed under "Network Locations" ? If so, you should be able to click on the icon and open up Asset's browsing views (Artist/Albums/Playlists etc.). This will at least let you know whether Asset is running and configured correctly.

Hi Simon,

At one point I wasn't sure that it was getting an IP Address, because it showed no servers.  Now it is showing 4 of them, but none are Asset.

SJBabbey - Yes, I can see the Asset on Ptilota from my other main PC (Laminaria).

So it looks like Asset is running OK, the network is setup correctly now - but the NDX doesn't want to play just yet.  I'll try some more reboots.

Cheers

Steve

Well, very weird.  I haven't done anything to it today, but now it can see Asset and use it.  I have no idea what has changed - no reboots, no restarts - nothing.

At least it's now working.  

Thanks everyone for your help.  

Cheers

Steve