Red Hat Bugzilla – Bug 426133
wins name resolution broken
Last modified: 2007-12-18 19:40:41 EST
Description of problem:
Can not resolve host names through wins.
ping and nmblookup fail to resolve netbios names.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit nsswitch.conf to add "wins" to hosts line
2. ping a wins host
3. nmblookup a wins host
Failure to resolve name to address
Expected name to resolve
Works fine on fedora 6 & 7
I need details on your configurations (smb.conf, nsswitch.conf) and the exact
commands you use to test this.
Also a level 10 log of nmbd operations would be appreciated.
smb.conf is default supplied with distribution. Samba service is not enabled.
nmbd is not running.
I only made the modification noted above to nsswitch.conf (added "wins" to hosts
line). Otherwise it is default supplied with the distribution.
# ping smartstor
ping: unknown host smartstor
# nmblookup smartstor
querying smartstor on 192.168.13.255
name_query failed to find name smartstor
These commands work on identically configured fc6 and fc7 systems on the same
Please let me know if this is not sufficient information.
So you have not set a "wins server =" line in smb.conf ?
Are you trying to just do broadcast resolution ?
Can you strace ping and tcpdump the network to see the network traffic ?
Created attachment 289957 [details]
strace of ping
Created attachment 289958 [details]
dump during ping
Correct, wins server is not set in smb.conf
Attachments for strace and tcpdump above.
In strace, you can see select timeout after the netbios request is made.
In tcpdump, you can see a netbios response from 192.168.13.72. This is the
address of the machine I am attempting to ping. For some reason, ping isn't
seeing this response?
The packet trace shows your machine firewall configuration is blocking the reply
and sending back a reject.
14:43:47.172194 IP johns-encoder.jetheaddev.com > 192.168.13.72: ICMP host
johns-encoder.jetheaddev.com unreachable - admin prohibited, length 98
turn off your firewall or enable UDP replies for NBT packets on port 137 and > 1024
Well now, don't I feel stupid! Thanks.
The firewall config has a service for samba which if allowed, fixes the problem.
However, in the process of attempting to fix my firewall, I think I found
another bug. system-config-firewall.py attempts to load
/usr/share/system-config-firewall/system-config-firewall_48.png. This file does
not exist (I checked the rpm, its not in there). Exits with error. There is a
file /usr/share/icons/hicolor/48x48/apps/system-config-firewall.png. I copied
this file to the expected location to work around the problem.