Route Table

Hello,

When using "route print" at a Win2000 and Win2003 command prompt, I see many
nonpersistant routes in my route table (in addition to the 7 or so standard
routes everyone has). These routes are removed after reboot, but come back
after the server has been up for some time. In fact, I can tracert to an IP,
and that same IP will immediately get added to my route table.

Is this behavior normal? If so, is there any documentation explaining why
it does this?

Thanks,
Scott

A client machine usually doesn't have a lot of routes. It sends "foreign"
data to its default gateway (or default router). This router then forwards
it on to its destination.

If the router finds there is a better path to the "target" machine, it
sends a ICMP redirect message to the sender, advising it of the better path
and the address of the "first hop" router to use. The sending machine will
then add this route to its routing table.

So the extra routes are probably just optimised paths to particular
machines.

"Scott" <(E-Mail Removed)> wrote in message
news:FA7DFD25-DAB7-4079-A26E-(E-Mail Removed)...
> Hello,
>
> When using "route print" at a Win2000 and Win2003 command prompt, I see
> many
> nonpersistant routes in my route table (in addition to the 7 or so
> standard
> routes everyone has). These routes are removed after reboot, but come
> back
> after the server has been up for some time. In fact, I can tracert to an
> IP,
> and that same IP will immediately get added to my route table.
>
> Is this behavior normal? If so, is there any documentation explaining why
> it does this?
>
> Thanks,
> Scott