Replies: 5 comments 12 replies
-
|
Hi @honear, |
Beta Was this translation helpful? Give feedback.
-
|
I never used NSSM but looks like there is a place to put the arguments like "/r \server\path /l m". |
Beta Was this translation helpful? Give feedback.
-
|
I connect my Buffalo NAS with the mirror command: |
Beta Was this translation helpful? Give feedback.
-
|
@honear I don't suppose you'd be able to share your config for this? I've been tearing my hair out over this all morning. For context: I have a network share which is mapped to B:\ via the Dokan mirror function, using the following syntax:
However, configuring this as a service to be automated at login through NSSM is proving to be a headache. I've created a few services now with some different syntax in the 'Arguments' field, but none of them are able to successfully map the share in the same way as when doing it manually via CMD as above. In the NSSM GUI, I've got the following fields: Application Path: The startup type is set to auto, log on account is set to 'Local System account' (I get log on errors when setting this to my own user or administrator accounts) NSSM then confirms a successful installation. But, when I then go to services.msc and manually click 'start' on the service created, it 'kind of' mounts B:\ , but it is just called 'Local Disk' and when trying to actually open B:\ there is a Windows error of "B:\ is not accessible. The filename, directory name, or volume label syntax is incorrect." Any advice on where I might be going wrong here would be highly appreciated - Ideally I really need to get these mounts automated on every login / reboot of the VM. |
Beta Was this translation helpful? Give feedback.
-
|
In addition to the above, for what it's worth, the same behaviour is experienced when pointing NSSM to a .bat file. This .bat file DOES successfully mount the share at B:\ when executed as usual and CMD is left open. However, when setting up this .bat file as a service in NSSM, the same behaviour happens of B:\ is kinda half mounted, but not actually accessible. (I have tested with other shares, as well - same results). |
Beta Was this translation helpful? Give feedback.
-
|
How To Using NSSM
GUI TimeApplication Tab
Details Tab
Process Tab
** DONE **
(You can now reboot to test it or start the service manually to test it ) |
Beta Was this translation helpful? Give feedback.
-
|
Note that if you want a Read-Write mirror, you can do this without a user-mode file system, NTFS provides this for free. You can create a symbolic link or junction point, and it's easy to do with tools like Link Shell Extension. NTFS's built-in features won't give you a read only mirror though. |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this? I was able to create service which starts at startup, but when i try to open the mounted disk, its not accessible. |
Beta Was this translation helpful? Give feedback.
-
|
I actually have custom project based on the mirror example. I use API calls to my server, which returns files/folder structure instead of mirror physical disk. Maybe there is some network access problem? I run the service with network service account, but that did not help. Windows event viewer shows no error after service startup |
Beta Was this translation helpful? Give feedback.
-
|
If the mounted file system shows up but is not accessible, I would suggest that you add some logging to your implementation and try to find out whether it fails in some way when files or directories are requested. It is quite common to get permission issues of various kinds when running as services compared to running as an interactive user. |
Beta Was this translation helpful? Give feedback.
-
I think it's a permissions/ login issue. I think it's trying to sign in as SYSTEM (as that's the user running the service on windows) and I'm not sure what password it's trying to use or how to set it. (Assuming you've followed @The009's instructions and used nssm.) EDIT: According to this thread #1203 there is no way to set a user/password combo when connecting to a share. So running as a service seems like kind of a bad idea with no other security implemented. Perhaps making a share that only allows SYSTEM to login from a specific IP would be a way to do something other than leaving it completely open. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for answers, i just created a .bat file and put it inside windows startup folder XD |
Beta Was this translation helpful? Give feedback.
-
^^ If you have set the Login information in Windows you can use shares that are NOT open to everyone, The problem with Windows is that you are limited to ONE single login for a network. So make sure whatever user you create has access to everything that PC needs access to, then set the credentials in Windows. Once the network services start (Hence the delayed start) the login information is then used by Windows to access that recourse. |
Beta Was this translation helpful? Give feedback.
-
It is still possible to run as a service, but you need to configure the service to run under a user account that is also present with the same password at the computer where the network resource is shared from. Running the service under SYSTEM account and accessing network shares is not at all a trivial task, though. |
Beta Was this translation helpful? Give feedback.
-
|
just on NMSS add use your local computer account to start the service .... say gabriel and that's it |
Beta Was this translation helpful? Give feedback.
-
Hi! Super new here, actually first 'discussion' on Github. I'm trying Dokan mirror and it's doing exactly what I needed, but when I close the command prompt, the drives also get unmounted. Is this the expected behavior? If so, what would I need to do in order to setup up something that mounts the drives on Login and they stay up without the command prompt window always there?
Thank you lots!
Beta Was this translation helpful? Give feedback.
All reactions