Article View: ahn.tech.linux
Article #1210Re: funny networking 101 problem...
From: jonathan.archer
Date: Sat, 11 Nov 2000 01:14
Date: Sat, 11 Nov 2000 01:14
53 lines
2890 bytes
2890 bytes
Hi
I find that using a DHCPD server makes life a whole lot easier, install
this one one machine and get the other to automatically retrieve an IP
address, you can arrange a static if you so wish. If the second machine can
recieve an IP then hey presto!!
For further info on DHCP just send me a mail, I will gladly help!!!
Cheers
Johno
felixthecat <felixthecat@erols.com> wrote in message
news:8udjjt$hgv$1@bob.news.rcn.net...
> Hi all --
> New to Red Hat (and Unix) but having fun. Trying to get two boxes on a LAN
> to talk. Both are RedHat 6.2. Both have local addr (192.168.1.2 and
> 192.168.1.3)
> Both can successfully ping themselves (the 192 addrs) but there seems to
be
> a prob w/ the interface for .2 It can't ping .3; get "network is
> unreachable", and pinging from .3 to .2 get "Destination Host
unreachable".
>
> indeed, seems the .2 interface is not 'up'. 'ifconfig' (with no params)
> yields 'UP' info for localhost, and nothing for the 192 addr, and if i
force
> it with 'ifconfig -a' it doesn't seem to be UP:
>
> eth0 HWAddr 00:A0:CC:63:4D:AC
> inet bcast mask (all look good)
> BROADCAST RUNNING MULTICAST (note no 'UP')
>
> Whereas ifconfig for the .3 box yields 'UP' interfaces for both localhost
> and eth0.
>
> 'route' seems ok for .3
> 192.168.1.0 255.255.255.0 U 0 0 0 eth0
> 127.0.0.0 ....U 0 0 0 lo
>
> ...but not so good for .2, only get the localhost (nothing for 192)
>
> /etc/hosts file seems fine. have put both addrs into each host file on
each
> machine (that is, the host files are identical).
>
> 192.168.1.2 (the funky one) has a Netgear FA 310 TX Fast Ether PCI
adapter
> 192.168.1.3 3Com etherlink 10/100 PCI board 3C905C TX
>
> Any suggestions greatly appreciated!
> Cheers
> --Felixthecat
>
>
Technical Details
Message-ID:
<161P5.2670$f12.36315@news2-win.server.ntlworld.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!isdnet!grolier!btnet-peer0!btnet!news5-gui.server.ntli.net!ntli.net!news2-win.server.ntlworld.com.POSTED!not-for-mailReferences:
<8udjjt$hgv$1@bob.news.rcn.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11033e,25227f31cfb0f592 X-Google-Attributes: gid11033e,public X-Google-ArrivalTime: 2000-11-10 17:16:54 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!isdnet!grolier!btnet-peer0!btnet!news5-gui.server.ntli.net!ntli.net!news2-win.server.ntlworld.com.POSTED!not-for-mail From: "jonathan.archer" <jonathan.archer@ntlworld.com> Newsgroups: ahn.tech.linux References: <8udjjt$hgv$1@bob.news.rcn.net> Subject: Re: funny networking 101 problem... Lines: 55 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: <161P5.2670$f12.36315@news2-win.server.ntlworld.com> Date: Sat, 11 Nov 2000 01:14:34 -0000 NNTP-Posting-Host: 62.255.36.137 X-Complaints-To: abuse@ntlworld.com X-Trace: news2-win.server.ntlworld.com 973905405 62.255.36.137 (Sat, 11 Nov 2000 01:16:45 GMT) NNTP-Posting-Date: Sat, 11 Nov 2000 01:16:45 GMT Organization: ntlworld News Service