Connecting a Unitiserve-SSD to an Apple network
Posted by: AndyF on 03 December 2015
I've borrowed a demo US-SSD until mine arrives. It is connected directly to an nDAC, but the issue I have is the ethernet connection to my network. I bought a Cat 6 ethernet cable and have tried connecting directly to either the NAS (Western Digital Ex4100) or into the Apple AirPort Extreme, or into a powered network adapter. I've also tried an alternative cable known to work. Each time I get the same result, the ethernet LED link and data lights are green at the network end, but solid dark orange on the link side and flashing orange on the data transfer LED's at the US end of the cable. Neither Safari, n-Serve (OSX), n-Serve (iOS), or Finder can see the US. I have tried rebooting a couple of times but to no avail.
Any ideas?
It sounds like your borrowed device is set to a specific IP or DNS which is not your networks. I don't know how to factory reset US, but assume its possible.
If not then you need to find a PC in order to use the naim IP tool to set the IP settings of the US to either an IP/DNS in range on your network or to DHCP.
Thanks Garyl, from the reference manual I think you're probably right that it is operating in 'local' mode. I'll hook up a Windows laptop to it later and try that.
There is nothing "special" you need to know to use Apple home networking hardware, other than by default Apple routers use a different range of IP addresses than most others use (most others use the 192.168.1.XXX range). If the nServe is set to get an IP address dynamically, there should be no issues. If, as Gary surmised, it has been set to a fixed IP address, you need to un-do that.
Something that the nServe seems to require, which as far I can tell still is not documented, is that you need to set the workgroup name to naim instead of the typical default of home.
See if those two things do the trick!
Thanks for the tip re naming the workgroup Bart.
I've brought my office laptop home and downloaded the Naim IP Tool on it and have directly plugged the ethernet cable from the US into the laptop. It can't see it. Tried re-booting the US but still nothing. If the IP has been set or if it is on a 'local; setting to ignore the internet to just play cd's, do I try another means of connection - e.g. usb? How do I make a US 'discoverable'? Otherwise I'm just taking this loan US back to the dealer.
I think you need to leave the US on your network then try to find it with the laptop.
Workgroups? I thought that was a Windows thing.
Thanks Chrissu
Workgroups does = Windows, but then Naim appear to like Windows rather than Apple - WAV is the native file format not AIFF and the desk top client / IP tool said to give the best range of tools is for Windows - probably half the problem.
Chrissu, OK plug your laptop and uS into your router switch.. Let the laptop gets its IP address from your router (DHCP). Ensure when the US is plugged into your router switch port, the LED is lights on the router switch port to the US.
now run the Naim tool. It should use a low level device discovery protocol that doesn't need IP addresses to work. Hopefully once the tool is finds your US you can resolve. Set to DHCP. Really bad idea not using DHCP on clients if that's the course.
Simon
Btw I skimmed the US manual, and didn't see the IP set tool mentioned.. So not sure it's compatible, others will confirm..
might need a factory reset, as DHCP is the default mode of operation.
Thanks for the replies Simon.
I now have both the US and Windows laptop connected by ethernet cables directly into the Apple AirPort Extreme. On my iPhone I'm running Net Analyzer - an app that Phil from Naim recommended on another thread. The app identifies the laptop but not the US. I've tried re-booting the US but to no avail. TBH I'm not sure what name the US would show - I have a couple of Unknown's but one has Hewlett Packard against it and the other Apple so I'm guessing its not either of them. If this needs a factory reset due to this then a) its a bit of a design flaw IMO, b) I'll just hand this one back and wait for mine to arrive.
I would call your dealer to see what they have done to your borrowed US. I am not sure the Net Analyzer will work - really that is only a consumer tool to show device responsiveness and the responsiveness of certain application services once correctly setup.
So - assuming no fault anywhere - you need to get the US into working as DHCP - not being that familiar with the US and reading the manual - that should be default operation or requires a device reset.
Apparently if the device doesn't detect a network connection only then does it start in local mode. This is removed according to the manual by connecting a physical Ethernet connection and restarting which appears what you are doing
Simon
Thanks again Simon,
Spoken to my dealer - they're contacting the branch it came from to see if there are any ideas as to what's what. Will update when i can,
Cheers Andy.
Is your Airport Extreme also your DHCP server? Mine isn't, it's connected to an ISP provided box which does that. If so, try connecting the Unitiserve to your ISP modem/router. You might be able to see it there, and set an IP address in its settings menu if necessary.
...also, have you looked in either N-Serve for Mac (NOT the iOS version) or the Desktop Client to see what IP address the Unitiserve has? At least you might be able to see if it's had an IP address allocated to it, and maybe which server has controlled it .
Latest update is the branch dealer who supplied the US to my local branch have confirmed they set a fixed IP address as the US had previously been used in a NaimNet configuration and then didn't reset it to DHCP. So now I know the problem I need to get at it somehow. I've tried connecting both directly to my Sky Hub as Chrissu suggested but still can't see it as the IP range the Sky Hub is looking at appears to be the same as my Apple AirPort Extreme - i.e. 192,168.0.xxx rather than 192,168.1.xxx. Not sure if there is a quick way for me to resolve this without risking messing up my network.
I'm not sure I need to spend much more of my time trying to sort out a borrowed US, but it does occur to me that this can't that rare an event - surely there's a fix available and for that reason alone I'd like to see this through.
Do you know which device is acting as DHCP server for your network. My understanding is that it's best to let your Sky router do that rather than the AE.
If you now know the Unitiserve IP address, type that into a browser (Mac or PC) and you should see the DTC. In Settings > System Status you'll be able to see all the device's network settings (DHCP status, MAC address, etc.)
If you look in UPnP settings, there is a 'reset to defaults' option, but I'm fairly sure this will not affect the IP address. No harm in you doing it anyway, though. To get rid of the offending static IP address you're still going to need the SetIP tool. If you connect both the US and laptop to your Sky router, and the laptop workgroup is set to NAIM, it should work......?
If you're still getting nowhere, at least you can relax in the knowledge that when you get your own Unitiserve, you won't need to do any of this - just leave it on DHCP.
Good luck.
If you install fing on your iPad it will show you the IP addresses of everything connected to your network.
AndyF posted:Thanks Chrissu
Workgroups does = Windows, but then Naim appear to like Windows rather than Apple - WAV is the native file format not AIFF and the desk top client / IP tool said to give the best range of tools is for Windows - probably half the problem.
Not QUITE right. The uServe runs a version of Windows, and the workgroup name that the uServe wants is naim, not the standard default of home. Whether you're accessing the uServe from a Mac, or a PC, you need to take account of this.
The uServe is perfectly happy connecting to Macs as well as PC's. But it won't be happy with either until the workgroup name is set to naim, as far as I understand (and experienced when I first set mine up ~ 4 years ago).
Hungry halibut - That sounds like the Network Analyser app which I have, but as someone else has said these apps only tell you what devices are actually connected and therein lies the problem - it's not connected.
Chrissu - I don't know the full IP address I'm waiting for the branch to text me but a search on 192.168.1 suggested thats a range generally used by Linksys routers - I guess I could try increasing he last digit by 1 each time...192.168.1.1, 192.168.1.2
AndyF posted:Chrissu - I don't know the full IP address I'm waiting for the branch to text me but a search on 192.168.1 suggested thats a range generally used by Linksys routers - I guess I could try increasing he last digit by 1 each time...192.168.1.1, 192.168.1.2
Yes, you might well find it by trial and error like that. Just type the IP addresses into a browser until a Naim screen appears....
Chrissu - I gave up at 192.168.1.70. Glad I did as it turns out the address is 192.168.1.248!
Had a quick try putting that IP into my iMac browser (Safari) but didn't come up with anything - will spend more time on it tonight.
one thing that does occur to me, the Naim SetIP Tool doesn't provide a facility to enter a specific IP to make the initial connection, it simply scans looking for a server and allows you to change the address once connected. Not sure this is taking me anywhere.
Hi,
If the UnitiServe has been set to a fixed IP address for a NaimNet setup then it will need reconfiguring using the NaimNet / NetStreams software which only runs on a Windows PC ... randomly poking around looking for it will probably not result in anything other than frustration. It's a great shame that the dealer sending out this unit didn't reset it to DHCP before it was sent out.
If you have access to a Windows PC then I can reset the unit to DHCP remotely using the NaimNet / NetStreams setup software via a remote login.
I also see discussion regarding the Windows Workgroup - the UnitiServe / HDX / NS0x are all by default in the "Naim" Workgroup and it would be normal practice to put any NASs used for music storage into that same Workgroup simply to logically / notionally group them together on the network however this is *NOT* essential for the servers to work correctly and they will happily access / find NASs in other Windows Workgroups.
Tools such as "Fing" can be handy when seeing whether devices 'exist' (or don't) on your local network and similarly "NetScan" can be used to determine whether various protocols used by devices (Ping / Bonjour / UPnP) are being properly supported / propagated on your local network however it is important to understand what they do and what you are trying to find with them and what the results of them mean ... Just as a stethoscope is a tool used by a doctor to do diagnosis they won't in themselves give you a definitive answer.
Cheers
Phil
Thanks for the contribution Phil, appreciate it. It would require co-ordination of me having my office laptop at home at a time you are able to log in to my network. To be honest rather than either of us go to that hassle I may as well wait for my US to arrive, which the branch said on Friday they think will be sometime this week.
Regards
Andy
No problem ... Hope you enjoy it. If you need a hand setting it up then just drop us an email and we'll try to help...
Phil
That's for that, Phil. My own experiences with the workgroup setting must have been an example of observing a result and implying cause / effect on my part. Thanks for clearing it up!