[Samba] nmbd don't start but gives no error (termux)

[Rowland Penny]

On Sun, 30 Mar 2025 12:12:17 +0200
f0rhum via samba <samba at lists.samba.org> wrote:

> I resend because I may have done something wrong

Don't worry, you haven't done anything yet that cannot be fixed :-)

> 
> Hi Rowland
> I'm back
> With your forensic smb.conf I get a different behaviour, but please 
> notice I never used -N on my own before 

All that '-N' does with smbclient is to stop the password prompt and
therefor connect anonymously.
Connecting in this way just shows that connecting is possible and what
shares are available.

The 'SMB' protocol comes in three versions: 1, 2 and 3, with 3 being
the latest (and probably last) version.

From the Windows versions your camera is supposed to be compatible
with, the highest possible version should be SMBv2, but as it is
unknown just what the camera is using, it could be SMBv1. This is how
the SMB protocol works:
It is a negotiated protocol, the client first tries the highest version
it knows, usually SMBv3 nowadays, and if the server replies, it uses
that version, if not, it tries the next lower version, until they both
agree on the version.

There is a major problem with SMBv1, it is very insecure, so it is
turned off by default everywhere.

If you are not using SMBv1, there is very little point in running the
nmbd deamon, it is only used for NetBIOS and that requires SMBv1.
When you run 'smbclient -NL PHONE_IP' and get back:

SMB1 disabled -- no workgroup available

This is nothing to worry about, because it isn't using SMBv1, it cannot
use NetBIOS to get the workgroup name, but everything should work over
SMBv2.

If you can get share names back from the initial smbclient search
between your Samba client and phone, you should then move onto
attempting to connect to a share on the phone from the client using:

smbclient //PHONE_IP/SHARENAME -Uuser_on_phone%password

If this works, you should find yourself at a Samba prompt 'smb: \>'

If you get this far, you have proved that Samba is working between your
phone and your client.

A couple of examples:

smbclient -NL 192.168.1.125 -p 4445

	Sharename       Type      Comment
	---------       ----      -------
	server          Disk      
	IPC$            IPC       IPC Service (Samba Client bookstand)
SMB1 disabled -- no workgroup available

smbclient //192.168.1.125/server -p 4445 -Urowland%xxxxxx
Try "help" to get a list of possible commands.
smb: \> 

This is to a standalone server with:

disable netbios = yes
smb ports = 4445

in smb.conf

If you can connect to your phone from your client, you should then try
to connect to the phone from your camera, if this works, then okay, if
it doesn't, then it is possible that you require SMBv1 and if so, you
need to run it everywhere, even if it is insecure.
Add:

nbt port = 1137
to your smb.conf on the phone and start the nmbd deamon

Do not add:

server services = smb, nbt

It only works on a Samba AD DC.

Rowland