Windows Server 2008 route command issue

I have (2) network adapters on a Windows Server 2008 as a virtual machine on ESX 4.0.  The first adapter is tied to our LAN (192.168.1.X) and the second is for a separate network (10.0.X.X), intended to be used for some off-site data replication to a satellite office.  

In attempting to add a route by the following command:

ROUTE ADD 10.0.2.0 MASK 255.255.255.0 10.0.1.1 METRIC 8 IF 12

Looking at the attached routeprint.txt file, you'll see that the interface is reflected as "c" instead of 10.0.1.1.  I have successfully added this route to other servers on this network and the corresponding routes on servers in the satellite office and both sides can talk to teach other.

Why is the interface showing as "c" instead of the address it's supposed to be (10.0.1.2)?
routeprint.txt
LVL 3
djhathAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Pradeep DubeyConsultantCommented:
route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3 IF 2
                   destination^      ^mask     ^gateway     metric^    ^Interface

are you sure the last option Interface is 12 ?
0
djhathAuthor Commented:
I found that if I delete the route and add it without defining the metric or the specific interface, it chooses the first network adapter on the 192.168.1.x network as its adapter, which what I don't want.  I have attached an updated route print of the routing table with illustrating the result of adding the command as I just described.
routeprint2.txt
0
djhathAuthor Commented:
Hi,

Yes.  This is a list of the adapters from the route print command:

===========================================================================
Interface List
 16...02 50 56 82 00 28 ......Microsoft Failover Cluster Virtual Adapter
 12...00 50 56 82 00 29 ......vmxnet3 Ethernet Adapter #2
 10...00 50 56 82 00 28 ......vmxnet3 Ethernet Adapter
  1...........................Software Loopback Interface 1
 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

The 192.168.1.x adapter is the "vmxnet3 Ethernet Adapter", interface 10.  Interface 12 is the "vmxnet3 Ethernet Adapter #2" with the 10.0.1.2 IP address assigned to it.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Cliff GaliherCommented:
I'm noticing that there are other entries in your routing table with "c" as the interface, and all of those routing entries are APIPA based. Looks to me like your 10.x.x.x interface is not actually getting that IP address and is generating an APIPA address. So when you attempt to define your route on that interface, and the gateway is not in the subnet it expects, it is barfing up.  Fix your APIPA issue (either go static or check your DHCP settings) and I think you'll see your situation clear up.
0
djhathAuthor Commented:
Thank you for the input, Cgaliher.  The 10.x.x.x address on that interface is assigned as a static IP.
0
Pradeep DubeyConsultantCommented:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.2     192.168.1.22    261
         10.0.2.0    255.255.255.0         10.0.1.1                c      8

see the metric you provided 3 and its getting 8. add the route again and check once.
0
Cliff GaliherCommented:
I would change it then, and then change it back. Or disable the adapter and re-enable it. Or, worst case, remove it altogether and then let it redetect.

Because not only do I see APIPA entries, but I *don't* see any of the auto-generated entries that would normally be associated with a NIC with a properly assigned IP address.

For example, if you look at your output, you'll see that a route for your 192.168.x.x address (actually addresses, as I spotted two off the cuff), with a subnet of 255.255.255.255 are created automatically by windows just by assigning that IP address to the NIC.

If the IP address was being properly assigned, you should have a few auto-generated routes that windows just ...creates. And you don't. That tells me the TCP stack isn't loading for that NIC. That most often is caused by corrupt data. And the various suggestions above should help replace all the various registry points where that corruption may be hiding.

-Cliff
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
djhathAuthor Commented:
Cliff - I think the idea of removing the adapter and re-adding it sounds like the right move. Unfortunately, I'm in the middle of doing some data migration over the primary interface, so I'll have to wait until that's done so that I can shut down the VM and remove the adapter and re-add.  I will update the question once I've done that to see if that does the trick.
0
Ernie GronblomCloud Systems EngineerCommented:
Perhaps a look at the 'ipconfig' output will help to shed some light on the address issue?

Ernie
0
djhathAuthor Commented:
Here is the output from "ipconfig /all"

Windows IP Configuration

   Host Name . . . . . . . . . . . . : CEAMAIL3
   Primary Dns Suffix  . . . . . . . : intranet.ceadvisors.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : intranet.ceadvisors.com

Ethernet adapter Local Area Connection* 9:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapte
r
   Physical Address. . . . . . . . . : 02-50-56-82-00-28
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ce1:6319:62aa:175f%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 169.254.2.63(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 386027606
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-7F-6F-B0-00-50-56-82-00-28

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter #2
   Physical Address. . . . . . . . . : 00-50-56-82-00-29
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.0.1.2(Duplicate)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Autoconfiguration IPv4 Address. . : 169.254.217.224(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
   Physical Address. . . . . . . . . : 00-50-56-82-00-28
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5999:42b3:d067:5f08%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.22(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.1.61(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.2
   DHCPv6 IAID . . . . . . . . . . . : 234901590
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-7F-6F-B0-00-50-56-82-00-28

   DNS Servers . . . . . . . . . . . : 192.168.1.14
                                       192.168.1.13
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{F115C8CD-43EF-4237-980F-71F7B226B210}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{5030551B-23EE-429B-B2A6-5BEBB0F0F987}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{DCFE2CD1-0238-437F-9F6C-0E6D79CCCE7C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Upon inspection, I'm uncertain as to what the 169. address on the 'autoconfiguration' is all about. I looked at the 'advanced' settings beyond the IP address and everything looks right to me.
0
Cliff GaliherCommented:
Caused because another machine on that network has 10.0.1.2 already and thus windows is detecting it as a duplicate...which is also indicated in that output.
0
djhathAuthor Commented:
That seems to be the issue.  I changed the IP to 10.0.1.5, deleted the existing routes for the 10.x.x.x network, re-added them and now have the following routing table:

===========================================================================
Interface List
 16...02 50 56 82 00 28 ......Microsoft Failover Cluster Virtual Adapter
 12...00 50 56 82 00 29 ......vmxnet3 Ethernet Adapter #2
 10...00 50 56 82 00 28 ......vmxnet3 Ethernet Adapter
  1...........................Software Loopback Interface 1
 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.2     192.168.1.22    261
         10.0.1.5  255.255.255.255         On-link          10.0.1.5    261
         10.0.2.0    255.255.255.0         10.0.1.1         10.0.1.5      8
        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
      169.254.0.0      255.255.0.0         On-link      169.254.2.63    261
     169.254.2.63  255.255.255.255         On-link      169.254.2.63    261
  169.254.255.255  255.255.255.255         On-link      169.254.2.63    261
      192.168.1.0    255.255.255.0         On-link      192.168.1.22    261
     192.168.1.22  255.255.255.255         On-link      192.168.1.22    261
     192.168.1.61  255.255.255.255         On-link      192.168.1.22    261
     192.168.1.71  255.255.255.255         On-link      192.168.1.22    261
    192.168.1.255  255.255.255.255         On-link      192.168.1.22    261
        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      192.168.1.22    261
        224.0.0.0        240.0.0.0         On-link          10.0.1.5    261
        224.0.0.0        240.0.0.0         On-link      169.254.2.63    261
  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      192.168.1.22    261
  255.255.255.255  255.255.255.255         On-link          10.0.1.5    261
  255.255.255.255  255.255.255.255         On-link      169.254.2.63    261
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.2  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 10    261 fe80::/64                On-link
 16    261 fe80::/64                On-link
 16    261 fe80::ce1:6319:62aa:175f/128
                                    On-link
 10    261 fe80::5999:42b3:d067:5f08/128
                                    On-link
  1    306 ff00::/8                 On-link
 10    261 ff00::/8                 On-link
 16    261 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

Interestingly, I can ping across to all hosts on the 10.0.2.x network (in the satellite office), but cannot ping the other hosts that are on the 10.0.1.x network, nor the gateway over which it is traveling.
0
Cliff GaliherCommented:
Maybe the gateway address is wrong? Could explain both the ping issue and the address conflict.
0
Ernie GronblomCloud Systems EngineerCommented:
If the gateway address was wrong it wouldn't pick up the 10.0.2.x hosts.  There is a missing network route which should have been added by default:
10.0.1.0 with gateway 10.0.1.5

Ernie
0
djhathAuthor Commented:
Ernie - Is that a route I should try to add manually or am I back to when I have a chance (soon, hopefully), powering off the server, removing the NIC and re-adding it?
0
Cliff GaliherCommented:
Indeed that is correct about the gateway. I initially misread the issue and thought 10.0.2.x could *not* be pinged. Funny how "can" and "can't" makes such a difference.

Anyways, after that gaffe I went and more carefully read the latest response and have come up with multiple concerns.

First, I am a bit confused about the network topology. You state "but cannot ping the other hosts that are on the 10.0.1.x network, nor the gateway over which it is traveling." Ping packets to hosts that are on 10.0.1.x shouldn't be travelling over *any* gateway, if the ipconfig you posted is accurate, the 10.0.1.2 to 10.0.1.5 change not withstanding. The subnet indicates all traffic is local. So your statement about not seeing pings that should be local to the network on the gateway seems...ambiguous.

Secondly, I am still seeing APIPA routes. Which, combined with Ernie's observation of the missing 10.0.1.0 route, leads me to think you still have NIC issues.

Finally, I notice in your ipconfig, there is a failover cluster adapter which seems completely unconfigured. If failover clustering was enabled and misconfigured, that would certainly explain a lot. Again, this is something I missed the first time, as I specifically scrolled to the existing adapter in question last time to see the 10.0.1.0 configuration. But it sticks out like a sore thumb now that I've gone back and taken a broader look at all of your output.

In particular, if failover clustering is botched, simply removing and redetecting the adapter won't solve the problem, as the root cause is not the NIC itself, but with a feature that was enabled and not properly implemented. If it were me, that's where I'd start.
0
djhathAuthor Commented:
Removing the adapter and re-adding it did the trick.  The route was added and I can now get to the 10.0.2.x subnet without issue.  Thank you all for your help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.