On Monday 06 May 2002 6:15 pm, [EMAIL PROTECTED] wrote: > Run tcpdump or equivalent on 192.168.0.17 and see what's getting > there, and whether it is replying, if at all. Also check the routing > tables, I've a feeling it's either eating the packets due to firewalling, > or because it doesn't know where to send the replies to due to incorrect > routing.
I agree with these suggestions. Tcpdump on a firewall can show you some odd things - have a look at it on the destination machine to get a better idea what's going on. Routing is a common cause of severe head-scratching in completely the wrong direction... Antony.
