samba - Apr 2016 - mount cifs

On 04/19/2016 8:39 AM, lists wrote:
> Found some more info:
>
> mount.cifs to mount shares from my DCs (samba 4.2.11) works
> mount.cifs to mount shares from smbserver (also 4.2.11) does NOT work.
>
> Here is the debug log it produces:
>
>> root at epo:/proc/fs/cifs# mount.cifs //smbserver.domain.com/share /mnt
>> -o username=username,domain=WRKGRP,sec=ntlmsspi
>> Password:
>> Apr 19 15:19:58 epo kernel: [74522.479080] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/cifsfs.c: Devname: 
>> //smbserver.domain.com/share flags: 0
>> Apr 19 15:19:58 epo kernel: [74522.479098] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Domain name set
>> Apr 19 15:19:58 epo kernel: [74522.479103] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Username: username
>> Apr 19 15:19:58 epo kernel: [74522.479111] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: file mode: 0x1ed  
>> dir mode: 0x1ed
>> Apr 19 15:19:58 epo kernel: [74522.479229] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: CIFS VFS: in 
>> cifs_mount as Xid: 133 with uid: 0
>> Apr 19 15:19:58 epo kernel: [74522.479234] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: UNC: 
>> \\smbserver.domain.com\share ip: 1.2.3.4
>> Apr 19 15:19:58 epo kernel: [74522.479268] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Socket created
>> Apr 19 15:19:58 epo kernel: [74522.479272] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: sndbuf 16384 
>> rcvbuf 87380 rcvtimeo 0x6d6
>> Apr 19 15:19:58 epo kernel: [74522.479748] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/fscache.c: 
>> cifs_fscache_get_client_cookie: (0xffff88105ddb8000/0xffff88085cdf6c00)
>> Apr 19 15:19:58 epo kernel: [74522.479758] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: CIFS VFS: in 
>> cifs_get_smb_ses as Xid: 134 with uid: 0
>> Apr 19 15:19:58 epo kernel: [74522.479763] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Existing smb sess 
>> not found
>> Apr 19 15:19:58 epo kernel: [74522.479776] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/cifssmb.c: secFlags 0x1081
>> Apr 19 15:19:58 epo kernel: [74522.479780] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/cifssmb.c: NTLMSSP only 
>> mechanism, enable extended security
>> Apr 19 15:19:58 epo kernel: [74522.479788] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Demultiplex PID: 
>> 13704
>> Apr 19 15:19:58 epo kernel: [74522.479798] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/transport.c: For smb_command 
>> 114
>> Apr 19 15:19:58 epo kernel: [74522.479809] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/transport.c: Sending smb:  
>> total_len 82
>> Apr 19 15:19:58 epo kernel: [74522.491173] 
>> /build/linux-4wkEzn/linux-3.2.68/fs/cifs/connect.c: Received no data 
>> or error: expecting 4 got 0
>> mount error(112): Host is down
>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>> root at epo:/proc/fs/cifs#
>
> And even though mount.cifs complains and refuses to mount stuff, the 
> smbserver ACTUALLY works fine, all windows clients map their drives to 
> it, I can also browse it with smbclient. It's just mount.cifs that 
> complains.
>
> As for smb.conf options: similar on the DCs and the smbserver, with:
>
> server signing = mandatory
> ntlm auth = yes
> server min protocol = SMB2
> client max protocol = SMB3
>
> Any ideas why mount.cifs doesn't connect to our smbserver?
>
> MJ
I echo MJ's request, what is now needed to mount a CIFS share? Using 
krb5 was mentioned, but what about standalone servers that don't use 
kerberos?

Dale

Hallo, Dale,

Du meintest am 19.04.16:
>> Found some more info:
>>
>> mount.cifs to mount shares from my DCs (samba 4.2.11) works
>> mount.cifs to mount shares from smbserver (also 4.2.11) does NOT
>> work.
[...]
>> As for smb.conf options: similar on the DCs and the smbserver, with:
>>
>> server signing = mandatory
>> ntlm auth = yes
>> server min protocol = SMB2
>> client max protocol = SMB3
>>
>> Any ideas why mount.cifs doesn't connect to our smbserver?
> I echo MJ's request, what is now needed to mount a CIFS share? Using
> krb5 was mentioned, but what about standalone servers that don't use
> kerberos?
Again: try (the default)

        max protocol = NT1

instead of the above options.

Viele Gruesse!
Helmut

Hi Helmut,

On 04/19/2016 08:44 PM, Helmut Hullen wrote:
> Again: try (the default)
>
>          max protocol = NT1
>
> instead of the above options.
If I understand things correctly, this would set my samba server to use 
NT1 as the MAX protocol, no SMB2 or SMB3 anymore?

Or do I misunderstand something?

On 04/19/2016 1:44 PM, Helmut Hullen wrote:
> Hallo, Dale,
>
> Du meintest am 19.04.16:
>
>>> Found some more info:
>>>
>>> mount.cifs to mount shares from my DCs (samba 4.2.11) works
>>> mount.cifs to mount shares from smbserver (also 4.2.11) does NOT
>>> work.
> [...]
>
>>> As for smb.conf options: similar on the DCs and the smbserver,
with:
>>>
>>> server signing = mandatory
>>> ntlm auth = yes
>>> server min protocol = SMB2
>>> client max protocol = SMB3
>>>
>>> Any ideas why mount.cifs doesn't connect to our smbserver?
>
>> I echo MJ's request, what is now needed to mount a CIFS share?
Using
>> krb5 was mentioned, but what about standalone servers that don't
use
>> kerberos?
> Again: try (the default)
>
>          max protocol = NT1
>
> instead of the above options.
>
> Viele Gruesse!
> Helmut
Helmut,

I added that parameter to smb.conf, then ran this:

mount -t cifs //path/to/share /path/to/mount_point -o 
sec=ntlmv2,credentials=/path/to/credentials_file

and got this:

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

It seems that something more is needed.

Thanks,
Dale