Windows Sever is dropping active persistant routes.

look @ routing table below , notice route 10.0.4.2 has been been dropped though listed persistant route.  why happening?  can fix this? 

c:\>route print

ipv4 route table
===========================================================================
interface list
0x1 ........................... ms tcp loopback interface
0x10003 ...00 14 22 1b ed d4 ...... intel(r) pro/1000 mt network connection
===========================================================================
===========================================================================
active routes:
network destination        netmask          gateway       interface  metric
          0.0.0.0          0.0.0.0         10.0.1.1        10.0.1.12     10
        10.0.0.90  255.255.255.255       10.0.1.254        10.0.1.12      1
        10.0.0.92  255.255.255.255       10.0.1.254        10.0.1.12      1
        10.0.0.93  255.255.255.255       10.0.1.254        10.0.1.12      1
        10.0.0.94  255.255.255.255       10.0.1.254        10.0.1.12      1
        10.0.0.95  255.255.255.255       10.0.1.254        10.0.1.12      1
         10.0.1.0    255.255.255.0        10.0.1.12        10.0.1.12     10
        10.0.1.12  255.255.255.255        127.0.0.1        127.0.0.1     10
   10.255.255.255  255.255.255.255        10.0.1.12        10.0.1.12     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
        224.0.0.0        240.0.0.0        10.0.1.12        10.0.1.12     10
  255.255.255.255  255.255.255.255        10.0.1.12        10.0.1.12      1
default gateway:          10.0.1.1
===========================================================================
persistent routes:
  network address          netmask  gateway address  metric
        10.0.0.90  255.255.255.255       10.0.1.254       1
        10.0.0.91  255.255.255.255       10.0.1.254       1
        10.0.0.92  255.255.255.255       10.0.1.254       1
        10.0.0.93  255.255.255.255       10.0.1.254       1
        10.0.0.94  255.255.255.255       10.0.1.254       1
        10.0.0.95  255.255.255.255       10.0.1.254       1
         10.0.4.2  255.255.255.255       10.0.1.254       1  <---------------------route here not in active table?

this happening on several of servers , depend on these routes critical find solution. this route has constant flow of traffic well.  there rhyme or reason this.  in advanced help.

chad

 

this kb applies windows cluster, same sort of thing may

happening:

 

http://support.microsoft.com/kb/2161341

 

although route has been added, not listed active since

interface parameter not used when adding persistent route. have

you tried re-adding route using interface id (in case

0x10003 listed in first part of table route

print command)

 

 

 

---

-- mike burr

Windows Server  >  Windows Server General Forum