Displaying 7 results from an estimated 7 matches for "smb2_get_dfs_ref".
Did you mean:
smb2_get_dfs_refer
2017 Oct 13
5
Share mounts in SMBv1 mode, but fails weirdly in SMBv2 mode
...\nfsserv22\expsi,vers=2.0,user=grasland,,domain=LAL,pass=********
>> mount error(95): Operation not supported
>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>> hadrien at linux-2ak3:~> dmesg | tail
>> [...]
>> [13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
>> [13424.789504] CIFS VFS: cifs_read_super: get root inode failed
>>
>> Replacing "vers=2.0" with "vers=1.0" in the mount command line makes
>> this work, so I'm quite confident that my general configuration is
>> correct and the proble...
2017 Oct 13
0
Share mounts in SMBv1 mode, but fails weirdly in SMBv2 mode
This might be a kernel thing. 4.13.5-1 .. ? Archlinux?
There where recently e-mail about this on technical.
So maybe its not implemented parts in samba or mount commands (yet)
And i point to this : smb2_get_dfs_refer
> > >> [13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
> > >> [13424.789504] CIFS VFS: cifs_read_super: get root inode failed
To give an idea..
https://kernel.opensuse.org/cgit/kernel-source/diff/patches.fixes/0001-CIFS-implement-get_dfs_refer-for-SMB2...
2017 Oct 13
2
Share mounts in SMBv1 mode, but fails weirdly in SMBv2 mode
...ork, as long as rolling
> back a broken system was easy.
>
>
> > There where recently e-mail about this on technical.
> > So maybe its not implemented parts in samba or mount commands (yet)
> I would welcome any clarification on this.
>
> > And i point to this : smb2_get_dfs_refer
> >>>>> [13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
> >>>>> [13424.789504] CIFS VFS: cifs_read_super: get root inode failed
> >
> > To give an idea..
> >
> https://kernel.opensuse.org/cgit/kernel-source/diff/patches...
2020 Sep 06
2
pam_mount in 'newer samba'...
...d servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Sep 5 12:38:11 pc1labinf17 kernel: [ 322.015963] CIFS VFS: BAD_NETWORK_NAME: \\fileserver.ad.domain.test\Users
Sep 5 12:38:11 pc1labinf17 kernel: [ 322.016188] CIFS VFS: \\fileserver.ad.domain.test\IPC$ ioctl error in smb2_get_dfs_refer rc=-22
Sep 5 12:38:11 pc1labinf17 kernel: [ 322.016522] CIFS VFS: cifs_mount failed w/return code = -2
clearly i've tried some vers= and sec= combination, with no clue.
If i use pam_mkhome (eg, i create the home instead of mountin it)
clearly i can login (so PAM, NSS/Winbind and kerbero...
2017 Oct 12
2
Share mounts in SMBv1 mode, but fails weirdly in SMBv2 mode
...ernel mount options:
ip=134.158.91.155,unc=\\nfsserv22\expsi,vers=2.0,user=grasland,,domain=LAL,pass=********
mount error(95): Operation not supported
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
hadrien at linux-2ak3:~> dmesg | tail
[...]
[13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
[13424.789504] CIFS VFS: cifs_read_super: get root inode failed
Replacing "vers=2.0" with "vers=1.0" in the mount command line makes
this work, so I'm quite confident that my general configuration is
correct and the problem is somehow specific to the SMBv2 protoco...
2020 Sep 07
0
pam_mount in 'newer samba'...
Hai Marco,
Is the UPN set for this server. CIFS/hostnam.fqdn ?
Does its A and PTR match with the "real" hostname?
But i see : smb2_get_dfs_refer rc
Not commenting on this expect... upgrade the servers.. ;-)
Try :
apt install keyutils this might be missing and is needed for CIFS kerberos mounts
mount -t cifs -o user=USER,domain=DOMAIN,cruid=USER,sec=krb5,vers=3.0 //hostname.FQDN/share /mnt/tmp
mount -t cifs -o user=USER,domain=DOMAI...
2017 Oct 12
0
Share mounts in SMBv1 mode, but fails weirdly in SMBv2 mode
...134.158.91.155,unc=\\nfsserv22\expsi,vers=2.0,user=grasland,,domain=LAL,pass=********
> mount error(95): Operation not supported
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
> hadrien at linux-2ak3:~> dmesg | tail
> [...]
> [13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2
> [13424.789504] CIFS VFS: cifs_read_super: get root inode failed
>
> Replacing "vers=2.0" with "vers=1.0" in the mount command line makes
> this work, so I'm quite confident that my general configuration is
> correct and the problem is somehow specif...