Fedora 14 Not able to ping the hostname from any system.

swatchie · 11-24-2010, 10:44 PM

I did a new install of Fedora 14. This is my first time using Linux seriously and I am trying to figure it all out.

I am able to ping my hostname of sinbad only from the linux system itself. On all my windows boxes, I am not able to ping it. I can only ping the IP address.

Here is /etc/hosts:

Quote:

192.168.160.103 sinbad # Added by NetworkManager
127.0.0.1 localhost.localdomain localhost sinbad.localdomain localhost4
::1 sinbad localhost6.localdomain6 localhost6

I disabled the firewall, disabled SELinux, and still not able to ping it.

here is the info from ifcfg-eth0 :

Quote:

DEVICE=eth0
BOOTPROTO=dhcp
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
#IPV6INIT=no
NAME="System eth0"
#UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
USERCTL=no
HWADDR=00:E0:4C:96:F6:44
PEERDNS=yes
PEERROUTES=yes
DHCP_HOSTNAME=pirates
IPV6INIT=no
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03

and the resolv.conf

Quote:

# Generated by NetworkManager
domain austin.rr.com
search austin.rr.com
nameserver 209.18.47.61
nameserver 209.18.47.62

I have been messing with this all day and it is starting to make me mad. I looked over all 7 pages here and was not able to find a resolution, so I am hoping that someone will be able to have an answer to this.

JoshyJ · 11-24-2010, 10:49 PM

Removed due to reading problem wrong.

forrestt · 11-24-2010, 11:02 PM

You are going about this from the wrong direction. The problem isn't on the Linux box, it is on the Windows systems. Your system isn't in DNS, and therefore they don't know the IP address associated with the Linux hostname (computers don't care about hostnames, they only know how to talk addresses and need some way to convert the name you tell them to the address they can understand). You need to add the hostname and IP address to c:\Windows\system32\drivers\etc\hosts on your Windows systems or set up a local DNS server and have that serve the hostname/ip resolution (I'd op for the former since it requires much less technical knowledge).

HTH

Forrest

swatchie · 11-24-2010, 11:15 PM

Quote:

Originally Posted by forrestt

You are going about this from the wrong direction. The problem isn't on the Linux box, it is on the Windows systems. Your system isn't in DNS, and therefore they don't know the IP address associated with the Linux hostname (computers don't care about hostnames, they only know how to talk addresses and need some way to convert the name you tell them to the address they can understand). You need to add the hostname and IP address to c:\Windows\system32\drivers\etc\hosts on your Windows systems or set up a local DNS server and have that serve the hostname/ip resolution (I'd op for the former since it requires much less technical knowledge).

HTH

Forrest

This was exactly it. I was just trying to reply to that effect. I am guessing that I need to add all my windows systems to the linux /etc/hosts file as well.

Might have to look at setting up a DNS server then. This is all a learning experience for me anyway so this will be good.

Thanks !

jefro · 11-25-2010, 02:39 PM

You may not need dns.

Do all of your windows boxes have the hosts file entries for all of your systems? Each name should be set to each boxes ip in all systems. Every box should be in the list.

archtoad6 · 11-28-2010, 10:34 AM

I don't know what you are using a router/gateway/firewall; but if you were using IPCop or SmoothWall Express, the hosts file on the firewall box would be served to the LAN as a "master" hosts file. You'd also get a good firewall

.

This behavior is a feature of dnsmasq, which you could install on your Linux box. I found both .deb & .rpm packages.