No subject

also get a reply on C, which is not true when attempting to ping C 
from A).
 
>I very much wonder if it isn't a router configuration problem.

Well, it *might* be, however, remember, systemB is also on the same 
subnet as systemC, and systemA has no problem getting to B.
Just C.

>I note that the 192.168.*.* addresses are reserved for "private" networks that are 
>often NAT'd behind a router that does NAT. It can be either really easy to 
>setup this or, if setup wrong, really a pain.

Not a problem.  NAT is not involved.  And 10.X.Y.Z addresses are just 
as private as 192.168.*.* addresses.  This all on an internal 
corporate network.

>I'd first examine very closely the configuration of the router that bridges 
>the two networks. If for some reason you find that there are TWO routers, 
>or more likely a computer with two NICs bridging the two networks, then 
>routing can get really funky as the rogue route sometimes handles traffic 
>and sometimes doesn't. I've seen stuff like that cause me sleepless 
>nights... :-(

Yeah, I'd like to closely examine the routers involved as well, 
however, I have no access to them :(  

I do have a call into the networking group, but they have yet to 
respond (there's a suprise!).

Thanks,
-- 

Seeya,
Paul
--
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!