Re: Problem with local network

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim wrote:

>On Fri, 2006-01-20 at 20:37 +0000, Chris Jones wrote:
>
>>[root@bilbo ~]# ifconfig eth0
>>eth0 Link encap:Ethernet HWaddr 00:0F:EA:8C:2E:52
>> inet addr:192.168.0.3 Bcast:192.168.0.255
>
>
>Okay, this shows your own interface is apparently working.
>
>>[root@bilbo ~]# ping -c4 192.168.0.3
>>PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
>>64 bytes from 192.168.0.3: icmp_seq=0 ttl=64 time=0.069 ms
>
>
>Pinging itself shows internally to the same PC that its network is
>working. (It probably doesn't really ping the hardware - some will,
>some won't.)
>
>>- --- 192.168.0.3 ping statistics ---
>>4 packets transmitted, 4 received, 0% packet loss, time 3003ms
>>rtt min/avg/max/mdev = 0.054/0.058/0.069/0.011 ms, pipe 2
>>[root@bilbo ~]# ping -c4 bilbo
>>ping: unknown host bilbo
>
>
>This is most likely because you're trying to use some DNS server that
>knows nothing about your names. Your router probably doesn't know what
>machine names go with what IPs, some don't have a DNS server that works
>that way.
>
>>My /etc/hosts shows:
>># Do not remove the following line, or various programs
>># that require network functionality will fail.
>>127.0.0.1 localhost.localdomain localhost
>>192.168.0.3 bilbo.stow-jones.local bilbo
>>192.168.0.2 gandalf.stow-jones.local gandalf
>>192.168.0.5 frodo.stow-jones.local frodo
>
>
>This looks fine.
>
>>The last three entries are for the PC's on the network.
>>
>>/etc/resolv.conf shows:
>>nameserver 192.168.0.1
>>nameserver 212.23.3.100
>>nameserver 212.23.6.100
>>search stow-jones.local
>># generated by NetworkManager, do not edit!
>>
>>The first line refers to my router, the other two nameservers are my
>>ISP's.
>
>
>Your ISP's aren't going to resolve local names, and the router mightn't
>either, unless specifically programmed to.
>
>Does your /etc/nsswitch.conf file have a line in it like this? (Below.)
>And no other conflicting "hosts: " lines?
>
>hosts: files dns
>
Yes. It does indeed.

>If so, then the machine should first check the hosts file for some
>network resolution issues. However, some things like dig will never
>look at the hosts file.
>
>>When I check the status of the named service, I get the following:
>>[root@bilbo ~]# service named status
>>rndc: couldn't get address for 'localhost': not found
>>[root@bilbo ~]#
>
>
>Now that's weird. What happens when you ping localhost,
>localhost.localdomain, and 127.0.0.1?
>
The ping commands return the following:-
[root@bilbo audit]# ping -c4 localhost.localdomain
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=0 ttl=64 time=0.059 ms
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.055 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.053 ms
64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.056 ms

- --- localhost.localdomain ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.053/0.055/0.059/0.009 ms, pipe 2
[root@bilbo audit]# ping -c4 localhost
ping: unknown host localhost
[root@bilbo audit]# ping -c4 127.0.0.17
PING 127.0.0.17 (127.0.0.17) 56(84) bytes of data.
64 bytes from 127.0.0.17: icmp_seq=0 ttl=64 time=0.065 ms
64 bytes from 127.0.0.17: icmp_seq=1 ttl=64 time=0.052 ms
64 bytes from 127.0.0.17: icmp_seq=2 ttl=64 time=0.056 ms
64 bytes from 127.0.0.17: icmp_seq=3 ttl=64 time=0.056 ms

- --- 127.0.0.17 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3012ms
rtt min/avg/max/mdev = 0.052/0.057/0.065/0.007 ms, pipe 2
[root@bilbo audit]#


- --
Somewhere in DOWNTOWN BURBANK a prostitute is OVERCOOKING a LAMB CHOP!!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFD0kPNZJbxzczKArcRAppVAJ9QKiB9+yv/ncRB1Zw2L1B8s8/WeQCffUPS
bm3rH62kdXqUTaXTKrtLVMs=
=vRJr
-----END PGP SIGNATURE-----

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: calling functions at the same time
    ... >plan to timestamp the pings) to test and measure network conditions over ... >different routes to different hosts. ... Putting all the ping hosts in a list ... >> have in mind. ...
    (comp.lang.python)
  • Re: W2K3 servers cant ping each other
    ... W2K3 servers enterprise ed. on my network ... > are able to ping all internet hosts and the other hosts ... > on my own network, and everyone can ping the W2K3 servers... ...
    (microsoft.public.windows.server.networking)
  • Re: Problem with local network
    ... Pinging itself shows internally to the same PC that its network is ... (It probably doesn't really ping the hardware - some will, ... And no other conflicting "hosts: ... then the machine should first check the hosts file for some ...
    (Fedora)
  • Re: Detect network connection
    ... This allows you to ping between two hosts ... without actually logging into one of them an performing the ping test... ... >> I need to be able to detect wether a computer has an active network ... and basically when there isn't a network connection there is an ...
    (microsoft.public.scripting.vbscript)
  • Re: Mshome is not accessible
    ... Windows Network, and select the workgroup I get: ... Mshome is not accessible. ... All computers are running Windows XP SP2 and are members of the MSHOME ... Computer A can ping using ping hom100fr001. ...
    (microsoft.public.windowsxp.network_web)