unable to connect to drive error 67

Open
#280 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux
Domain
cli, networking, tooling

Research direction

Begin by reproducing the reported net use command against 10.66.124.129 and comparing it with the three working servers; also compare the working sshfs-win.exe svc invocation. The issue names no repository file or test, so completion would require identifying the server-specific cause of system error 67 and documenting a verified workaround for automatic login mounting.

Written by the indexing model from the issue text.

Description

Hi @billziss-gh,

I'm currently using the SSHFS to mount my linux drives to my windows server. I have issues connecting to one of my linux servers and the error 67 keeps coming out I was able to mount my other drives from 3 different linux servers. Have no clue as to why I'm unable to connect to this particular server.

I'm running a batch file to connect this drives automatically after user logs in and below is the command I'm currently running which works for my other 3 servers but doesn't for this 1 particular server.

net use U: \sshfs\emsusr@10.66.124.129....\opt\IBM\WebSphere\AppServer\profiles /user:emsusr abcd /persistent:Yes

I have tried using sshfs-win.exe svc \sshfs.k\emsusr@10.66.124.129 K: "emsusr" "-oIdentityFile=c:/Keys/id_rsa.txt" and this works. But somehow a net use command to mount the drives is giving me a system error 67 for only 1 server and works for the remaining 3 servers.

The intention of using net use is to create a batch file that will execute automatically upon logging in for all users.
Any workaround on this?

Any help is greatly appreciated.

Dominant language
C
Stars
6.4k
Forks
315
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from winfsp/sshfs-win

All issues in winfsp/sshfs-win

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.