On 18.10.2024 21:45, Gilles via samba wrote:> On 18/10/2024 20:52, Peter Milesson via samba wrote:
>> I see that port 139 is active. It shouldn't be there if you have
>> turned netbios. In my smb.conf I have got:
>>
>> ??????? disable netbios = yes
>> ??????? smb ports = 445
>>
>> and no port 139 shows up.
>> Netbios is ancient and deprecated, shouldn't be there.
>>
>> When having a look at your smb.conf excerpt, do you really need the
>> lines:
>>
>> hosts allow = 127.0.0.1 192.168.0.0/24
>> hosts deny = 0.0.0.0/0
>> bind interfaces only = yes
>> interfaces = 192.168.0.15/255.255.255.0 127.0.0.1/255.255.255.255
>>
>> Unless you have more interfaces and IP addresses, those lines are not
>> needed in a small network. Block unwanted networks in the firewall
>> instead.
>>
>> Then, interfaces you should probably refer to interfaces like lo and
>> eth0, instead of IP-address/mask. I know that the wiki states that
>> you can use IP addresses, but to me, an interface isn't an IP
address.
>>
>> Comment out the 4 lines, restart smbd and winbindd and try again.
>
> I already had "disable netbios = yes" in [global]. I added
"smb ports
> = 445", and edited the other lines accordingly.
>
> Apparently, "The winbindd daemon is part of the winbind service and is
> used to allow Unix systems to obtain user and group information from a
> Windows NT/2000 server." Do I need it to run a single Samba server in
> a home network with no Windows server?
>
> Reloaded smb.conf, and gave browsing a new try: still slow.
>
> > Just another point. What does the dhclient do in your server with a
> fixed IP address? It shouldn't be there, unless your server gets the
> address from DHCP. Disable/uninstall the service. Also make sure that
> your hosts file has got proper information. If your server has got a
> fixed IP address it should be something like:
> > 127.0.0.1?????? localhost
> > 192.168.0.15 ??? datasrv.private.home ? datasrv
>
> I use my ADSL modem's DHCP server to assigns IP addresses.
>
> The Windows computer does have Samba's IP address in its hosts file
> (ping works).
>
> Interestingly, I get the same problem when running the following on
> the Samba server, so it's not a Windows problem:
> ===========> root at debian:~# smbclient -L localhost
> Password for [WORKGROUP\root]:
>
> ??????? Sharename?????? Type????? Comment
> ??????? ---------?????? ----????? -------
> ??????? www ????????? Disk
> ??????? sdcard????????? Disk
> ??????? IPC$??????????? IPC?????? IPC Service (Samba 4.17.12-Debian)
> SMB1 disabled -- no workgroup available
> ===========
Hi Gilles,
The dhclient fulfills no function on your server, as you have got a
fixed IP address. It does not provide services to other computers in the
network either.? IMHO, it may even confuse wsdd (just a hunch).
About winbind, there are other on the list who could answer that
question with more certainty. You could always try to shut down winbind.
But make sure you have got the following entries in nsswitch.conf
passwd:???????? files systemd
group:????????? files systemd
hosts:????????? files dns
networks:?????? files
winbind should not be there.
Best regards,
Peter