net usershare add: cannot convert name "everyone" to a SID. The transport connection is now disconnected.

[Carlos Alberto Lima dos Santos]

If use Nautilus or command line to share a folder

'net usershare' returned error 255: cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe lsarpc failed with error NT_STATUS_CONNECTION_DISCONNECTED
net usershare add: cannot convert name "Everyone" to a SID. The transport connection is now disconnected..

OS: Ubuntu 24.04 LTS x86_64
Host: Inspiron 5480
Kernel: 6.8.0-39-generic
Uptime: 4 hours, 13 mins
Packages: 2668 (dpkg), 12 (flatpak), 19 (snap)
Shell: bash 5.2.21
Resolution: 1920x1080
DE: GNOME 46.0
WM: Mutter
WM Theme: Adwaita
Theme: Yaru-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i7-8565U (8) @ 4.600GHz
GPU: Intel WhiskeyLake-U GT2 [UHD Graphics 620]
GPU: NVIDIA GeForce MX150
Memory: 14310MiB / 31811MiB

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: samba 2:4.19.5+dfsg-4ubuntu9
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BothFailedConnect: Yes
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 26 18:49:10 2024
InstallationDate: Installed on 2024-05-03 (85 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SambaServerRegression: Yes
SmbConfIncluded: Yes
SmbLog:

SourcePackage: samba
TestparmExitCode: 0
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Miriam España Acebal (mirespace)]

Hello Carlos Alberto,

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I wanted to ask you a couple of things. Checking the logs attached, I saw a network issue:

 Packet send failed to 10.125.143.255(138) ERRNO=Network is unreachable
  Packet send failed to 192.168.78.255(137) ERRNO=Network is unreachable
  send_netbios_packet: send_packet() to IP 192.168.78.255 port 137 failed

1) Is this still happening? It seems that it might be a punctual network issue affecting the sharing.

2) If the answer to the above is "no" and you are still experiencing this message, I found a similar (but old) bug: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186 .Could you check if any of the actionable comments work for you (e.g., https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186/comments/10 )? If you want more info about the guest account settings, please check https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html

Let us know how it goes. In the meantime, I will set this bug as "Incomplete". Please mark it again as "New" when sharing new information about the case here.

Thanks in advance.

[Carlos Alberto Lima dos Santos (toca.cals)]

     Hi Miriam,

     Thanks for your help.

     I think these errors are not related to the sharing I am trying to
do. These IPs that are showing errors are external IPs and not from the
internal network that I am using for sharing.

     I'm using the internal networks:

     192.168.111.0/24 and 172.16.12.0/24 to share folders.

Regards

==============================

Carlos Alberto Lima dos Santos

Eng. de Computação

http://www.linkedin.com/in/carlostoca

Campinas-SP / Brasil

On 9/23/24 06:38, Miriam España Acebal wrote:
> Hello Carlos Alberto,
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> I wanted to ask you a couple of things. Checking the logs attached, I
> saw a network issue:
>
> Packet send failed to 10.125.143.255(138) ERRNO=Network is unreachable
> Packet send failed to 192.168.78.255(137) ERRNO=Network is unreachable
> send_netbios_packet: send_packet() to IP 192.168.78.255 port 137 failed
>
> 1) Is this still happening? It seems that it might be a punctual network
> issue affecting the sharing.
>
> 2) If the answer to the above is "no" and you are still experiencing
> this message, I found a similar (but old) bug:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186 .Could you
> check if any of the actionable comments work for you (e.g.,
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186/comments/10
> )? If you want more info about the guest account settings, please check
> https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
>
>
> Let us know how it goes. In the meantime, I will set this bug as "Incomplete". Please mark it again as "New" when sharing new information about the case here.
>
> Thanks in advance.
>

[Miriam España Acebal (mirespace)]

Hello Carlos Alberto,

Sorry for the delay; I was unavailable for some time.

It's good to know that those errors are not related.

Have you been able to take a look at the links I provided in 2) in my previous comment, especially this one [1]?

[1] https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186/comments/10

[Nicolas Binkowski (argonnate)]

Hello everyone.

Sorry to bring up this post from 2024, but the release of Zorin 18, based on Ubuntu 24.04, presents this bug and the proposed solutions don't work for me (guest account = nobody in smb.conf). The Zorin forum now has several posts where it's impossible to share with this error.

I found this post: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1299186

But it's from 2014, and I don't know which one to post on. This post #2074234 is closer to the current error message. Is a fix planned?
Thanks in advance, and sorry my post is inappropriate.
Nicolas.

[Lukas Märdian (slyon)]

Thank you Nicolas for confirming that this issue is still happening on 24.04 and the suggestion mentioned by Miriam in comment #5 does not help.

This means we'll need to find another solution..

Can you please share the following information?

- The exact command you're running when observing the error
  + The command "net usershare add temp /tmp/test bla nobody:F guest_ok=y" seems to work fine for me on 24.04
- The exact error message you're seeing.
- The contents of /etc/samba/smb.conf
- The output of "cat /etc/passwd | grep nobody"
- Confirm that you've set a SMB password via "sudo smbpasswd -a nobody"

[Nicolas Binkowski (argonnate)]

Hello Lukas, thank you very much for your reply.

As for the command I use when I notice the error, I don't use one because I use the Nautilus-Share graphical interface. It's when I validate that the message appears in the window:

    - cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe lsarpc failed with error NT_STATUS_CONNECTION_DISCONNECTED. net usershare add: cannot convert name "nobody" to a SID. The transport connection is now disconnected..

The same message appears when I test with the same command you suggested:
    - nicolas@Zorin18-VirtualBox:~$ net usershare add PartageZorin /home/nicolas/Documents/PartageZorin ZorinShare nobody:F guest_ok=y
cli_rpc_pipe_open_noauth: rpc_pipe_bind for pipe lsarpc failed with error NT_STATUS_CONNECTION_DISCONNECTED
net usershare add: cannot convert name "nobody" to a SID. The transport connection is now disconnected..

I also confirm that I set nobody's password with smbpasswd. I left the password blank. Is that the problem?

Here is also the contents of smb.conf:

    - nicolas@Zorin18-VirtualBox:~$ grep -E "^[^#;].*" /etc/samba/smb.conf
[global]
   workgroup = WORKGROUP
   server string = %h server (Samba, Ubuntu)
   server min protocol = SMB2
   client max protocol = SMB3
   dns proxy = no
   syslog = 0
   passdb backend = tdbsam
   log file = /var/log/samba/log.%m
   max log size = 1000
   logging = file
   panic action = /usr/share/samba/panic-action %d
   server role = standalone server
   obey pam restrictions = yes
   unix password sync = yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   pam password change = yes
   map to guest = bad user
   security = user
   username map = /etc/samba/smbusers
   usershare owner only = False
   guest account = nobody
   usershare allow guests = yes
[printers]
   comment = All Printers
   browseable = no
   path = /var/tmp
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no

Several lines aren't there natively. Like server min or max protocol or username map, for example. I only tried a few solutions found on the web to resolve my problem, but they didn't work.

And the contents of /etc/passwd for nobody:

    - nicolas@Zorin18-VirtualBox:~$ cat /etc/passwd | grep nobody
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin

Thank you very much for your time. Have a great day.

Nicolas

[Utkarsh Gupta (utkarsh)]

Ubuntu 25.04 (Plucky Puffin) has reached end of life, so this bug will not be fixed for that specific release.

[Athos Ribeiro (athos)]

Hi Nicolas,

Thanks so much for providing additional information on this one.

Would you be able to come up with a detailed step-by-step guide on how to reproduce this issue on a Ubuntu 24.04 fresh install?

Once you do so, please, move this bug status from Incomplete back to new.