Ping Hosts by Name not Working 14.2

jcamez · 08-05-2016, 02:40 PM

Quote:

Originally Posted by kjhambrick

jcamez --

Since you mentioned WINS in your original post, I have to ask ...

Is smb running on the 14.2 box ?

Code:

ps -ef |grep smb

Or do you have a firewall running ?

If so, I believe WINS wants to chat on port 137 {?}

HTH

-- kjh

Hi kjhambrick!

Code:

bash-4.3# ps -ef | grep smb
root      1149     1  0 12:09 ?        00:00:00 /usr/sbin/smbd -D
root      1151  1149  0 12:09 ?        00:00:00 /usr/sbin/smbd -D
root      1152  1149  0 12:09 ?        00:00:00 /usr/sbin/smbd -D
root      1160  1149  0 12:09 ?        00:00:00 /usr/sbin/smbd -D
root      4648  1149  0 12:24 ?        00:00:00 /usr/sbin/smbd -D
root      4843  4717  0 12:37 pts/0    00:00:00 grep smb
bash-4.3#

Samba it is running. So i'm really lost as to why i can't ping by name. If i ping my linux box from a windows machine, it works ok but not the other way. I haven't found what configuration it's missing that was not necessary in 14.1.

bassmadrigal · 08-05-2016, 02:57 PM

Quote:

Originally Posted by jcamez

1) My /etc/resolv.conf shows the corresponding lines of my router.

" ##Generated by NetworkManager
nameserver 200.52.162.137
nameserver 200.52.160.200
nameserver 200.77.146.137 "

2) i have think of that, but then i would have to add a line every time my ip changes right??

Thanks.

I wonder if this is something with NetworkManager (or maybe the dhcp client you are using with NM), because on my resolv.conf (generated with dhcpcd), I only have my router listed as my nameserver (and then I have Google's DNS servers listed on my router in addition to whatever it gets from the ISP's DHCP server).

Code:

jbhansen@craven-moorhead:~$ cat /etc/resolv.con
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 10.0.0.1
# /etc/resolv.conf.tail can replace this line

What happens if you add your router's IP as an additional nameserver in your resolv.conf?

Code:

##Generated by NetworkManager
nameserver 192.168.1.1  #or whatever your router's IP is
nameserver 200.52.162.137
nameserver 200.52.160.200
nameserver 200.77.146.137

michaelk · 08-05-2016, 03:19 PM

The OP wants local DNS within the LAN. Did you install winbind?

Windows netbios can resolve names to IP addresses because it broadcasts the information and each system stores the information in a cache. samba broadcasts the information for windows clients but can not automatically use it without winbind and changes to nsswitch.conf.

Do your windows computers have netbios over TCP enabled?

Richard Cranium · 08-05-2016, 03:49 PM

Quote:

Originally Posted by allend

Code:

bash-4.3$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 211.29.132.12
nameserver 198.142.0.51

and excerpt from /strace ping -c2 www.google.com'

Code:

socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("211.29.132.12")}, 16) = 0

stares

Given that the error was 'host not found', the problem the OP was experiencing was that DNS wasn't working versus something wrong with 'ping'.

zk1234 · 08-05-2016, 04:13 PM

Quote:

Originally Posted by jcamez

i have think of that, but then i would have to add a line every time my ip changes right??

Thanks.

Yes and no. It depends on the way in which your DHCP works (*).
Anyway, if this is so important for you, why aren't you using static IPs?

(*)
1) If you use DHCP client only, you may have the same IPs all the time (only router "makes decisions").
2) If you have DHCP daemon running, you may have different IPs (router+daemon "make decisions")

.

MarcT · 08-05-2016, 08:25 PM

I wonder if it's not picking up libnss_wins? First try running "ldconfig -v" (as root), and see if the issue is fixed.

If not, try this to see if the wins library is being loaded:

Code:

root@anvil:~# strace ping wibble 2>&1 | grep -i wins

(wibble is just a non-existant host-name)

You should see something like:

Code:

open("/usr/lib64/libnss_wins.so.2", O_RDONLY|O_CLOEXEC) = 4

M