2

I currently have a Windows Server 2008R2 box with a single physical NIC. For what I want to do I need two network adaptors in the box. To accomplish this, I added a legacy hardware device "Network Adaptor" and used the Microsoft Loopback Adaptor as the driver.

Now I have two network adaptors:

  1. NIC1 - Physical NIC 10.71.1.3 (network: 10.71.1.0/24)
  2. NIC2 - Virtual (Loopback) NIC 10.71.2.3 (network: 10.71.2.0/24)

My goal is to get NIC2 to piggyback off of NIC1 and be able to ping another server (10.71.2.2) on the same switch (there is only one switch involved in this scenario).

Currently I can ping a server (10.71.1.5) with no issues because it's using the physical NIC as its gateway. But I can't ping 10.71.2.2. I'm guessing because the driver I used (loopback) is creating an isolated network on NIC2.


Please Note: Normally one would just add a secondary IP to NIC1 (the physical NIC). If I did I could ping 10.71.2.2 with no issues (I have tried and it works). But in this case I need two network adaptors and not just a single one to make what I'm trying to do work.

Ideas?


Updated: 4/28/2015 enter image description here

  • I think you need to enable ICS (Internet connection sharing) for the adapters. Also, what's the gateway setting on the loopback adapter, and how does the windows routing table look (open CMD and type "route print")? – Noobixide Apr 26 '15 at 19:27
  • On the loopback adaptor there is no gateway... I don't think there should be as the DEFAULT gateway is still the same gateway as it has always been. As far as the route goes there is a route in the table that manages all traffic on the subnet in question... "192.168.2.0 255.255.255.0 On-link 192.168.2.3 286" – Arvo Bowen Apr 26 '15 at 22:00
  • Never use full uppercase words (except in technical abbreviations), they look as yelling. Never begin all of your words with uppercase, it is bad. There is a close vote for your question, I will try to save it, but probably it won't succeed. – peterh - Reinstate Monica Apr 26 '15 at 23:14
  • A few things... 1) Where could I see these "close votes" and the reason why someone would want to close it. 2) Your edits completely change my question and information! It does not mean what it was intended to mean now... 3) A topic is commonly typed as a "Start case" because it is in fact a "topic". If I was "yelling" I would MAKE THE TOPIC LOOK LIKE THIS. – Arvo Bowen Apr 27 '15 at 1:18
2

You need to add the Routing and Remote Access role to the server and set it up for IP routing.

RRAS will handle the routing from Nic2 to the Nic1 network, but the other servers will need to know the route back to Nic2.

On the other servers you will need

route add 10.71.2.0 mask 255.255.255.0 10.71.1.3

This will let the other servers know to route return traffic via 10.71.1.3

  • I was trying to test this on my windows 7 box before setting it up on my remote server... Is it not possible with win 7? I don't see that feature. – Arvo Bowen Apr 26 '15 at 21:56
  • Windows 7 doesn't have this as a role, but you can enable IP Routing in the registry by going to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\Tcpip\Parameters\IPEnableRouter and changing the 0 to a 1 – ChadH360 Apr 26 '15 at 21:59
  • Nice! After I do that how can I configure it? – Arvo Bowen Apr 26 '15 at 22:01
  • You shouldn't need to do anything else. You can check the routing table with 'route print' and if necessary can add any new routes there. If you need to add a route to a specific interface, you can do so using the route add command and specifying the interface at the end of the command - check route /? from a command prompt for full details. – ChadH360 Apr 26 '15 at 22:27
  • 1
    Whenever you have a server connected to two networks and you want traffic to flow between the networks, you will need to set up RRAS with IP routing. In this case, you won't want network address translation - there are several scenarios where you might want this, but in this case, secure connection between two private networks would be the preferred choice. Once you've got your routing between networks setup, you then need to make sure that devices/clients in the network know how to find each of the networks. This can be done at your default gateway or with the route add command on each device – ChadH360 Apr 28 '15 at 18:03
0

In the end I decided to go a different route (no pun intended). I actually have multiple physical NICs installed and was using them for other things.

I since have learned something new about clustering. I have always in the past dedicated a NIC for the sole purpose of the cluster heartbeat. We my heartbeat always had a single point of failure. That never seemed to be an issue for me but the more I read up on it the more I realized that you don't have to dedicate a NIC just for the heartbeat. There is actually very little traffic that is used for the heartbeat itself and just incase that NIC goes down you should always have another NIC that is allowed to be utilized by the cluster and permitted to send/receive cluster data. This can be found by right clicking then going to "Properties" for each of the "Networks" from within the cluster config itself. Just make sure "Allow cluster network communication..." is ticked. You can allow clicks to if you wish but this is intended for things like VMs in the cluster etc and is not needed for the heartbeat.

So I ended up with 2 NICs with different subnets and both are being used as a heartbeat and that way they each show up as segregated networks in the cluster.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.