On Fri, 2003-08-29 at 20:42, Kevin Buhr wrote: > Mark Roach <[EMAIL PROTECTED]> writes: > > > > All of a sudden, the server will reject all network communication on > > eth0, won't respond to pings, no ssh, no samba. (ssh gives the message : > > No route to host) However, if I ssh in through eth1 I am able to ping > > addresses _from_ eth0. If I ifdown eth0 && ifup eth0 everything starts > > working again. > > Sounds a little like it's not responding to ARPs on the "eth0" side. > Machines that don't already know "eth0"'s MAC address can't send > packets to it until it responds to an ARP request, but it's not a > problem when pinging out, for example, because the target host (or the > router) remembers the IP->MAC mapping when it receives the request > packet and knows where to deliver the reply on that basis. > > Running "tcpdump" on both the misbehaving host and another host while > trying to (unsuccessfully) ping in to the misbehaving host would > certainly help show what's going on.
That's a good thought, I had considered that. I think the problem is resolved now though. I replaced the network card and everything has been working just fine. I appreciate your help though. Thanks, Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
