Routing table problem

Hello everybody,

I'm facing some routing table problem with XP O.S.

I'm using 192.168.x.x/255.255.248.0 network set. 8.0 for the secured server
leg, 24.0 for published server leg, and XP clients have 16.0 leg. 0.0 leg is
used for internet access.

The connection between legs are 0.0-ISA1, ISA1-24.0, ISA1-16.0, 24.0-ISA2
and ISA2-8.0

I haven't configured all the global routing rules yet, i'm just testing the
configuration. Moved my xp terminal to 24.0 network by adding secondary
configuration to my nic and added the routing rule to establish a connection
to 8.0 leg which is routed from configured ISA2.

"route add 192.168.8.0 mask 255.255.248.0 192.168.24.254" this is the
natural route entry for my xp terminal, right? And thus, i can connect any
service running any computer in 8.0 network without any problems.

The problem is: when i turn off my terminal, or hibernate ( or just a
timeout i didn't test that yet ) and power back, the route table changes...
It returns to its original state where the rule to connect 8.0 network isn't
exist. Every time i open my computer i have to readd that rule over and over
again...

So, please tell me what's the explanation to this? Am i missing anything? Is
there something i don't know about Windows XP's routing table principles?

Thanks a lot...

"Hasan MANZAK" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hello everybody,
>
> I'm facing some routing table problem with XP O.S.
>
> I'm using 192.168.x.x/255.255.248.0 network set. 8.0 for the secured
> server leg, 24.0 for published server leg, and XP clients have 16.0 leg.
> 0.0 leg is used for internet access.
>
> The connection between legs are 0.0-ISA1, ISA1-24.0, ISA1-16.0, 24.0-ISA2
> and ISA2-8.0
>
> I haven't configured all the global routing rules yet, i'm just testing
> the configuration. Moved my xp terminal to 24.0 network by adding
> secondary configuration to my nic and added the routing rule to establish
> a connection to 8.0 leg which is routed from configured ISA2.
>
> "route add 192.168.8.0 mask 255.255.248.0 192.168.24.254" this is the
> natural route entry for my xp terminal, right? And thus, i can connect any
> service running any computer in 8.0 network without any problems.
>
> The problem is: when i turn off my terminal, or hibernate ( or just a
> timeout i didn't test that yet ) and power back, the route table
> changes... It returns to its original state where the rule to connect 8.0
> network isn't exist. Every time i open my computer i have to readd that
> rule over and over again...
>
> So, please tell me what's the explanation to this? Am i missing anything?
> Is there something i don't know about Windows XP's routing table
> principles?
>
> Thanks a lot...
>


Sounds like a complicated XP box. :-)

The only thing I can think of is you may have forgotten to use the
persistent switch (-p) in the route command:
route add -p 192.168.8.0 mask 255.255.248.0 192.168.24.254

If you want it to clear all previous routes, use the -f in conjunction with
the above command.
route add -f -p 192.168.8.0 mask 255.255.248.0 192.168.24.254

Run route /? for available info on the switches.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Yes... I really had forgotten to use p switch ) Damn! )

"Ace Fekay [MCT]" <(E-Mail Removed)>, haber iletisinde þunlarý
yazdý:(E-Mail Removed)...
> "Hasan MANZAK" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hello everybody,
>>
>> I'm facing some routing table problem with XP O.S.
>>
>> I'm using 192.168.x.x/255.255.248.0 network set. 8.0 for the secured
>> server leg, 24.0 for published server leg, and XP clients have 16.0 leg.
>> 0.0 leg is used for internet access.
>>
>> The connection between legs are 0.0-ISA1, ISA1-24.0, ISA1-16.0, 24.0-ISA2
>> and ISA2-8.0
>>
>> I haven't configured all the global routing rules yet, i'm just testing
>> the configuration. Moved my xp terminal to 24.0 network by adding
>> secondary configuration to my nic and added the routing rule to establish
>> a connection to 8.0 leg which is routed from configured ISA2.
>>
>> "route add 192.168.8.0 mask 255.255.248.0 192.168.24.254" this is the
>> natural route entry for my xp terminal, right? And thus, i can connect
>> any service running any computer in 8.0 network without any problems.
>>
>> The problem is: when i turn off my terminal, or hibernate ( or just a
>> timeout i didn't test that yet ) and power back, the route table
>> changes... It returns to its original state where the rule to connect 8.0
>> network isn't exist. Every time i open my computer i have to readd that
>> rule over and over again...
>>
>> So, please tell me what's the explanation to this? Am i missing anything?
>> Is there something i don't know about Windows XP's routing table
>> principles?
>>
>> Thanks a lot...
>>
>
>
> Sounds like a complicated XP box. :-)
>
> The only thing I can think of is you may have forgotten to use the
> persistent switch (-p) in the route command:
> route add -p 192.168.8.0 mask 255.255.248.0 192.168.24.254
>
> If you want it to clear all previous routes, use the -f in conjunction
> with the above command.
> route add -f -p 192.168.8.0 mask 255.255.248.0 192.168.24.254
>
> Run route /? for available info on the switches.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit
> among responding engineers, and to help others benefit from your
> resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>

"Hasan MANZAK" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...


Well, glad to see it was an easy solution! :-)

Cheers!

Ace


> Yes... I really had forgotten to use p switch ) Damn! )
>
> "Ace Fekay [MCT]" <(E-Mail Removed)>, haber iletisinde
> þunlarý yazdý:(E-Mail Removed)...
>> "Hasan MANZAK" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Hello everybody,
>>>
>>> I'm facing some routing table problem with XP O.S.
>>>
>>> I'm using 192.168.x.x/255.255.248.0 network set. 8.0 for the secured
>>> server leg, 24.0 for published server leg, and XP clients have 16.0 leg.
>>> 0.0 leg is used for internet access.
>>>
>>> The connection between legs are 0.0-ISA1, ISA1-24.0, ISA1-16.0,
>>> 24.0-ISA2 and ISA2-8.0
>>>
>>> I haven't configured all the global routing rules yet, i'm just testing
>>> the configuration. Moved my xp terminal to 24.0 network by adding
>>> secondary configuration to my nic and added the routing rule to
>>> establish a connection to 8.0 leg which is routed from configured ISA2.
>>>
>>> "route add 192.168.8.0 mask 255.255.248.0 192.168.24.254" this is the
>>> natural route entry for my xp terminal, right? And thus, i can connect
>>> any service running any computer in 8.0 network without any problems.
>>>
>>> The problem is: when i turn off my terminal, or hibernate ( or just a
>>> timeout i didn't test that yet ) and power back, the route table
>>> changes... It returns to its original state where the rule to connect
>>> 8.0 network isn't exist. Every time i open my computer i have to readd
>>> that rule over and over again...
>>>
>>> So, please tell me what's the explanation to this? Am i missing
>>> anything? Is there something i don't know about Windows XP's routing
>>> table principles?
>>>
>>> Thanks a lot...
>>>
>>
>>
>> Sounds like a complicated XP box. :-)
>>
>> The only thing I can think of is you may have forgotten to use the
>> persistent switch (-p) in the route command:
>> route add -p 192.168.8.0 mask 255.255.248.0 192.168.24.254
>>
>> If you want it to clear all previous routes, use the -f in conjunction
>> with the above command.
>> route add -f -p 192.168.8.0 mask 255.255.248.0 192.168.24.254
>>
>> Run route /? for available info on the switches.
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among responding engineers, and to help others benefit from your
>> resolution.
>>
>> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
>> 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>>
>> For urgent issues, please contact Microsoft PSS directly. Please check
>> http://support.microsoft.com for regional support phone numbers.
>>
>>
>>
>
>