62 replies to this topic

[WanWizard]

I doubt that. There must be something different for you than for everyone else.

 

Did you do the checks I asked in post #34?

[mackguil]

@ Wanwizard: can you try to connect at root, please ?

[mackguil]

I doubt that. There must be something different for you than for everyone else.

 

Did you do the checks I asked in post #34?

Yes i change password with 123456789 to test,  workgroup is the same

 

I try with username=WORKGROUPNAME/root  but not work,

 

root@setopbox:~# /etc/init.d/samba.sh restart
Stopping Samba: smbd nmbd.
Waiting for samba processes to die off...
Starting Samba: smbd nmbd.
 

All work fine

 

logs:

 cat /var/log/log.smbd
[2018/04/13 16:45:52.888289,  3] ../lib/util/util_net.c:256(interpret_string_addr_internal)
  interpret_string_addr_internal: getaddrinfo failed for name vuduo2 (flags 34) [Name or service not known]
[2018/04/13 16:45:52.888429,  3] ../source3/lib/util_sock.c:1187(get_mydnsfullname)
  get_mydnsfullname: getaddrinfo failed for name vuduo2 [Unknown error]
[2018/04/13 16:45:52.892151,  3] ../lib/util/util_net.c:256(interpret_string_addr_internal)
  interpret_string_addr_internal: getaddrinfo failed for name vuduo2 (flags 34) [Name or service not known]
[2018/04/13 16:45:52.892270,  3] ../source3/lib/util_sock.c:1187(get_mydnsfullname)
  get_mydnsfullname: getaddrinfo failed for name vuduo2 [Unknown error]
[2018/04/13 16:45:52.892761,  3] ../auth/ntlmssp/ntlmssp_util.c:69(debug_ntlmssp_flags)
  Got NTLMSSP neg_flags=0xe0080225
[2018/04/13 16:45:52.895359,  3] ../auth/ntlmssp/ntlmssp_server.c:452(ntlmssp_server_preauth)
  Got user=[WORKGROUP/root] domain=[] workstation=[] len1=0 len2=104
[2018/04/13 16:45:52.895546,  3] ../source3/param/loadparm.c:3742(lp_load_ex)
  lp_load_ex: refreshing parameters
[2018/04/13 16:45:52.895834,  3] ../source3/param/loadparm.c:544(init_globals)
  Initialising global parameters
[2018/04/13 16:45:52.897137,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[root]"
[2018/04/13 16:45:52.897549,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[Media]"
[2018/04/13 16:45:52.898192,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[Harddisk]"
[2018/04/13 16:45:52.898854,  3] ../source3/param/loadparm.c:1588(lp_add_ipc)
  adding IPC service
[2018/04/13 16:45:52.898966,  3] ../source3/auth/auth.c:178(auth_check_ntlm_password)
  check_ntlm_password:  Checking password for unmapped user []\[WORKGROUP/root]@[] with the new password interface
[2018/04/13 16:45:52.899029,  3] ../source3/auth/auth.c:181(auth_check_ntlm_password)
  check_ntlm_password:  mapped user is: [VUDUO2]\[WORKGROUP/root]@[]
[2018/04/13 16:45:52.899176,  3] ../source3/auth/check_samsec.c:400(check_sam_security)
  check_sam_security: Couldn't find user 'WORKGROUP/root' in passdb.
[2018/04/13 16:45:52.899245,  2] ../source3/auth/auth.c:315(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [WORKGROUP/root] -> [WORKGROUP/root] FAILED with error NT_STATUS_NO_SUCH_USER
[2018/04/13 16:45:52.899302,  3] ../source3/auth/auth_util.c:1602(do_map_to_guest_server_info)
  No such user WORKGROUP/root [] - using guest account
[2018/04/13 16:45:52.901217,  3] ../source3/lib/access.c:338(allow_access)
  Allowed connection from 192.168.1.8 (192.168.1.8)
[2018/04/13 16:45:52.901473,  3] ../source3/smbd/service.c:622(make_connection_snum)
  Connect path is '/tmp' for service [IPC$]
[2018/04/13 16:45:52.901653,  3] ../source3/smbd/vfs.c:113(vfs_init_default)
  Initialising default vfs hooks
[2018/04/13 16:45:52.901755,  3] ../source3/smbd/vfs.c:139(vfs_init_custom)
  Initialising custom vfs hooks from [/[Default VFS]/]
[2018/04/13 16:45:52.902163,  3] ../source3/smbd/service.c:872(make_connection_snum)
   (ipv4:192.168.1.8:39286) connect to service IPC$ initially as user root (uid=0, gid=0) (pid 3444)
[2018/04/13 16:45:52.904403,  3] ../source3/lib/access.c:338(allow_access)
  Allowed connection from 192.168.1.8 (192.168.1.8)
[2018/04/13 16:45:52.904520,  2] ../source3/smbd/service.c:416(create_connection_session_info)
  guest user (from session setup) not permitted to access this share (root)
[2018/04/13 16:45:52.904631,  1] ../source3/smbd/service.c:560(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2018/04/13 16:45:52.904781,  3] ../source3/smbd/smb2_server.c:3098(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_ACCESS_DENIED] || at ../source3/smbd/smb2_tcon.c:135
[2018/04/13 16:45:52.906107,  3] ../source3/smbd/service.c:1148(close_cnum)
   (ipv4:192.168.1.8:39286) closed connection to service IPC$

and log.nmbd

 cat /var/log/log.nmbd
[2018/04/13 16:39:16.943369,  3] ../source3/nmbd/nmbd_become_lmb.c:540(become_local_master_browser)
  become_local_master_browser: first stage - attempt to register ^1^2__MSBROWSE__^2^1
[2018/04/13 16:39:16.949356,  3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
  write_browse_list: Wrote browse list into file /var/lib/samba/browse.dat
[2018/04/13 16:39:20.954569,  3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
  add_name_to_subnet: Added netbios name __MSBROWSE__<01> with first IP 192.168.1.103 ttl=0 nb_flags=80 to subnet 192.168.1.103
[2018/04/13 16:39:20.954748,  3] ../source3/nmbd/nmbd_become_lmb.c:453(become_local_master_stage1)
  become_local_master_stage1: go to stage 2: register the WORKGROUP<1d> name.
[2018/04/13 16:39:20.954818,  3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
  add_name_to_subnet: Added netbios name __MSBROWSE__<01> with first IP 192.168.1.103 ttl=0 nb_flags=80 to subnet UNICAST_SUBNET
[2018/04/13 16:39:24.960109,  3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
  add_name_to_subnet: Added netbios name WORKGROUP<1d> with first IP 192.168.1.103 ttl=0 nb_flags= 0 to subnet 192.168.1.103
[2018/04/13 16:39:24.960247,  3] ../source3/nmbd/nmbd_become_lmb.c:354(become_local_master_stage2)
  become_local_master_stage2: registered as master browser for workgroup WORKGROUP on subnet 192.168.1.103
[2018/04/13 16:39:24.960300,  3] ../source3/nmbd/nmbd_sendannounce.c:70(broadcast_announce_request)
  broadcast_announce_request: sending announce request for workgroup WORKGROUP to subnet 192.168.1.103
[2018/04/13 16:39:24.960448,  3] ../source3/nmbd/nmbd_namelistdb.c:263(add_name_to_subnet)
  add_name_to_subnet: Added netbios name WORKGROUP<1d> with first IP 192.168.1.103 ttl=0 nb_flags= 0 to subnet UNICAST_SUBNET
[2018/04/13 16:39:24.960534,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****

  Samba name server VUDUO2 is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.103

  *****
[2018/04/13 16:39:24.960776,  3] ../source3/nmbd/nmbd_sendannounce.c:170(send_local_master_announcement)
  send_local_master_announcement: type 849a03 for name VUDUO2 on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:39:24.960944,  3] ../source3/nmbd/nmbd_sendannounce.c:189(send_workgroup_announcement)
  send_workgroup_announcement: on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:39:24.961301,  3] ../source3/nmbd/nmbd_incomingdgrams.c:118(process_host_announce)
  process_host_announce: from MACK-18<00> IP 192.168.1.8 to WORKGROUP<1d> for server MACK-18.
[2018/04/13 16:39:24.961429,  3] ../source3/nmbd/nmbd_serverlistdb.c:134(create_server_on_workgroup)
  create_server_on_workgroup: Created server entry MACK-18 of type 40819a03 (mack-18 server (Samba, Ubuntu)) on workgroup WORKGROUP.
[2018/04/13 16:39:24.971927,  3] ../source3/nmbd/nmbd_incomingdgrams.c:118(process_host_announce)
  process_host_announce: from MACK-PC<00> IP 192.168.1.4 to WORKGROUP<1d> for server MACK-PC.
[2018/04/13 16:39:24.972073,  3] ../source3/nmbd/nmbd_serverlistdb.c:134(create_server_on_workgroup)
  create_server_on_workgroup: Created server entry MACK-PC of type 40011003 () on workgroup WORKGROUP.
[2018/04/13 16:39:44.997005,  3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
  write_browse_list: Wrote browse list into file /var/lib/samba/browse.dat
[2018/04/13 16:39:51.102241,  3] ../source3/nmbd/nmbd_incomingdgrams.c:118(process_host_announce)
  process_host_announce: from SSD-PC<00> IP 192.168.1.2 to WORKGROUP<1d> for server SSD-PC.
[2018/04/13 16:39:51.102383,  3] ../source3/nmbd/nmbd_serverlistdb.c:134(create_server_on_workgroup)
  create_server_on_workgroup: Created server entry SSD-PC of type 40011003 () on workgroup WORKGROUP.
[2018/04/13 16:39:51.107417,  3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
  write_browse_list: Wrote browse list into file /var/lib/samba/browse.dat
[2018/04/13 16:41:41.199873,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.1.8 on subnet 192.168.1.103 for name WORKGROUP<1d>
[2018/04/13 16:41:41.200026,  3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request)
  OK
[2018/04/13 16:41:41.200158,  3] ../source3/nmbd/nmbd_sendannounce.c:170(send_local_master_announcement)
  send_local_master_announcement: type 849a03 for name VUDUO2 on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:41:41.200299,  3] ../source3/nmbd/nmbd_sendannounce.c:189(send_workgroup_announcement)
  send_workgroup_announcement: on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:43:40.530643,  3] ../source3/nmbd/nmbd_incomingdgrams.c:118(process_host_announce)
  process_host_announce: from MACK-18<00> IP 192.168.1.8 to WORKGROUP<1d> for server MACK-18.
[2018/04/13 16:43:40.535504,  3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
  write_browse_list: Wrote browse list into file /var/lib/samba/browse.dat
[2018/04/13 16:44:50.605682,  3] ../source3/nmbd/nmbd_sendannounce.c:170(send_local_master_announcement)
  send_local_master_announcement: type 849a03 for name VUDUO2 on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:44:50.605923,  3] ../source3/nmbd/nmbd_sendannounce.c:189(send_workgroup_announcement)
  send_workgroup_announcement: on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:46:40.698424,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.1.8 on subnet 192.168.1.103 for name WORKGROUP<1d>
[2018/04/13 16:46:40.698562,  3] ../source3/nmbd/nmbd_incomingrequests.c:574(process_name_query_request)
  OK
[2018/04/13 16:48:42.813514,  3] ../source3/nmbd/nmbd_incomingdgrams.c:118(process_host_announce)
  process_host_announce: from MACK-18<00> IP 192.168.1.8 to WORKGROUP<1d> for server MACK-18.
[2018/04/13 16:48:42.813710,  3] ../source3/nmbd/nmbd_sendannounce.c:170(send_local_master_announcement)
  send_local_master_announcement: type 849a03 for name VUDUO2 on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:48:42.813870,  3] ../source3/nmbd/nmbd_sendannounce.c:189(send_workgroup_announcement)
  send_workgroup_announcement: on subnet 192.168.1.103 for workgroup WORKGROUP
[2018/04/13 16:48:42.818510,  3] ../source3/nmbd/nmbd_serverlistdb.c:401(write_browse_list)
  write_browse_list: Wrote browse list into file /var/lib/samba/browse.dat

I have also changed ip, netbios name and pc for this test.

[WanWizard]

What do you mean? The root share? Hmm, doesn't work here either.

 

I've been looking into it, seems that with Samba 4 more things have changed. The Media and Harddisk share both have "public = yes" which now seems to be an alias for "guest = ok", so it simply connects without password, even though it prompts for one. If I remove those, none of the shares work anymore.

 

Digging a bit further, I see that PAM isn't included at all, so linux accounts will never work. Guess someone needs to put a bit more effort in...

[mackguil]

What do you mean? The root share? Hmm, doesn't work here either.

I've been looking into it, seems that with Samba 4 more things have changed. The Media and Harddisk share both have "public = yes" which now seems to be an alias for "guest = ok", so it simply connects without password, even though it prompts for one. If I remove those, none of the shares work anymore.

So, I'am not crazy
 

Digging a bit further, I see that PAM isn't included at all, so linux accounts will never work. Guess someone needs to put a bit more effort in...

And now ?

 

Can I help you ?

 

[WanWizard]

No, you're not.

 

 And now ?

 

 

Now we need a developer to pick this up. This bit is beyond me I'm afraid.

[mackguil]

Ok, I wait for solution. 

[WanWizard]

As I understand samba dropped PAM support in v4.4. So we need a plan B, I'm not really in favor of downgrading samba or porting the v3 solution...

[betacentauri]

Here is the link to the commit:

https://github.com/s...c1d334940b5cc66

 

and this is the interesting part:

pam_winbind is not a total replacement, as the migrate functionality used
to keep the Samba password up to date with the system password is not
present, but otherwise can provide essentially the same services.

[mackguil]

Another Problem ...

 

When I try to mount a samba share in command line from another device to openpli.

 

Also a Permision denied.

root@setopbox:~# mount -t cifs -o user=cocoricoloco //192.168.1.86/myshare /mnt/smbshare/
mount: mounting //192.168.1.86/vuplus on /mnt/smbshare/ failed: Permission denied

[athoik]

mkdir -p /mnt/smbshare/

and then retry? In other words, does the folder /mnt/smbshare exits and it is empty?

[mackguil]

mkdir -p /mnt/smbshare/

and then retry? In other words, does the folder /mnt/smbshare exits and it is empty?

ls -lha /mnt/
drwxrwxrwt    4 root     root          80 Apr 14 18:18 .
drwxr-xr-x   16 root     root        1.3K Apr 12 23:14 ..
drwxr-xr-x   12 root     root        4.0K Apr 14 18:27 hdd
drwxr-xr-x    3 root     root         100 Apr 14 18:28 smbshare

The first part from my script  create the share with:

mkdir /mnt/smbshare

All worked fine since long year with Open pli 4.0 but didn't work with 6.1. 

[WanWizard]

Why does the mount command mention the share "myshare", while the response mentions the share "vuplus"?

 

What is this "other device"? If that is a recent Windows box, or an up to date NAS, it might be that SMBv1 is disabled, so you need to tell mount to use SMBv2:

root@setopbox:~# mount -t cifs -o user=cocoricoloco,vers=2.0 //192.168.1.86/myshare /mnt/smbshare/

This is not something that is changed on the box, it is a security update in Windows and most NAS systems that disabled SMBv1.

[mackguil]

This is not something that is changed on the box, it is a security update in Windows and most NAS systems that disabled SMBv1.

I flash an old op4.0 just now to test and the mount work fine ...

The problem is on the box not the other device (nas).

Edited by mackguil, 14 April 2018 - 17:46.

[mackguil]

I think that the two problems are related.

[WanWizard]

Possibly, as I don't have this problem as well (both with a mount between boxes as from the box to my Synology NAS).

[mackguil]

Hello

 

No news ?

 

[WanWizard]

No.

 

It isn''t an easy fix, and all energy goes to releasing 6.2 at the moment.

[mackguil]

Upgrade to OP 6.2 samba password won't work ....

 

Is there a fix in few time ?

 

[WanWizard]

No. Samba 4 no longer supports linux user accounts, and until now no real solution has been created.

 

It's on the todo list, but if I understand the samba team correctly, they are not going to re-introduce this feature.