DSM 7.1 Sudden Synology Drive Failure, All Clients

Currently reading
DSM 7.1 Sudden Synology Drive Failure, All Clients

13
3
NAS
DS218+, DS110j
Operating system
  1. Windows
  2. other
Mobile operating system
  1. Android
I have two clients, both laptops, and both suddenly quit connecting to the NAS via Drive Client at the same time (about 30 days ago). All I see on the client side is 'reconnecting' - but this is never successful. When I re-enter the passwork in the laptop Drive Client, I get 'invalid Quick Connect ID' (this is not true, can use QC from that same laptop at the time of the error msg) or 'Drive Server not enabled in QuickConnect settings'. Hmmm...looking at those settings, all possible connections for QC are enabled (mobile clients, DSM and filesharing) - but I don't see an option to select Drive specifically. Is that a problem? Also, both of my laptops are identified in Drive Client Manager as 'desktop' clients - but that's not right and I can't seem to change that. Proxy in the laptop Drive Client is 'autoidetect'. What's going on? Both worked perfectly up until 30 days ago. DId the DSM 7.1 update break something?
 
Because it's [V7.1] an RC release and not a full release you will need the [Drive Server] beta version which is 3.1.0-22885 and can be found in the beta section of the package centre in DSM.
Good luck!
 
Last edited:
Hmmm...just checked and the update was not to 7.1 but to 7.0.x. Does that change the advice? One more clue (?) .. both clients stopped communicating with the DS218+ at the same time - and this was immediately after the first data scrubbing. Just coincidence?
 
Yep. Maybe someone else can help then.
OK, thanks. A mystery b/c this approach has been working perfectly for 6+ months. To have both clients fail at the same time points to something related to the common item - the DS. I like your forum avatar - we have a son adopted from Ukraine...
 
OK, thanks. A mystery b/c this approach has been working perfectly for 6+ months. To have both clients fail at the same time points to something related to the common item - the DS. I like your forum avatar - we have a son adopted from Ukraine...
OK, an update. Went home and tried client #2. Consistent with the info on the DS from remote login, client #2 has not been able to sync with Synology Drive for about one month. Logging onto my DS, I had an update pending to 7.0.1-42218 Update 3. Did the update, DS rebooted and now client #2 is automagically back on line and in synch with my DS through Drive Client. Hoo-wah! I'll test Client #1 tomorrow...
 
And...Client #1 started the sync as soon as it powered up and got on the network. So, clearly something that resulted from a DSM update that was resolved by either the 2nd update or simply the reboot. The weird part are the error messages implying a missetting that blocked remote access. Not true, it seems.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

SOLVED It was, in face, the precious few 15 overlay slots allowed by Windows. I had installed something...
Replies
1
Views
527
1.) Python is the way: #%% import os from re import U, purge from dirsync import sync #%% #Task1...
Replies
1
Views
568
  • Solved
Finally found some info on this thread. So, to my understanding, it is impossible to use win/mac Drive...
Replies
1
Views
709
Thank you, that will help, but its almost there. Not all places I support use AD or even LDAP. I would...
Replies
2
Views
558
Sounds like you want the same as I do (local PC files & folders backed up on my NAS). I would start with...
Replies
2
Views
691
I too am able to sync many folders deep on my windows 11 machine to my DS220+ (ex F:\House\House Net\Pro...
Replies
2
Views
646

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top