Cannot Open or Save database on a Network Share
A lightweight and easy-to-use password manager
Brought to you by:
dreichl
Menu
▾
▴
#1686 Cannot Open or Save database on a Network Share
Greetings,
I am unable to save my KeepPass database on a Network Share on one of my Windows 10 systems. When I select "File > Save" all it provides is access to my local C:\ and D:\ Drive.
If I manually copy the database to a Network Share, and try to launch it, it says it cannot find the file.
When I go to another Windows 10 system, it allows me to open/save to a Network Share.
What am I missing here?
If the network share is available as a Windows drive or share then KeePass can use it.
You most likely have some Windows issue that makes the share unavailable.
cheers, Paul
One would imagine that is the case; be it works on another system, but my question is what? This is the only application that is unable to see Network Shares; thus it is not a global situation. This is specific to the use of this application.
But it's OK on another PC, so it's not KeePass as such.
Have you run KeePass with different credentials to the one that can access the share?
cheers, Paul
As you can see in the screen shot, its multiple shares that is possible and it sees none. I can see if it was specific to one particular share or one particular user, but i log into another network system; with the same domain credentials and same shared drives and can access it. That eliminates it being a user or network rights issue; as the same thing would have traveled with me accordingly.
I can however, log in with different credentials on the same system (with the issue) to rule out system over policy.
Doesn't make a difference who I log in with. On this Windows 10 System (even with a defaulted group policy reset), it does not allow/show Network Shares. I log into my Windows 7 system with the same credentials and has the same GPO policy as it does on my Windows 10 system (had 2.35 installed, and it shows Network Shares, upgraded to 2.37 and still shows Network Shares). Does not show shares on Windows 10 (enterprise 64bit)
Last edit: Tony 2017-11-20
The difference is that apparently the Win7 PC is set up to mount the shares as virtual drives (G:, H:, J:, L:, etc.) and the Win10 PC isn't. On the Win10 machine, try clicking on "Network" at bottom left and see what you get. If you can navigate to the shares from there, you can either right-click on them and select "Map Network Drive...", or switch to referring to the files by their real network names ("\\SERVER\SHARED DATA\Personal\Cred\OGX.kdbx", etc.) instead of the virtual names ("X:\Personal\Cred\OGX.kdbx").
And BTW, this section of the forum is really intended for bugs in the KeePass program, which this is not. For future reference, you really should have posted this in the Help discussion section.
Last edit: T. Bug Reporter 2017-11-20
Hmm, good call. I was able to get to it via '\server\folderpath\'... but I then remoted to my home domain environment which also runs Windows 10 and it sees the virtual drives identical as my work Windows 7. They both are mapped via Active Directory GPO "Drive Maps" configuration; so what is different here?
This is strange.
Last edit: Tony 2017-11-20
Can't help you much there, because I don't use AD. Are you sure both domains are configured to map the same share(s) to the same drive letter(s)? If one claims your file is on H:, but the other calls the same share E:, it won't work. This is why I don't map drives at all anymore; it's just less error-prone to let every machine access FileX.kdbx at \\MYREPOSITORY\MYSTUFF\FileX.kdbx. (It does mean I have to be a little more careful about path lengths, tho.)
i'm confident both drives i am seeking to store my dba is on my G:\ Drive, which is typically a networks "home" volume. it doesnt see anything past E:\ on this system - which my network shares start at G:.
but, at least i am up and running with "\servername\folderpath\" for the time being. That is better than nothing. all my other apps, acrobat, office, browsers, ftp, winscp, etc can see these drives no problem when i do file > open... its just keepass with the issue. :(
This issue is not just affecting KeePass.
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_files/network-mapped-drives-not-available-on-windows-10/ef955b4b-1103-42db-a00d-cd1520a8e178?auth=1
There is a registry hack, that seems to fix it for some, towards the bottom of the first page.
cheers, Paul
Paul,
That indeed resolved my issue. It appears UAC was the cause of this and that cleared it up.
Yay!