This server has two NIC, the persistent routes are added for the Layer 3 switch. When the server is rebooted, the server is not able to ping the gateway. Found the persistent routes when we do a route print after the reboot. only if we remove and add the persistent route then we are able to ping the gateway. What could be the issue.

Hi Thanks for posting here. Have you tried disable the NIC that NOT connected with switch first and try again ? would this issue persist? And what’s the metric value you set for persistent routes? Please post full route table here for further investigation . Thanks Tiger LiPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi I cannot disable the NIC since both are in use. following are the route table in the server: C:\Documents and Settings\admin>route print IPv4 Route Table =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x10003 ...00 23 7d ea d1 a6 ...... HP NC382i DP Multifunction Gigabit Server Ad apter #2 0x10004 ...00 23 7d ea d1 a4 ...... HP NC382i DP Multifunction Gigabit Server Ad apter =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.91.128.1 10.91.128.231 20 10.91.128.0 255.255.255.0 10.91.128.231 10.91.128.231 20 10.91.128.0 255.255.255.0 10.91.128.233 10.91.128.233 10 10.91.128.0 255.255.255.0 10.91.128.129 10.91.128.231 1 10.91.128.231 255.255.255.255 127.0.0.1 127.0.0.1 20 10.91.128.233 255.255.255.255 127.0.0.1 127.0.0.1 10 10.255.255.255 255.255.255.255 10.91.128.231 10.91.128.231 20 10.255.255.255 255.255.255.255 10.91.128.233 10.91.128.233 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.91.128.231 10.91.128.231 20 224.0.0.0 240.0.0.0 10.91.128.233 10.91.128.233 10 255.255.255.255 255.255.255.255 10.91.128.231 10.91.128.231 1 255.255.255.255 255.255.255.255 10.91.128.233 10.91.128.233 1 Default Gateway: 10.91.128.1 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 10.91.128.0 255.255.255.0 10.91.128.129 1

=========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.91.128.1 10.91.128.231 20 10.91.128.0 255.255.255.0 10.91.128.231 10.91.128.231 20 10.91.128.0 255.255.255.0 10.91.128.233 10.91.128.233 10 10.91.128.0 255.255.255.0 10.91.128.129 10.91.128.231 1 Default Gateway: 10.91.128.1 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 10.91.128.0 255.255.255.0 10.91.128.129 1 Hi, Thanks for update. Seems the IP address that set for each NIC on your host is in same subnet, and this is really not recommend ,because it will cause routing mess, I think this is the root cause of issue. You may following the suggestions in the article below to modify network settings for your host: Default Gateway Configuration for Multihomed Computers http://support.microsoft.com/kb/157025 Thanks. Tiger Li Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.