[Bug 1802628] [NEW] winbind name resolution fails when remote host has multiple IPs

[Brian Turek]

Public bug reported:

Description:    Ubuntu 18.04.1 LTS
Release:        18.04

winbind:
  Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
  Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
  Version table:
 *** 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2:4.7.6+dfsg~ubuntu-0ubuntu2 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages


This is essentially a confirmation of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825380

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

** Affects: samba (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1802628

Title:
  winbind name resolution fails when remote host has multiple IPs

Status in samba package in Ubuntu:
  New

Bug description:
  Description:    Ubuntu 18.04.1 LTS
  Release:        18.04

  winbind:
    Installed: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
    Candidate: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2
    Version table:
   *** 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 500
          500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
          100 /var/lib/dpkg/status
       2:4.7.6+dfsg~ubuntu-0ubuntu2 500
          500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  This is essentially a confirmation of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825380

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1802628/+subscriptions