Need help routing with a quad nic server

Ok lets say I have 2 teamed connections going to my LAN under ip 192.168.16.2 dedicated as the servers LAN address. This server is 2008 ad/exchange.

Ok now I have 2 more ports I can use. One of them I want to connect directly to my mikrotik router which has been designated as 192.168.16.252, and it is connected to my dsl modem.


I want this server to send any traffic needing to go to the internet to that extra port connected to the mikrotik.

How can I go about doing this? Perhaps route add in cmd? Below is a copy and paste of my current static routes...



C:\Users\GRogers>route print
===========================================================================
Interface List
 39 ...84 2b 2b 66 1f 76 ...... BASP Virtual Adapter
 18 ...84 2b 2b 66 1f 7c ...... Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Cl
ient) #4
 16 ...84 2b 2b 66 1f 7a ...... Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Cl
ient) #3
  1 ........................... Software Loopback Interface 1
 10 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 14 ...00 00 00 00 00 00 00 e0  Microsoft ISATAP Adapter
 11 ...00 00 00 00 00 00 00 e0  6TO4 Adapter
 17 ...00 00 00 00 00 00 00 e0  isatap.{B3160FA5-8251-4D5D-AC7C-342FF64A8AA0}
 19 ...00 00 00 00 00 00 00 e0  isatap.{0FA9D9DE-9813-474B-B840-BC0DA781C6D7}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   192.168.16.252     192.168.16.2    266
        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
     192.168.16.0    255.255.255.0         On-link      192.168.16.2    266
     192.168.16.2  255.255.255.255         On-link      192.168.16.2    266
   192.168.16.255  255.255.255.255         On-link      192.168.16.2    266
        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.16.2    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      192.168.16.2    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0   192.168.16.252  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 39    266 fe80::/64                On-link
 39    266 fe80::a14a:41c5:7b91:64e/128
                                    On-link
  1    306 ff00::/8                 On-link
 39    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
E J PopeAsked:
Who is Participating?
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Your default route is going to the Mikrotik already, so this is fine. Your issue is, however, that you will have two 192.168.16.x networks, which is no good. It is best to give the Mikrotik an IP address of another network, like 192.168.17.0/24, and the same for your "new" NIC.
If you cannot change the Mikrotik IP, you can split your current network into two, e.g. 192.168.16.0/29 (current NIC) and 192.168.16.248/29 (new NIC). That allows IPs 1-246 to be on the current network, and 249-254 on the new one (of which you only need 252 and one for the NIC).

Your clients will not be able to use the router, unless they set up 192.168.16.2 as default gateway.

BTW, I'm not certain whether you can directly connect the Mikrotik router to the NIC - Gb NICs can auto-detect cross-over cabling if needed, but 100Mb usually do not and need to be switched, if able to do that at all. You might have to either use a cross-over Ethernet cable or a switch/hub.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.