On Wed, 30 Sep 1998, Jacques Du Pasquier wrote:
> Hello there,
>
> - one machine is named "phat" (IP 192.168.1.1), has RedHat 5.0
> - the other is named "admin" (IP 192.168.1.2), has Win95 with MS-TCP/IP
> - local domain name is corcise
> - netmask in both machines is 255.255.255.0
>
> What does work:
>
> - DNS looks OK, on both machines the name addres is resolved into the
> right IP address (phat=162.198.1.1, admin=162.198.1.2); I've set a
> netmask of 255.255.255.0 on both machines.
>
DNS can't work unless each machine is running its own nameserver if there
is no networking between them. Presumeably you have /etc/hosts set up OK
and the names are being resolved from there.
> - when I ping phat on admin, ping fails (times out), but the phat LAN
> adapter led blinks in rythm with the ping packets sent (also true in
> the other way, ie when I ping admin from phat).
>
What happens if you ping phat from phat (NOT localhost)?
> - on phat, some command (I've forgotten which one), that reports bytes
> sent to and received from an interface, reports the bytes sent when
> I ping admin from phat; and the bytes received when I ping phat from
> admin
>
That'd be ifconfig.
> /home/jacques 1012 # ifconfig
> eth0 Link encap:Ethernet HWaddr 00:00:E8:DE:CA:BB
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:198 errors:0 dropped:0 overruns:0
> TX packets:79 errors:0 dropped:0 overruns:0
> Interrupt:11 Base address:0x6500
>
That looks fairly healthy (although I'm surprised about that base address,
but if it wasn't there you'd be haveing worse problems).
> /home/jacques 1013 # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.1.0 phat.corcise 255.255.255.0 UG 0 0 4 eth0
Ah. That's wrong. This is telling phat that any packets going to
192.168.1.* should be routed to phat.corcise via eth0. That ain't gonna
work - packets will just loop as it sends everything back to itself.
Try either removing this entry (preferably) or changeing it to read
192.168.1.0 admin.corcise 255.255.255.0 etc
Do this with
route del 192.168.1.0 (I think this should work, but it might remove the
next entry as well, in which case you need to do
route add -net 192.168.1.0 eth0)
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 7 lo
>
These are correct.
HTH
--
Mike <[EMAIL PROTECTED]>
Immigration is the sincerest form of flattery.
-- Jack Paar
