Hello,
First let me say this question is not a Dopus issue. But because you guys are the experts in file/directory systems I was hoping something off the "top of your head" might help me. If I get no response I will understand. So you know, I've spent hours scouring forums etc looking for the answer. The Backup software author is not able to help me either.
My issue; I have a Synology NAS. When it first powers up (in this case wake on lan) the backup software is not able to access the files on the NAS (I have a very long delay so I know it is not the NAS power up routing).
Then, after I access the target NAS folder with Dopus, the backup software will be able to access the backup folder.
Any suggestions will be very much appreciated. And again I know this is considered "off topic ish".
Best Regards,
Thank you for you reply. It suggested a test I performed. I found that If I "touched" the path with notepad (windows version) and simply read the directory it made a difference.
Backup software - Initiated a successful WOL command but when trying to access the NAS folder received error "12:11:17 PM !E Destination drive Y: is inaccessible"
Reran Backup software - Initiated a successful WOL command but when trying to access the NAS folder received error "12:11:17 PM !E Destination drive Y: is inaccessible"
Windows notepad - read the directory (using the open command) of the NAS folder Y.
wowbagger asked / suggested "Do you use the same username and password on the synology as the logged on windows user?"
Hi wowbagger, Thanks for reading and your suggestion.
Yes/no. The NAS uses the same name, but with a different password. Reason is that I don't have a password on my main computer. It is used solely by me and if someone broke into our house, the computer would be gone and password would not be a deterrent.
However, with notepad being able to read correctly and somehow changing the state of the NAS directory, it would not indicate name/password were my issue.
What happens if you change your "not-existent" password to be the same as used on the NAS for the same user?
Just for a test..
But if you don't want take the risk of loosing your password/data to thieves, any automatic connection to the NAS with locally stored credentials should be avoided. What about creating a dedicated user on the NAS and whenever you launch the backup tool, connect to that share or what it is by manually creating the connection first?
Or connect to the sensitive locations manually at the time your computer starts up, that's what I do, to get around storing/reusing existing account/password information on the system.
I don't know if you will actually see this, I hope you do.
Thank you for the lead that finally allowed me to solve the solution. I used wireshark and notepad to analyze network traffic (I'm still not sure what all the packets do but after a while I kinda got a sense of them.
It appears Windows 7 holds user credentials for different (each?) login action. So when I mapped the NAS the appropriate login name and password were used.
The problem was that I was using the mapped drive letter to refer to locations on the NAS. This apparently is not recognized by the NAS. Once I switched to the network name all was good. i.e. \\MyDiskstation<directory><subdirectory>
So thanks again for reading my issue and helping me on the right road.
I see this! Glad you were able to work this out! o)
Do you know? You can manage the credentials stored. By running "rundll32.exe keymgr.dll, KRShowKeyMgr" e.g., or by opening your account settings and finding the correct credential manager there. Maybe that's also helpful the next time.
Btw, respect for "mastering" Wireshark, I did not really get behind it, trying to research network related things! o))