Potential Fixes for "Network Name cannot be found" with sshfs.k

[CaptainXLAB]

Not a problem/issue, but findings on how I resolved my own issues when trying to connect to a sever with sshfs.kr.

For any Windows versions that have OpenSSH included, make sure you use the latest pre-release!

• OpenSSH included with Windows is seemingly not compatible with SSHS-Win

If \\sshfs.kr and \\sshfs.k\ don't work, try connecting with \\sshfs\ first and see if it prompts for a password (connection test)

When using \\sshfs.k with one key file

• Try connecting with ssh first, without sshfs. Look for any warnings, connection failure(s), etc.
• Make sure you have the correct permissions set on %userprofile%\.ssh\id_rsa. Any warning(s) will show up when trying to connect with plain ssh.
• Only these 3 users are required in permissions:
  • administrators
  • Your current user
  • SYSTEM
• Ensure Winfsp.Launcher service is running using services.msc, start if it has stopped

For \\sshfs.k with different key files based on domain

• Open C:\Program Files\SSHFS-Win\etc\ssh_config file
• Add entries to that file based on this pattern below:

Host pixel.phone
    User root
    IdentityFile C:\Users\User\.ssh\id_rsa_pixel_root
    userknownhostsfile C:\Users\User\.ssh\known_hosts

Host 100.123.45.67
    User test
    IdentityFile C:\Users\User\.ssh\testserver_key
    userknownhostsfile C:\Users\User\.ssh\known_hosts

I had to do all this to make sshfs.kr work with Windows 11 connecting with sshfs.kr

• Fix bad permissions on key file
• Add entry to ssh_config file
• Install latest pre-release version

Hope this helps if you're stuck seeing Network name cannot be found when using sshfs.kr