Windows NFS and Kerberos #3
Comments
|
I also have this Q as KRB5 is rather important to link with NFS |
gisburn
added a commit
to gisburn/ms-nfs41-client-kofemannvacation
that referenced
this issue
Jan 18, 2025
Fix DrMemory hit in |nfs41_setattr()|: ---- snip ---- Error kofemann#3: UNINITIALIZED READ: reading 4 byte(s) 0 nfs41_setattr [daemon\nfs41_ops.c:1514] 1 handle_setacl [daemon\acl.c:1468] 2 upcall_handle [daemon\upcall.c:220] 3 nfsd_worker_thread_main [daemon\nfs41_daemon.c:207] 4 nfsd_thread_main [daemon\nfs41_daemon.c:245] ---- snip ---- Signed-off-by: Cedric Blancher <[email protected]>
kofemann
pushed a commit
that referenced
this issue
Jan 27, 2025
Fix DrMemory hit in |nfs41_setattr()|: ---- snip ---- Error #3: UNINITIALIZED READ: reading 4 byte(s) 0 nfs41_setattr [daemon\nfs41_ops.c:1514] 1 handle_setacl [daemon\acl.c:1468] 2 upcall_handle [daemon\upcall.c:220] 3 nfsd_worker_thread_main [daemon\nfs41_daemon.c:207] 4 nfsd_thread_main [daemon\nfs41_daemon.c:245] ---- snip ---- Signed-off-by: Cedric Blancher <[email protected]> Signed-off-by: Tigran Mkrtchyan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hallo,
how can I use Kerberos connection with the NFS Client?
I have tried to mount with:
nfs_mount.exe -p -o sec=krb5i z: 192.168.0.182:\home\winclient
but it tells me:
The Network address is unreachable. Error Code 1231. The PING is working. If I switch Kerberos off (at server) and mount it without kerberos, it will wok
The text was updated successfully, but these errors were encountered: