I have a second-hand UnitiServe SSD that I'm having some further difficulties with. Initially, the US would not automatically detect my Synology NAS (412+). I figured out through the forums, thank you, to manually type in the address of the NAS. So far so good. However, if I leave the US alone for an hour or so, e.g. I don't load CD or use it, it seems to lose connectivity with the network. The symptom I typically get is I can't use the N-serve app to connect on my macbook, ipad or iphone. Typically, the program will shut down and give me an error message on the macbook or just send me back to the home menu on the idevices.
When it looses connectivity, all I seem to need to do is restart my Airport Extreme. I had originally had the US in my stereo room connected to a Dlink switch along with my NAS and an Airport Express for wifi. The Airport Express was connected to my Airport Extreme. For testing purposes, I have moved the US next to my Airport Extreme along with the NAS and it is having the same
The funny thing to me that doesn't make this just a network issue is when I lose connectivity and load a CD it appears to not know what to do. It'll start reading the CD and then stops. I'll have to essentially reboot at that point. I called Sound Organisation (The US distributor) and they basically said I need to have the unit repaired without attempting to troubleshoot. I don't think there is something wrong with the US, but rather a network issue.
Any help would be appreciated.
Thanks.
Posted on: 15 January 2013 by busaganashi
Here's what is on my network now:
? (10.0.1.1) at _________________ on en1 ifscope [ethernet]
? (10.0.1.11) at UNITISERVE SSD on en1 ifscope [ethernet]
? (10.0.1.14) at _________________ on en1 ifscope [ethernet]
? (10.0.1.19) at _________________ on en1 ifscope [ethernet]
? (10.0.1.20) at _________________ on en1 ifscope [ethernet]
? (10.0.1.28) at _________________ on en1 ifscope [ethernet]
? (10.0.1.32) at _________________ on en1 ifscope [ethernet]
? (10.0.1.36) at SYNOLOGY NAS on en1 ifscope [ethernet]
? (10.0.1.39) at _________________ on en1 ifscope [ethernet]
? (10.0.1.255) at ff:ff:ff:ff:ff:ff on en1 ifscope [ethernet]
The NAS has been on 10.0.1.36 and can also be on .37 and the UnitiServe is on 10.0.1.11. The US seems to always be on 10.0.1.11. I just set the NAS to be static on 10.0.1.37.
Posted on: 15 January 2013 by Bart
Well I really don't know if it's a network problem or uServe issue.
When you can't connect using n-Serve, can you connect from your Mac just using the web browser? Or does that stop working right too?
I've got my uServe and nas both connected to a Netgear switch, which in turn is connected to my Time Capsule (essentially an Airport Extreme). I've got another Airport Extreme elsewhere in the home, and they bridge the wifi. I use iOS devices with nServe, and never lose connectivity; my uServe runs 24/7 for days and weeks without ever needing to be rebooted. DHCP however is provided by the home (FiOS) router; it's turned off on the Apple stuff. How are you getting out to the internet? If you also have a home cable or FiOS router, do you have a 'double nat' or another problem due to running dhcp services on two routers?
I do see that you use the typical Apple class C network addresses. I have no idea if it'd make a difference, but I use the 192.168.x.x addresses that the FiOS router provides.
Not sure if any of this helps!
Posted on: 15 January 2013 by busaganashi
Hey Bart. No the browser doesn't connect when the US goes offline. The fix is to reboot my Airport Extreme. It just happened. I stuck in a CD and checked. The CD wasn't being burned so I checked the connectivity and n-serve said offline. I ejected the CD and then rebooted my Airport Express. Everything working again.
I have a comcast cable modem. It doesn't have any switching our routing functions. I connect that to the WAN in on my Airport Express.
Posted on: 16 January 2013 by Bart
Well I still don't know . . . but my guess'd be a network issue. You can figure out if it's a problem with your Airport pretty easily. Go to the Apple store, buy a new Airport Extreme, and if it still happens just return it. I"d probably do that to start. (Ive given Apple so much business I'd not feel bad about doing that.)
There is nothing special in my Airport config, other than "Connection Sharing" being "off -- Bridge Mode" as dhcp is performed by my FiOS router.
It sounded like you removed the wireless link between the uServe and the Airport Extreme and it was still happening (right)? It still happens if the uServe is hard-wired to the Airport Extreme?
I just don't know why the uServe would go "offline." Either the network is dropping and it's detecting that, or it has a glitch and THINKS the network is dropping.
If it's not just a fault with your router, you could get in touch with Chris West at AV Options. That's where you'd want to send the server if you need to get it checked out and possibly repaired (be it hardware or software). He knows more about the workings of them than any other person in the States I am pretty confident.
Posted on: 16 January 2013 by Jan-Erik Nordoen
Is the UnitiServe set to "Rip" mode ? Even when offline it will rip, although taking more time until it consults its internal database.
If Yes to the question, then the unit needs to go in for repairs.
Jan
Posted on: 16 January 2013 by Phil Harris
Hi Garry,
It does sound to me like something in your network is either going to sleep or entering a power saving mode ... please try hard wiring your UnitiServe and your NAS *DIRECTLY* to your AirPort Extreme.
Please also be aware that you have set your NAS to a static IP address that is within your DHCP range and this is *NOT* a valid thing to do - either reserve an IP address for the NAS in the DHCP range on your router or set your NAS to a statis IP address outside your DHCP range.
Best Regards
Phil
Posted on: 16 January 2013 by busaganashi
Phil, I have the US connected directly via ethernet to the Apple Extreme as well as the NAS. I bought a new Apple Extreme (which is hooked up to my cable modem) today to see if the old one has an issue. Still testing. I've set up the second one in bridge mode and use it as a switch and to get wifi access to the internet.
Thx.
Posted on: 16 January 2013 by Bart
Just triple-check that your cable modem has no dhcp capabilities. Nowadays a pure cable modem (itself a misnomer) is a rarity. Almost all cable providers are putting a router into the customers' homes.
Does your cable modem have just one ethernet port? Coax in, and one ethernet out?
Posted on: 16 January 2013 by busaganashi
The cable modem only has one ethernet out which goes into my Airport Express WAN. I started over from scratch and re-did everything. It appears that adding my network share for my HD Tracks downloads is causing the problems at this point. I've been up for several hours without the US dropping connection. It only sees the Music Store on the NAS. The HD Tracks is on the same NAS in a different folder. Strange. I'll tinker with the folder and see if I can get it to work.
The other thing I noticed was the previous user had a backup folder on Drive D which I can't get rid of. It shows up in the n-serv application but not on the browser app. I don't see a way to delete it. It doesn't show up on the network shares or music store either. Just in the backup section. Any ideas?
Thx
Posted on: 17 January 2013 by Phil Harris
You're not setting up a nested share are you? Where one shared folder is a subfolder of another shared folder?
I've seen this possible to set up on a few Synology's in the past...
Phil
Posted on: 17 January 2013 by busaganashi
Well I spoke too soon. It is still loosing connectivity. Basically, if I don't access the US for awhile I can't access it when I come back form the iOS devices or the nserv app. I even tried making both the US and the NAS static on my Airport Express and that doesn't work. Starting to think it is the US unfortunately. It's not the NAS since the US and my other devices never lose connection. It's always the US that drops.
All of the shares are in the parent "shared folders" directory.
Posted on: 18 January 2013 by Bart
Originally Posted by busaganashi:
All of the shares are in the parent "shared folders" directory.
There should be a "store" for where the uServe rips to, and then one or more "shares" that are folders that contain the rest of your music (flacs and other stuff that you did not rip). Ideally none of these should be nested. I'd make each of these folders in the root directory of the Synology.
But I'm not sure that that's the connectivity issue; it probably is not.
I can come back to my uServe when it's not been used for days, and it's "there" when I launch nServe on my iPhone. Sorry you've having these troubles -- it's not a flaw inherent in the device, but it sure is a pain to track down.
