Let's see now, standard troubleshooting:
Do everything by IP address, until the basic network is known to be
good lets not add the resolver into the picture!
1) Make sure your new IP addresses are being used with the right
subnet mask and gateway. Since you cannot ping the machine, see if
traceroute shows something funny (like trying to go to a router)>
2) Use tcpdump to watch the network while you are pinging the other
machine. Do you see an ARP? An answer to the ARP? What does the ARP
cache look like?
On Sun, Feb 18, 2001 at 01:34:41PM -0700, Daddy Mak wrote:
> I've got a weird routing issue that I'm sure has a fairly simple solution:
>
> My workstation, Mitch, has the ip a.b.c.d, he just got this ip this
> morning. Earlier he had w.x.y.z.(diff s/n) Neko, my new web server at
> another location has the ip l.m.n.o, but previously held a.b.c.d (Mitch's
> current ip) After Mitch got his new ip, he could no longer connect
> directly to Neko, not even ping. He can however ping the
> ip below neko's (another box at that location), and neko accepts pings
> from Poo which is on the same s/n as Mitch. Mitch's ip used to belong to
> Neko while being configured at this location, but everything has been
> updated, including forward and reverse dns...any ideas?
>
> --
> "Americans are benevolently ignorant about Canada while Canadians are
> malevolently well informed about the United States." - J. Bartlett Brebner
>
> -Chris Maki http://phresh.net
>
>
--
|
I am not sure how many monkeys it would take to type out the
works of Shakespear. I do know how many cats it would take to spam a
maillist if I leave my computer on.
AA4YU http://www.beekeeper.org http://www.q7.net
|