N-serve won't see server - new router cause?

Do you know if either the nas or the nserve had fixed IP addresses before?

Download Fing Network scanner (free) from the app store and see if the server is on the network with an IP address. 

Gary's point is key.. If fixed before, best move to DHCP, at least initially. The new virgin router probably will  be working with a new subnet, in which case the fixed addresses you used before will be incompatible.

if this is not the case and you are using DHCP, you might want to temporarily insert a LAN switch between components.. This will help remove any possible intermittent filtering of any layer 2 discovery used by nserve etc by your Virgin home network equipment.

If still problematic you try and download basic analyzers etc to look at your LAN.. But I suspect the answer lies above...

Simon

This is probably going to be an IP address issue. John's suggestion is a good start point and you can probably look at your router's control panel to see if the devices can be seen or scanned for. It shouldn't take a lot of sorting out.

I think the NAS has a fixed address but will check when home this evening, I take it the NAS is the server not the US?

I tried Fing a while ago but is the server the NAS or the US?

I am assuming here that your nas has the music on, its not actually a server in respect of a uniti serve as the serve will simply link to it via SMB. However the issue remains. If the qnap is a fixed IP, it may well sit out of the range of your new router, meaning it won't be seen.

The is a bit of software from qnap to scan the network and find your qnap regardless, sorry cannot remember what its called. Once you find your qnap with it, you can set it back to DHCP.

However you need to be a little more explicit with what nserve is telling you though. i.e. if its saying it cannot find the serve, then thats not related to the QNAP.

Gary is referring to Qfinder, which while not a bad idea to run to see if it can find your QNAP (and what its IP address is, to compare to what the uServe things the IP address is), isn't going to get at the route of the issue.  If n-Serve says it can't find the server, it's the uServe it can't find.

This is driving me mad, the NAS is on 192.168.0.8 but the n-serve thinks it is on 192.168.0.12.

I have tried to set the n-serve manually to 192.168.0.8 but then it says it can't find the server? Autoconnect wants to take me back to 192.168.0.12.

Qnap all up to date with latest firmware which it sees from my windows 7 pc

Any ideas before I lose the will to live much appreciated!

On the Router (virgin superhub) Qnap is showing as 192.168.0.8 Q Finder sees NAS as 192.168.0.8

What is the n-serve. N-serve is software. Are we talking about a UnitiServe? I recently swapped to Virgin - the hub thing is rubbish - you'd be well advised to get an Asus router and put the hub in modem mode. 

Yes I am using a Unitiserve (US) which I am just rebooting. Back in the day, wind the record player up, chuck on a 78 and drop the needle and music, now its so beep beep complicated if you don't have an IT degree!

When I put the settings for n-serve to auto detect no servers are found, if I take off auto connection then put in the IP address for the NAS it doesn't work\

Can you use the set IP tool to unfix the fixed IP? Get it all working with DCHP and then refix it. When I moved to Virgin I had to use the old Draytek to unfix everything, then effectively start again. I'd get an Asus in any event. 

N-serve needs to be looking at the Unitiserve, not the NAS. although you can use a NAS as a server, if you are using n-serve to control your playback as well as your ripping then the NAS must be there just as a store or a backup or both.   n-serve wants to talk to your Unitiserve.  So setting n-serve to look for the NAS is never going to work.  I agree with the suggestion made earlier of using Fing from the App score to discover what IP address your Unitiserve is using and then set that in n-serve.

if you can't fix this over the weekend then I would advise that you ring Naim support next week. They are very helpful and will be able to sort it out for you. I suggest ring rather than email because that way they can get to how you are actually trying to use the Unitiserve and the possible solutions will flow from that.

hope this helps

David

Success of sorts, N-serve now sees NSSRV04C7 as Naim HD player but isn't seeing the music on the NAS. Fing is seeing both. More head scratching

If you go into settings in the n-serve App, you have to have the button next to the Unitiserve selected.  It's green in the latest version of n-serve and it's the top thing in settings.

n-serve only sees the Unitiserve.  The Unitiserve is what sees the NAS.

david

Thanks, in Nserve in settings it shows NSSRV04C7 Naim HD player under the banner Select Server with a tick to the right, auto connection, stay connected and rip mode are all slid to the right so green.

App version is 2.11 (10536) and server version is 1.7a_sp1 which I think is up to date.

If I refresh cache it says Music Library Synchronised but no music.

I feel I might be getting close . . . .

I'm not really sure what to suggest. Is your Unitiserve an ordinary Unitiserve or a Unitiserve SSD? If the former then the music is stored on the Unitiserve and not the NAS. The NAS is normally used for storing backups.  If it's an SSD then the music is stored on the NAS, but I'm not familiar with how you tell the Unitiserve where the NAS is.  I think you do this with the desktop software running on a windows PC or a Mac.  

And are you playing back by a hardwire connection from the Unitiserve to your preamp or are you streaming it? If you are streaming it, then the obvious questions are can your streamer see the music and does the Naim streamer App see the music?

best

David

The US is not SSD as far as I know, it is cable connected to the router as is the NAS and both show on Fing. Through the network I can see all the music stored on the NAS and the capacity is bigger than the Naim unit capacity so I am pretty sure it is only stored on the NAS.

I think I will have to wait until Monday and make time to contact Naim as it is probably something so simple I am just not seeing it. Before the move all was working 100% so it is very frustrating.

THANKS TO ALL FOR YOUR HELP!

n-serve only ever sees the US and not a NAS.  If the music is stored on a NAS then the n-serve Appp should normally see that via the US. I don't know why anyone would set up a US to save all its music on a NAS instead of internally. The older US has a 1TB HD and should save about 1000 albums even in WAV, more in FLAC, and if it's a recent US it will have a 2 TB HD. A NAS used as a store should just add more capacity to the basic capacity in the US and can also provide a backup for the music stored in the US. Anyway whatever, I suspect your issue is that your US for some reason isn't seeing your NAS.

i have read on this forum of several members who have had problems with Virgin Media Superhubs.. If Naim support can't sort the problem then I would suggest that you next do what Hungryhalibut suggested and use the superhub just as a cable modem and use a separate router. Or another possible and perhaps simpler approach is to connect the superhub, still set up as it is now, to a switch, for example a Netgear GS105 which is cheap and effective.  You can buy a GS105 from the well known big online supplier or the well known auction site for £25 or thereabouts. Then you connect the NAS and the US to the switch instead of to the router. They will then each continue to get an IP address from the router as at the moment but communicate with each other via the switch rather than the superhub, which should be a foolproof way of making sure the US and the NAS can see each other properly.

Anyway I hope you can get it sorted and do please let us know what happens!

best

David

Because you have better control of backups, redundancy and disaster recovery. I used this arrangement with the HDX.