winbind name resolution fails when remote host has multiple IPs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Debian) |
Fix Released
|
Unknown
|
|||
samba (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 18.04.1 LTS
Release: 18.04
winbind:
Installed: 2:4.7.6+
Candidate: 2:4.7.6+
Version table:
*** 2:4.7.6+
500 http://
500 http://
100 /var/lib/
2:
500 http://
This is essentially a confirmation of https:/
I had the combination of smb and autofs working in Ubuntu 16.04 and then recently upgraded to 18.04. I hadn't checked my back-up logs that used autofs+smb for a while but today noticed that autofs claimed that it could not resolve my Win10 hostname (the remote backup endpoint). I found the above Debian bug report and can confirm that the issue is present in 18.04.
Steps to reproduce:
# ping abcomputer
ping: abcomputer : System error
# nmblookup abcomputer
192.168.1.8 abcomputer<00>
192.168.5.1 abcomputer<00>
Note the 192.168.5.1 IP is a Virtualbox host-only interface on the Win10 machine. I then remove the host-only interface from the Win10 computer
# nmblookup abcomputer
192.168.1.8 abcomputer<00>
# ping hyperion
PING abcomputer (192.168.1.8) 56(84) bytes of data.
64 bytes from 192.168.1.8 (192.168.1.8): icmp_seq=1 ttl=128 time=0.533 ms
Changed in samba (Debian): | |
status: | Unknown → Fix Released |
tags: | removed: server-todo |
The Debian bug is closed by accident, the root cause was not fixed, just an issue that came up while checking.
I'll have to ask andreas to take a look and let you know (he knows samba much better than I do).
Subscribing him