Sonology Update

Aside from losing out on security updates, I don't have a problem with this approach. It will certainly be less of a hassle down the road. You might consider doing an update every 6 months to a year to get the latest security patches, keeping in mind that you may have to spend some time right afterward fixing a problem. My guess though is you'll only have to one in five times.

Sonology?

I have had automatic updates enabled for all time for my Synology servers and have never had a problem.

Although if you are using some Chinese imitation then you may have a problem.

Perhaps the dealer can be named, then everyone will know to avoid them. 

This could be the start of a new thread - rubbish advice I have been given and believe it's worth passing on to others so they can get it wrong too. 

No problem with doing updates. Just make sure you keep a regular backup of your music stored on the NAS. If an update (or anything else) does cause you a problem then you've always got your backup to restore from. 

I also always carry out the updates and have never had a problem. The only thing that gets on my nerves is the ip address changing at each update. When I first bought the synology a couple of years ago I recall seeing an option to fix the ip address, but I cant find it now. It just means that you have to change the log in details of devices that use the nas after a powerdown or update.

I have never seen an IP address change,  also not heard of it bing reported as a problem so a bit surprised to see your post.

That said,,    I have my BT HH4 - the DHCP (IP address) manager - set to fix the IP addresses on NAS, NDX & iPad.  In the BT advanced setting its checked to "Always use this IP address"    Its still DHCP,  but its told to always use the IP you choose.  

Mike-B posted:

......  I have my BT HH4 - the DHCP (IP address) manager - set to fix the IP addresses on NAS, NDX & iPad.  In the BT advanced setting its checked to "Always use this IP address"    Its still DHCP,  but its told to always use the IP you choose.  

 

Mike's advice is spot on. Its always sensible to use DHCP on a client device. DHCP can then be set to use a fixed address or an address out of a pool for a particular device.

If you don't use DHCP on a client you can really get yourself into a pickle and possibly not be able to achieve network connectivity at all if you change your home network setup.

Simon-in-Suffolk posted:

Mike-B posted:

......  I have my BT HH4 - the DHCP (IP address) manager - set to fix the IP addresses on NAS, NDX & iPad.  In the BT advanced setting its checked to "Always use this IP address"    Its still DHCP,  but its told to always use the IP you choose.  

 

Mike's advice is spot on. Its always sensible to use DHCP on a client device. DHCP can then be set to use a fixed address or an address out of a pool for a particular device.

If you don't use DHCP on a client you can really get yourself into a pickle and possibly not be able to achieve network connectivity at all if you change your home network setup.

Simon, Just to be absolutely clear for those of us who are technologically challenged....are you saying that reserving an IP address on the DHCP server (i.e. router) is OK in this context? As opposed to using the Set IP tool on a Naim device, for example.

Mike-B posted:

Its spelt SYnology

It might be partially true that very little of the updates concern Media Server,  but they do make changes to the OS that are needed in other areas & as in all things computer its best to run the latest.  The next big change is to the DSM 6 series

As for messing things up,  absolutely not so,  I update each & every time something is available & never had a problem.   Your dealer is giving you bad advise my friend.

One of the updates did introduce a problem based on rights assigned to shared folders.  I recall there was a pinned thread on the streaming audio forum regarding it.

I think the best approach is to not upgrade immediately.  Wait 2-3 weeks to let others identify potential problems and workarounds.

One other thing I would definitely NOT do is enable the functionality that allows the NAS drive to be accessed remotely across the internet.  That's just asking for trouble, particularly when new security vulnerabilities are discovered.

ChrisSU posted:

Simon-in-Suffolk posted:

Mike-B posted:

......  I have my BT HH4 - the DHCP (IP address) manager - set to fix the IP addresses on NAS, NDX & iPad.  In the BT advanced setting its checked to "Always use this IP address"    Its still DHCP,  but its told to always use the IP you choose.  

 

Mike's advice is spot on. Its always sensible to use DHCP on a client device. DHCP can then be set to use a fixed address or an address out of a pool for a particular device.

If you don't use DHCP on a client you can really get yourself into a pickle and possibly not be able to achieve network connectivity at all if you change your home network setup.

Simon, Just to be absolutely clear for those of us who are technologically challenged....are you saying that reserving an IP address on the DHCP server (i.e. router) is OK in this context? As opposed to using the Set IP tool on a Naim device, for example.

I originally had my NDS configured to use a fixed address (i.e. not using DHCP) and neither iRadio nore Tidal streaming worked, NDS wouldn't connect to either and eventually timed out.  Once I changed this so my hub (also BT HH4) always provided the same address via DHCP and NDS was configured to get address via DHCP it all worked fine.  So I'd say that Simon's guidance is spot on.

The advice to set DCHP to always allocate a device the same IP address is really good advice. I use WD MyBook Live NAS drives for monthly backups over my network and as they are always allocated their own IP address it allows me to bookmark their GUI addresses on my internet browser in case I need to change their settings or update their firmware and for safely shutting them down etc.

Thanks for the advice guys. Where do I find the dchp settings? Is it in the nas or in the sky router?

The problem I get, usually after an update or power down is that nothing will find the nas and the ip address, I think its the ip address anyway (something like 192.168.0.5) will have changed to say 192.168.0.9, I then have to re enter the new number on the synology apps to log them in again, however, I cant remember having to re log the nds though, it seems to find the nas ok, possibly as its hard wired?

It should be in the router as it is the router which allocates the IP addresses of the devices on your network.

Never had a problem with Synology updates been using a 212j for nearly four years never missed a beat in fact three updates this week all still working spot on.

Mr Happy posted:

Thanks for the advice guys. Where do I find the dchp settings? Is it in the nas or in the sky router?

The problem I get, usually after an update or power down is that nothing will find the nas and the ip address, I think its the ip address anyway (something like 192.168.0.5) will have changed to say 192.168.0.9, I then have to re enter the new number on the synology apps to log them in again, however, I cant remember having to re log the nds though, it seems to find the nas ok, possibly as its hard wired?

The IP address of your router is almost certainly 192.168.0.1

Type that into a browser, and you should be able to see your DHCP settings and edit them if you need to.

ChrisSU posted:

Simon, Just to be absolutely clear for those of us who are technologically challenged....are you saying that reserving an IP address on the DHCP server (i.e. router) is OK in this context? As opposed to using the Set IP tool on a Naim device, for example.

Yes... obviously assuming the Naim device is set to use DHCP which I think is the default.

and also the router address could be 192.168.0.1 - but marginally more likely to be 192.168.1.1 which for technical legacy reasons is a safer class C address and subnet to use - assuming your router is using a class C subnet....

In short you cant take it for granted at all - as your post has demonstrated.

Simon

It's probably a good idea to bookmark your router's IP address in you internet browser too.

Although book marking your routers address could be done -it will in 99.9999% of home networks always be the same as the default gateway or default router address - which will be part of your computer's or any devices IP settings on your home network - given to it by the DHCP

So really easy to find.....

Simon

Thanks Simon. My guess is based on the fact that my SKY router has that address, although in the past they've always ended 1.1

Thanks for all the advice. I will have a look at the router settings. I was with talktalk when the issue occured but a few weeks ago switched to sky, so maybe I wont have the issue again as others seem not to? I had assumed that it was a nas issue and didnt even consider the router. Ive clearly still got lots to learn.

The simple answer is to wait a couple of weeks after the initial release and check the forums for issues.  If there's none, update.  Synology introduce security updates as well as general improvements so it's not always best advice to ignore updates full stop.

Your dealer is not wrong. As long as your NAS is not accessible from the internet and as long you can trust all clients in your (w)lan, it is ok, to not update the system if it does what you want.

The behaviour of the NAS and e.g. Its media server can change with an update. In some versions the deep sleep standby of my DS213+ did not work anymore. Or the mediaserver lost the ability to transcode to wav and still play gaplessly.

On the other hand you will miss improvements (bugfixes, security patches, new functionality). But if you are happy without them, why bother?

gert posted:

Your dealer is not wrong. As long as your NAS is not accessible from the internet and as long you can trust all clients in your (w)lan, it is ok, to not update the system if it does what you want.

The behaviour of the NAS and e.g. Its media server can change with an update. In some versions the deep sleep standby of my DS213+ did not work anymore. Or the mediaserver lost the ability to transcode to wav and still play gaplessly.

On the other hand you will miss improvements (bugfixes, security patches, new functionality). But if you are happy without them, why bother?