Networking help

Ken D'Ambrosio kend at flyingtoasters.net
Mon Nov 25 16:10:41 EST 2002


I shouldn't be an ARP issue -- if it were, then the other machine sending
pings wouldn't work.  Namely:

- If it were an ARP issue on the primary pinging machine, then that would
  infer the something kaput with the default router's MAC -- since that's
  the only MAC that would matter in this scenario.  One assumes Paul's
  tried pinging other hosts on other subnets (alas, I can't check the
  original e-mail).

- If it were an ARP issue on the router, then the second pinging machine
  wouldn't be able to ping, either.

- If it were an ARP issue on the destination machine, then, again, neither
  would be able to ping it.

I do, however, have to wonder if you're routing correctly.  Can you ping
the remote subnet's router address?  Is there any chance that the remote
machine's got a static route with an incorrect subnet mask?  Can you swap
IP addresses with the machine that works and give that a go?

$.02,

-Ken


> In a message dated: Mon, 25 Nov 2002 10:22:24 EST
> Marc Evans said:
>
>>When I have seen these in the past, I have usually found them to be
>> caused by an ARP issue. Try flushing the arp cache on the systems
>> involved and then retry you experiment.
>
> The arp tables are usually empty when this occurs.
>
>>If that doesn't work, look at all routers on
>>the network to insure that proxy-arp is disabled.
>
> I wish that I could, but the routers are out of my control :(
> --
>
> Seeya,
> Paul
> --
> 	It may look like I'm just sitting here doing nothing,
>    but I'm really actively waiting for all my problems to go away.
>
> 	 If you're not having fun, you're not doing it right!
>
>
> _______________________________________________
> gnhlug-discuss mailing list
> gnhlug-discuss at mail.gnhlug.org
> http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss






More information about the gnhlug-discuss mailing list