Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I just updated the route tables due to a mistake on my part.

I am working on getting networking working correctly on a cluster of 14 virtual servers at a customer site. 11 of them work fine for routing and 3 don't work correctly for their administrative network (172.28.56.0). All are running Windows Web Server 2008R2.

Default gateway is set on the production network (172.28.58.0) and not on the administrative network (handled with persistent static routes).

On a working server, route print gives me the following (MACs redacted)

===========================================================================
Interface List
 11...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection
 13...XX XX XX XX XX XX00 0c 29 85 b2 98 ......Intel(R) PRO/1000 MT Network Connection #2
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table

===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
           0.0.0.0         0.0.0.0      172.28.58.1    172.28.58.11     266
        10.18.1.22 255.255.255.255      172.28.58.1    172.28.58.11      11
         10.32.0.0     255.255.0.0      172.28.56.1   172.28.56.201      11
         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
   127.255.255.255 255.255.255.255          On-link       127.0.0.1     306
      172.28.34.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.42.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.56.0    255.255.255.0          On-link   172.28.56.201     266
      172.28.56.0    255.255.255.0      172.28.56.1   172.28.56.201      11
    172.28.56.201  255.255.255.255          On-link   172.28.56.201     266
    172.28.56.255  255.255.255.255          On-link   172.28.56.201     266
      172.28.58.0  255.255.255.224          On-link    172.28.58.11     266
      172.28.58.0  255.255.255.224      172.28.58.1    172.28.58.11      11
      172.28.58.1  255.255.255.255      172.28.58.1    172.28.58.11      11
     172.28.58.11  255.255.255.255          On-link    172.28.58.11     266
     172.28.58.31  255.255.255.255          On-link    172.28.58.11     266
      172.28.60.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      172.28.63.0    255.255.255.0      172.28.56.1   172.28.56.201      11
      192.168.0.0      255.255.0.0      172.28.56.1   172.28.56.201      11
        224.0.0.0        240.0.0.0          On-link       127.0.0.1     306
        224.0.0.0        240.0.0.0          On-link   172.28.56.201     266
        224.0.0.0        240.0.0.0          On-link    172.28.58.11     266
  255.255.255.255  255.255.255.255          On-link       127.0.0.1     306
  255.255.255.255  255.255.255.255          On-link   172.28.56.201     266
  255.255.255.255  255.255.255.255          On-link    172.28.58.11     266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      172.28.56.0    255.255.255.0      172.28.56.1       1
      172.28.63.0    255.255.255.0      172.28.56.1       1
      192.168.0.0      255.255.0.0      172.28.56.1       1
      172.28.60.0    255.255.255.0      172.28.56.1       1
        10.32.0.0      255.255.0.0      172.28.56.1       1
      172.28.34.0    255.255.255.0      172.28.56.1       1
      172.28.42.0    255.255.255.0      172.28.56.1       1
          0.0.0.0          0.0.0.0      172.28.58.1  Default
===========================================================================

IPv6 Route Table

===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

On one of the non-working server, route print gives me the following (MACs redacted)

===========================================================================
Interface List
 11...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection
 13...XX XX XX XX XX XX ......Intel(R) PRO/1000 MT Network Connection #2
  1...........................Software Loopback Interface 1
 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table

===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
           0.0.0.0         0.0.0.0      172.28.58.1    172.28.58.21     266
         10.32.0.0     255.255.0.0      172.28.56.1   172.28.56.211      11
         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
   127.255.255.255 255.255.255.255          On-link       127.0.0.1     306
       172.28.34.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.42.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.56.0   255.255.255.0      172.28.56.1   172.28.56.211      11
     172.28.56.211 255.255.255.255          On-link   172.28.56.211     266
       172.28.58.0   255.255.255.0      172.28.58.1    172.28.58.21      11
       172.28.58.0 255.255.255.224          On-link    172.28.58.21     266
      172.28.58.21 255.255.255.255          On-link    172.28.58.21     266
      172.28.58.31 255.255.255.255          On-link    172.28.58.21     266
       172.28.60.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       172.28.63.0   255.255.255.0      172.28.56.1   172.28.56.211      11
       192.168.0.0     255.255.0.0      172.28.56.1   172.28.56.211      11
         224.0.0.0       240.0.0.0          On-link       127.0.0.1     306
         224.0.0.0       240.0.0.0          On-link   172.28.56.211     266
         224.0.0.0       240.0.0.0          On-link    172.28.58.21     266
   255.255.255.255 255.255.255.255          On-link       127.0.0.1      06
   255.255.255.255 255.255.255.255          On-link   172.28.56.211     266
   255.255.255.255 255.255.255.255          On-link    172.28.58.21     266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      172.28.56.0    255.255.255.0      172.28.56.1       1
      172.28.60.0    255.255.255.0      172.28.56.1       1
      172.28.63.0    255.255.255.0      172.28.56.1       1
      172.28.34.0    255.255.255.0      172.28.56.1       1
      172.28.42.0    255.255.255.0      172.28.56.1       1
      192.168.0.0      255.255.0.0      172.28.56.1       1
        10.32.0.0      255.255.0.0      172.28.56.1       1
          0.0.0.0          0.0.0.0      172.28.58.1  Default
      172.28.58.0    255.255.255.0      172.28.58.1       1
===========================================================================

IPv6 Route Table

===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  1    306 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

I am at a complete loss why the non-working servers have no On-link route for 172.28.56.0. Does anyone have any suggestions on what I should be looking at to figure this out? Also, I do have "physical" access to the console if needed through vSphere Client.

share|improve this question

closed as off topic by Darth Android, 8088, Randolph West, Nifle, Diogo Sep 15 '12 at 23:25

Questions on Super User are expected to relate to computer software or computer hardware within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Welcome to Super User! While this isn't explicitly off-topic here, there's a good chance you'll get better results at Server Fault, our sister-site for professional server administrators. There's no need to cross-post your question there - if a moderator or several other users agree, the question will be migrated for you. –  Darth Android Sep 14 '12 at 15:15
    
As no one else seems to be voting to move it and I need help w/ this ASAP, I posted on Server Fault. –  smccloud Sep 14 '12 at 17:33
    
Please DO NOT CROSSPOST. –  user3463 Sep 14 '12 at 17:34
    
Randolph, I would not have but sadly until I said I did only Darth Android offered any sort of help. –  smccloud Sep 14 '12 at 17:37
    
@smccloud For future reference, the ideal solution would be to simply flag your own post for moderator attention (assuming you can, I'm not sure if there's a rep requirement for that), or simply wait. It's not that it's a bad question for Super User -- There's a lot of overlap between the communities -- But in the long run, it simply fits better on Server Fault. That all being said, I hope you get the issue worked out! –  Darth Android Sep 14 '12 at 19:41