I just checked out netstat, and also checked the arp table, just for fun.
There's nothing in either table indicating the annoying IP address.
Anything else you can think of would be most helpful.
Thanks,
John
I had a similar problem on one of my machines recently. It turned out
that I had a loo
I had a similar problem on one of my machines recently. It turned out
that I had a loopback entry in the routing table for the offending IP
address. It's something to try, at least. Do netstat -r and make sure
the routes are sane.
Regards,
Nathan Grant
-Original Message-
From: [EMAIL
