Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network Drive not connecting after reboot of client machine #433

Open
guenhter opened this issue Jun 19, 2024 · 1 comment
Open

Network Drive not connecting after reboot of client machine #433

guenhter opened this issue Jun 19, 2024 · 1 comment

Comments

@guenhter
Copy link

guenhter commented Jun 19, 2024

Hi,

when the SFTP client machine is rebooted, the nework drive is still there in the Windows explorer, but it is not connected.
What I did

  • When mapping the network drive, I selected "reconnect on logon"
  • I also added the "Recovery" key on all sshfs* folders in the registry

Still, when booting up, the drive is disconnected until I make a double click on it.

I guess this is similar to #108

My environment is:

  • Windows 11 Home 23H2
  • Latest version of SSHFS-Win

to be more precise: When I startup my PC, in the Event Log I see an event like this:

launcher-x64: The service WinFsp.Launcher has been started.

When I then double click the disonnected network drive, and wait until it is connected, I see those messages:

launcher-x64: The service WinFsp.Launcher has been started.
launcher-x64: create sshfs\someuser@somehost = 0
sshfs: The service sshfs has been started.

@LostBeard
Copy link

My mounts are just disappearing. Good stuff. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants