Re: dymanic route table problem

I agree whole heartedly, the unfortunate part is that I am admin for the outsourcer, I all of the hundreds systems for this client and I know every piece of software that is running and there is nothing installed that could do this.
Would you happen to have any references on how 2000/2003 discovers routes on boot, I have a feeling this is something learned, something like spanning tree.
"Phillip Windell" <@.> wrote in message news:uvQRIEc3GHA.4900@xxxxxxxxxxxxxxxxxxxxxxx
"Brian E" <dirwolf@xxxxxxxxxxxxx> wrote in message news:%

These are three I see consistently and all are valid internal hosts to the
outsourcer.
And is only the systems that live on the same vlan that pix firewall for the
outsourcer sits on , 167.126.101.101 is the internal interface for that
device.
So the question again is how are these OS learning about routes when they
should just send to the dgatway? :-)
------------------------------------


The "outsourcer" needs to get involved. They are probably the cause, or they
have software on your machines that is creating this. It is almost
blatantly obvious that they have at least something to do with this since
everyone of these routes tartgets one of their machines and it only happens
on machine that are on the same segment as their PIX.

I have 4 local segments here with VPN connecting us to about 40 other sites
across the United States and none of my machine do anything similar to this.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com