search

kofemann / ms-nfs41-client

NFSv4.1/pNFS client for Windows 7 developed by CITI, UMICH.
GNU Lesser General Public License v3.0
90 stars 35 forks source link

MS NFS 41 Client failed with error code 3 #2

Open MySepultura opened 9 years ago

MySepultura commented 9 years ago

Dear Community,

I have a question because the NFS Client is failing with error code 3. System can't find path.

NekoDrive NFS Client Test Component is finding the the drive.

I typed: nfsd.exe -d 3 -noldap uid 1000 gid 100

then I typed nfs_mount z: 192.168.0.182:\home\winclient

Here the programm is failing.

Can anyone help me?

kofemann commented 9 years ago

Hi, do you started command window as admin?

MySepultura commented 9 years ago

yes. NFSD is active

kofemann commented 9 years ago

and it's --uid 1000 --gid 1000 and --noldap right?

MySepultura commented 9 years ago

yes I used nfs_mount.exe -d 3 -noldap --uid 1000 --gid 100.

NekoDrive can connect with UID 1000 and GID 100 Read+Write Access.

MySepultura commented 9 years ago

I have fixed this Problem!

kofemann commented 9 years ago

Great! Is there ang information missing in the readme to get it running ?

MySepultura commented 9 years ago

yes you must set on System > Computer Name > Change > more > Primary DNS Prefix or NFSD will fail to load.

And it seems you must add "insecure" to Linux NFS Server.

vision-ken commented 6 years ago

@MySepultura what's need to set to Primary DNS Prefix?

Converter-App commented 3 years ago

I ran into the same issue and spent hours fixing it. The solution was, that the NFS daemon (nfsd.exe) file was corrupted, therefore the service did not start properly at the system startup as it used to. Fixing all file system errors and reinstalling the daemon solved it for me.