At 11:04 AM 10/30/02 -0500, Christopher Audley wrote: [...]
Heres another thing I've noticed, the problem will appear separately for each client. On the DMZ I have two machines, A and B. A can't ping the Bering, but if I ping A from the Bering, after the first few packets it works. After this A can now ping the router. However, B still can not ping the router until I do the router->B ping. And this isn't always necessary, sometimes things just work.This sounds like an arp problem. try investigating when the router (and the client) acquires an arp entry for the host it is pinging, or being pinged by. Examples:
1. "A can't ping the Bering". After it tries and fails, does A's arp table have an entry for the Bering router's IP address? Does the Bering router's arp table have an entry for A?
2. "if I ping A from the Bering, after the first few packets it works". Do a short ping (only 1 or 2 packets) and see if A's and Bering's arp caches get entries for each other.
If it is an arp problem, it might be in your switch, some sort of problem with broadcast Ethernet frames (guessing a bit wildly here).
Finally, could you explain a bit more about your configuration? Why does this router have 2 NICs connected to the same switch? Does this introduce any ambiguities in its routing table, or even its arp resolution?
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
