FS#48692 - [smbclient] wins name resolution doesn't work with 4.4.0-1

Attached to Project: Arch Linux
Opened by nackd (Prieto) - Friday, 25 March 2016, 17:32 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 12:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

$ ping freenas
ping: freenas: Name or service not known

$ pacman -Q smbclient
smbclient 4.4.0-1

$ sudo pacman -U /var/cache/pacman/pkg/smbclient-4.3.6-1-x86_64.pkg.tar.xz
[...]

$ ping freenas
PING freenas (192.168.1.128) 56(84) bytes of data.
64 bytes from 192.168.1.128 (192.168.1.128): icmp_seq=1 ttl=64 time=0.669 ms
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 12:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  initial issue was solved, old report, assuming all haven been fixed meanwhile.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 25 March 2016, 20:30 GMT
Look at release notes, you need to enable winbindd.service
Comment by nackd (Prieto) - Friday, 25 March 2016, 23:47 GMT
  • Field changed: Percent Complete (100% → 0%)
smbclient does not have a winbindd.service. It seems to be part of samba, but that's not even an optional dependency.
Comment by Jonathan Clark (jc79) - Saturday, 26 March 2016, 15:02 GMT
I am sorry to be thick. I have exactly the same problem as the original error report, except that in order to downgrade, I have to enter "sudo pacman -v -U /var/cache/pacman/pkg/smbclient-4.3.6-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/samba-4.3.6-1-x86_64.pkg.tar.xz" because I do have samba also installed. After I do this wins name resolution works again.

But if I revert to samba and smbclient 4.4.0-1, wins name resolution stops working even though I have winbindd.service running. I can find no hint as to what other changes I may need to make to get wins name resolution working after the upgrade to 4.4.0-1 despite having read the release notes.
Comment by nackd (Prieto) - Saturday, 26 March 2016, 15:46 GMT
I also find it a bit strange that the NSS WINS libraries are in smbclient and the service in samba. Shouldn't they be part of the same package?
Comment by Giovanni Santini (ItachiSan) - Sunday, 10 April 2016, 08:54 GMT
Also, enabling the winbindd service does not work for me.
Only downgrading both smbclient and libwbclient give some results.
I can post some logs, if you want.
Comment by Giovanni Santini (ItachiSan) - Sunday, 17 April 2016, 08:38 GMT
The error is still present even after 4.4.2 upgrade.
Comment by Giovanni Santini (ItachiSan) - Monday, 18 April 2016, 11:38 GMT
I tried to disable UFW, still no success.
Comment by Serede (Serede) - Sunday, 01 May 2016, 16:58 GMT
Aye. I'm having the same issue and running the winbind daemon doesn't seem to help anyhow. Had to downgrade as well.
Comment by Giovanni Santini (ItachiSan) - Thursday, 12 May 2016, 10:24 GMT
Upgraded to 4.4.3, issue is gone.
Comment by Jonathan Clark (jc79) - Thursday, 12 May 2016, 10:38 GMT
For me too. Thank you so much Itachisan for telling us.
Comment by Giovanni Santini (ItachiSan) - Sunday, 15 May 2016, 10:01 GMT
I've a strange issue; winbindd is not working after system boot, but restarting the service fix the thing. Strange.
Comment by Serede (Serede) - Sunday, 15 May 2016, 12:00 GMT
I faced a similar problem since the samba share was being mounted before the winbind daemon had actually started, causing wins name resolution to fail once again.
I fixed it by adding a systemd dependency metaparameter to the fstab entry (x-systemd.requires=winbindd.service), hope that helps.
Comment by Giovanni Santini (ItachiSan) - Tuesday, 30 August 2016, 08:24 GMT
I have the issue again, name resolution not working for 4.4.5

EDIT: Never mind, the issues were firewall related.
Comment by Dāvis (davispuh) - Friday, 28 October 2016, 00:58 GMT
It looks like libwbclient (maybe samba/smbclient) update to 4.5.1-1 broke wins resolving...

I've "wins" entry in /etc/nsswitch.conf and
$ ping google.com
ping: google.com: System error

when I remove "wins" DNS works...
Comment by Richard PALO (risto3) - Sunday, 30 October 2016, 08:23 GMT
I'm seeing this too with:
libwbclient 4.5.1-1
samba 4.5.1-1
smbclient 4.5.1-1

needed to remove 'wins' from nsswitch.conf else anything using nameservices is fubar.

nmblookup seems fine though, and winbindd seems okay
● winbindd.service - Samba Winbind daemon
Loaded: loaded (/usr/lib/systemd/system/winbindd.service; enabled; vendor preset: disabled)
Active: active (running) since dim. 2016-10-30 08:42:04 CET; 39min ago
Main PID: 1142 (winbindd)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/winbindd.service
├─1142 /usr/bin/winbindd -D
├─1166 /usr/bin/winbindd -D
└─3436 /usr/bin/winbindd -D

oct. 30 08:42:03 sarchx64 systemd[1]: Starting Samba Winbind daemon...
oct. 30 08:42:04 sarchx64 systemd[1]: Started Samba Winbind daemon.
oct. 30 08:42:05 sarchx64 winbindd[1142]: [2016/10/30 08:42:04.626080, 0] ../source3/winbindd/winbindd_cache.c:3244(initialize_winbindd_cache)
oct. 30 08:42:05 sarchx64 winbindd[1142]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
oct. 30 08:42:09 sarchx64 winbindd[1142]: [2016/10/30 08:42:09.217939, 0] ../lib/util/become_daemon.c:124(daemon_ready)
oct. 30 08:42:09 sarchx64 winbindd[1142]: STATUS=daemon 'winbindd' finished starting up and ready to serve connections

things were fine before I upgraded recently.

Loading...