I never defined anything. I bought the unit about 8 years ago. Never used it apart from a quick trial at another house about 2 years ago (wasnt running long enough to notice any dropped connections). Then needed it this week so decided to set it up yesterday. Updated the DSM to latest when it lost connection. And then when it kept losing connection I did the hard reset. I assumed it was brand new when bought from amazon, still has factory seals on drive cover, ethernet and power cord all factory wrapped etc but i suppose someone could have tried it with a different power cord, ethernet cable etc. and altered the configuration? Installed WD Black drives that I bought brand new. Not a mark on the box or the 212. Absolutely factory perfect so still assume unused. Would the hard reset not wipe any user defined specs? Or can they be wiped as belt and braces?
Update time ... installed new battery (old one had some incredibly light crusting on join at back so was failed/failing). When powered up blue light flashed (I thought it was goosed). Then read syno instructions and suggested remove all drives and disconnect from network and power up before waiting 3 mins ... syno beeped (confirming motherboard healthy) and blue light went stable. Then powered down and installed one drive at a time (and repeated waiting for beep and stable blue light each time). All drives healthy and motherboard healthy. Connected to LAN and fins. syno cannot find anything now. Connected direct to W7 - set IP address and it pinged to that address but would still not open when entered IP 5000 address in browser. Blooming annoying. The time I (and we) have spent on this is mind boggling. How can healthy motherboard, healthy drives, stable blue light and flashing LAN and ethernet NOT allow any connection?
Thanks Coop .. same thing happens 192.168.1.6 cannot be reached (taking too long) etc
Hate to admit it but looks like I will. Shame ... I cannot understand how everything (sum of parts) can appear to work but as a whole they don't. Seems like something minor. Removing battery has now lost the IP (the one thing detectable by finds. syno so its gone worse but better in some respects because I know some parts are fine. Its a strange one
-- post merged: --
Are Synology normally reliable? I dont want to go through this again.
Can I throw in my two cents even though I'm a newbie also. Have you tried the simplest thing. Get a cat cable you know is good. connect it directly to pc and the nas, see if Synology assistant finds it. in other words, bypass any switch or anything between the nas and pc.
He's connected the NAS directly to his Win 7 PC and can ping the NAS....just can't access DSM via browser, and he's in a catch 22 because he did a reset and now can't set it back up again..IMO not a cable issue.
DHCP would possibly be an issue if both devices were connected to the router (I assume that your router is handling DHCP). But to my understanding you have disconnected both the NAS and PC from the router and connected them together directly. Please confirm.
It's bricked ... Flashing blue light this morning. Found two other posts (below) which suggest the DSM upgrade could have caused the initial issues (should have left it with the factory installed DSM - but who does that? If new firmware with bug fixes is available you use it right?) OR the factory hard reset caused it. Seems to be the bios is corrupted and without Linux skills and reflashing the chip and resoldering its a paperweight.
I thought I'd post this here for anyone looking for help on troubleshooting a failed Synology Diskstation NAS. I've been a happy user of a Synology DS-212+. The software is robust and much better than my old DroboFS, and the...