On 9/19/22 11:14, Shannon Price via samba wrote:> From the original problem - why is there a difference in mapping FQDN vs
short name?
>
> \\SERVER\SHARE
> \\SERVER.DOMAIN.NAME\SHARE
>
> Is this something different happening on the client side with the way it
talks to the server?
>
> --
> Shannon
>
>> The problem now is only that I have full access to everything with
>> unqualfied names (\\SERVER\homes< file://SERVER/homes> works),
but
>> FQDN (\\server.domain.edu\homes<
>> file://server.domain.edu/homes>)
>> doesn't work and the debug logs show that Samba wants winbind
>> whenever I talk to the server with FQDN.
>>
>> Logs with FQDN:
>> [2022/09/17 08:40:16.941558, 0]
>> ../../source3/auth/auth_winbind.c:120(check_winbind_security)
>> check_winbind_security: winbindd not running - but required as
>> domain member: NT_STATUS_NO_LOGON_SERVERS
>> [2022/09/17 08:40:16.943204, 2]
>> ../../source3/auth/auth.c:343(auth_check_ntlm_password)
>> check_ntlm_password: Authentication for user [USERNAME] ->
>> [USERNAME] FAILED with error NT_STATUS_NO_LOGON_SERVERS,
>> authoritative=1
>> [2022/09/17 08:40:16.943300, 2]
>> ../../auth/auth_log.c:635(log_authentication_event_human_readable)
>>
>> Logs without FQDN:
>> 131.204.17.34 (ipv4:131.204.17.34:28915) connect to service USERNAME
>> initially as user USERNAME (uid=12345, gid=123) (pid 454545)
>> [2022/09/17 10:15:38.595009, 0]
>> ../../source3/param/loadparm.c:3358(process_usershare_file)
>
Yes. When using the FQDN, Windows Clients (and Samba Clients) use DNS to
look up the name, and connect on Port 445.
When using the Short name, Windows/Samba Clients use WINS or NetBios to
look up the name, and connect on port 139. Two distinctly different
Protocols.
The Port 139 variant is used by Win9x and NT4 Clients.
The Port 445 Variant is used by Windows 2000 and later.