[Samba] smbclient -L localhost -N fails NT_STATUS_INVALID_NETWORK_RESPONSE
Stefan Kania
stefan at kania-online.de
Sun Nov 27 10:17:50 UTC 2022
If you use -N then a Kerberos-ticket is required and "localhost" has no
Kerberos principal so "localhost" together with Kerberos is not working,
you must use the hostname.
Am 24.11.22 um 11:16 schrieb Luis Peromarta via samba:
> Hi all,
>
> So I got my 4 DCs all nicely working. In 3 of them smbclient works fine.
>
> smbclient -L localhost -N
> Anonymous login successful
>
> Sharename Type Comment
> --------- ---- -------
> sysvol Disk
> netlogon Disk
> IPC$ IPC IPC Service (Samba 4.17.3-Debian)
> SMB1 disabled -- no workgroup available
>
>
> In the fourth one:
>
> smbclient -L localhost -N
> protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
>
> Same for:
>
> smbclient -L localhost -N -m SMB2
> protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
>
> smb.conf is the same in all DCs (except for netbios name)
>
> [global]
> netbios name = DC2
> realm = MAD.MATER.INT
> workgroup = MAD
> server role = active directory domain controller
> dns forwarder = 192.168.0.15 192.168.0.14
> idmap_ldb:use rfc2307 = yes
> interfaces = lo enp3s0
> bind interfaces only = yes
>
> [netlogon]
> path = /var/lib/samba/sysvol/mad.mater.int/scripts
> read only = No
>
> [sysvol]
> path = /var/lib/samba/sysvol
> read only = No
>
> I have no idea where the problem could be.
>
> Sysvol is accessible from windows machines, all GPOs are loaded from this machine when it is the logon server from the windows client.
>
> Any hint ?
>
>
> LP
More information about the samba
mailing list