Hi, and sorry for my english
I'm trying Syncback pro and i try to make it work with cryptomator, that i use to crypt files on the cloud.
Cryptomator create a network drive like Z: if you want, related to my cloud storage: MEGA in my case, but it's the same with others
When i try to create a new profile in syncback and want to select this network drive as destination, it doesn't show up in the list, so i can't use it
I tried in administrator mode, same issue.
Do you know what i can do ?
Thanx for you help
Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
- If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
SyncBack don't see my network drive
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: SyncBack don't see my network drive
Hi, see this KB article
The quickest solution is probably the registry tweak. IIRC no-one has reported any problems when trying it since Vista launched...
The quickest solution is probably the registry tweak. IIRC no-one has reported any problems when trying it since Vista launched...
-
eldaria
- Newbie
- Posts: 3
- Joined: Thu Dec 21, 2017 7:56 am
Re: SyncBack don't see my network drive
Hi, and thanx for your response
I noticed that i have already the "enableLinkedConnections" to 1 in the registry, so it don't work for me :/
I'll look on the others solutions, but that strange
I noticed that i have already the "enableLinkedConnections" to 1 in the registry, so it don't work for me :/
I'll look on the others solutions, but that strange
-
eldaria
- Newbie
- Posts: 3
- Joined: Thu Dec 21, 2017 7:56 am
Re: SyncBack don't see my network drive
and i don't really understand what i need to do about the unc path.. not in my language ^^
-
cliffhanger
- Expert
- Posts: 606
- Joined: Tue May 31, 2011 5:59 pm
Re: SyncBack don't see my network drive
[note: my previous comment about 'no problems' from trying the registry tweak was meant to refer to 'absence of unwanted side effects'; it was not a guarantee the tweak would work]
The fact the registry tweak does not help suggests the method your cloud software uses to spoof a drive letter mapping does not involve mapping to a standard UNC path. This kinda makes sense if you consider that your cloud resource is not only 'on the other side' (from your PC's point of view) of a network adapter, it is also on the other side of a modem (DSL/cable/fibre). So it is highly likely that you cannot 'use the UNC equivalent of the mapping' anyway (because there actually isn't such a direct UNC equivalent).
One other trick you could try is to install a copy of SyncBackFree (make sure you install it to the default path: do not try to install to the same path as the Pro version). You may find that a profile in Free can see your mapped drive letter, in which case creating a non-elevated copy of Pro will probably also work, subject to the loss of elevated functions mentioned in the KB. Or, if it will otherwise suit your needs, keep using the Free version for this particular job.
If none of the above works, I can only guess the spoofing (mapping) used is somehow dedicated to the Explorer code, and won't work if you try to point other software at the 'drive'.
The fact the registry tweak does not help suggests the method your cloud software uses to spoof a drive letter mapping does not involve mapping to a standard UNC path. This kinda makes sense if you consider that your cloud resource is not only 'on the other side' (from your PC's point of view) of a network adapter, it is also on the other side of a modem (DSL/cable/fibre). So it is highly likely that you cannot 'use the UNC equivalent of the mapping' anyway (because there actually isn't such a direct UNC equivalent).
One other trick you could try is to install a copy of SyncBackFree (make sure you install it to the default path: do not try to install to the same path as the Pro version). You may find that a profile in Free can see your mapped drive letter, in which case creating a non-elevated copy of Pro will probably also work, subject to the loss of elevated functions mentioned in the KB. Or, if it will otherwise suit your needs, keep using the Free version for this particular job.
If none of the above works, I can only guess the spoofing (mapping) used is somehow dedicated to the Explorer code, and won't work if you try to point other software at the 'drive'.