Adding a persistant route with a specific interface

On Windows Server 2000 and 2003 The interface information for a static route
is changed to another interface after reboot. Anyone aware of a way to force
a static route to persist on a specific interface.

"MPirrone1" <(E-Mail Removed)> wrote in message
news:3468D47D-63CD-42F0-8710-(E-Mail Removed)...
> On Windows Server 2000 and 2003 The interface information for a static
route
> is changed to another interface after reboot. Anyone aware of a way to
force
> a static route to persist on a specific interface.

If you are running RRAS routing, it is MUCH better to put
the routes in the RRAS/IP are using the GUI than it is to
use "route add". (The two do not seem to be well integrated.)

If you wish to use the command line, use NetSh.exe in preference
to route add.

"Route add" should only be used on non-RRAS-server machines.

Even then, NetSh.exe might be better.

Setting the persistent route within RRAS works fine as long as RRAS is
configured and running. netsh only works if RRAS in running. But the server
owner does not want RRAS running on the production server. The route -p add
command works fine until a reboot, any ideas why the interface is assigned to
the route after reboot?



"Herb Martin" wrote:

> "MPirrone1" <(E-Mail Removed)> wrote in message
> news:3468D47D-63CD-42F0-8710-(E-Mail Removed)...
> > On Windows Server 2000 and 2003 The interface information for a static
> route
> > is changed to another interface after reboot. Anyone aware of a way to
> force
> > a static route to persist on a specific interface.
>
> If you are running RRAS routing, it is MUCH better to put
> the routes in the RRAS/IP are using the GUI than it is to
> use "route add". (The two do not seem to be well integrated.)
>
> If you wish to use the command line, use NetSh.exe in preference
> to route add.
>
> "Route add" should only be used on non-RRAS-server machines.
>
> Even then, NetSh.exe might be better.
>
>
>

"MPirrone1" <(E-Mail Removed)> wrote in message
news:6F23EB3C-219C-4C46-8674-(E-Mail Removed)...
> Setting the persistent route within RRAS works fine as long as RRAS is
> configured and running. netsh only works if RRAS in running. But the
server
> owner does not want RRAS running on the production server. The route -p
add
> command works fine until a reboot, any ideas why the interface is assigned
to
> the route after reboot?

While you can route without RRAS, that is the
normal way to do it.

If you don't use RRAS, then you are correct that
"route add" is the method.

In that case, if -p doesn't make the route persistent
then it is probably a bug (and I am pretty sure that
I have seen this too.)