This is a very good explanation, however I have this identical scenario
with one of my co-los. I have gone round and round with the administrator
for over a year now with no solution.
You make the statement below that these two machines can't communicate,
however I can ping and tracroute the
On Wed, Sep 18, 2002 at 02:55:32PM -0400, Jim wrote:
This is a very good explanation, however I have this identical scenario
with one of my co-los. I have gone round and round with the administrator
for over a year now with no solution.
You make the statement below that these two machines
Chris Byrnes wrote:
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is
not on local network
Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is
not on local network
After doing some reading, I've already issued, sysctl -w
Crist J. Clark [EMAIL PROTECTED] probably said:
This is a netmask problem, but not really the one that other people
have described. This is how it usually works. Your troubled machine
above, servername, receives an ARP who-has from another machine on
the LAN called clientname. However, the IP
I get these errors generated on a machine which has the correct
netmask, no static routes, no incorrect routes of any kind.
During a migration there are multiple IP networks on the same physical
switched network, if I connect to one of the machines in the other
network on the same wire,
