Persistent Route ignored on XP pro when destination network is unavailable

[Prash]

Hi

I currently have Windows xp Professional workstation(89.2.80.) that
have persistent routes used to connect to a private network(192.168..) through a gateway lying on the same LAN(89.2...).

I add a persistent route to connect to 192.168.0.1

H:\>route add -p 192.168.0.1 mask 255.255.255.255 89.2.40.135 metric 1

H:\>route print
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 43 08 1b f5 ...... Broadcom NetXtreme 57xx Gigabit Controller - P
ket Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 89.2.7.25 89.2.80.207 1
89.0.0.0 255.0.0.0 89.2.80.207 89.2.80.207 20
89.2.80.207 255.255.255.255 127.0.0.1 127.0.0.1 20
89.255.255.255 255.255.255.255 89.2.80.207 89.2.80.207 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.1 255.255.255.255 89.2.40.135 89.2.80.207 1
224.0.0.0 240.0.0.0 89.2.80.207 89.2.80.207 20
255.255.255.255 255.255.255.255 89.2.80.207 89.2.80.207 1
Default Gateway: 89.2.7.25
================================================== =========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.1 255.255.255.255 89.2.40.135 1

This works fine till 192.168.0.1 pc is up.
But when 192... is shut down and we try to ping that machine the gateway The temporary route if changed as shown below.

H:\>route print
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 43 08 1b f5 ...... Broadcom NetXtreme 57xx Gigabit Controller - P
ket Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 89.2.7.25 89.2.80.207 1
89.0.0.0 255.0.0.0 89.2.80.207 89.2.80.207 20
89.2.80.207 255.255.255.255 127.0.0.1 127.0.0.1 20
89.255.255.255 255.255.255.255 89.2.80.207 89.2.80.207 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.1 255.255.255.255 89.2.7.25 89.2.80.207 1
224.0.0.0 240.0.0.0 89.2.80.207 89.2.80.207 20
255.255.255.255 255.255.255.255 89.2.80.207 89.2.80.207 1
Default Gateway: 89.2.7.25
================================================== =========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.1 255.255.255.255 89.2.40.135 1

hence forth we are not able to connect to client 192.168...

Does anyone know why it is defaulting to the default gateway when
the persistent route loses connectivity?

Does anyone know how to prevent this default gateway fall back
(registry or network properties setting)?

thanks in advance
__________________
Prashanth Shetty