The ROUTE command in Windows Server 2008 and later and Windows 7


my company  preparing our anual hurricane season disaster drill weekend , dusting off procedures test our dr systems. in past, have tested prior test using route add command locally on systems create static routes networks know down during our test simulate conditions during test. during tests, connections physically broken.

this first time have done since have migrated our desktops windows 7 , of our servers server 2008r2. apparently ms change way static routes handled in newer os. here did before:

route add -p 172.27.0.0 mask 255.255.0.0 127.0.0.1 metric 20

does not work.

after doing basic research, found there called built-in loopback interface, , command this

route add -p 172.27.0.0 mask 255.255.0.0 "the pc or server's default gateway" if 1 metric 20

this indeed work degree. can no longer ping, , other communication fails, but, when go start/run can still unc mapping device on networks. makes no sense. can manually map drive device on 1 of these networks cannot ping!

how overcome this?

hi,


post , sorry delay.


however, please let know why need add static route. can see, there has following route entries in our route table default.


network destination        netmask          gateway       interface  metric

127.0.0.0                      255.0.0.0          on-link         127.0.0.1    306

127.0.0.1                  255.255.255.255     on-link         127.0.0.1    306


anyway, can try disable windows firewall , try again.


hope helps.


jeremy wu
technet community support



Windows Server  >  Platform Networking



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file