windows server <2012 two NIC

Milan Mudrinic 1 Reputation point
2020-12-08T15:21:26.207+00:00

I'm have idea but im not sure how to implement.

I want windows server >2012 use two NIC.

One is for clients computers (i already make that Network segment with domain isolation trough IPsec) - clients means just access to shares on server and access to MSSQL and MYSQL database. That network use one segment of IP address - for example 192.168.0.x.

I want use second NIC for admin parts of LAN - mean same access as clients plus basic administration of active directory (this no need IPSec).

I want to stop spy clients (guests OS who just connect to LAN - on clients side) to watch IP traffic over admin part of LAN, that's why NIC teaming isn't good option.

If someone has good advice or example how to do that?

P.S. Hyper-V isnt option.

With regards Milan.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
11,933 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Dave Patrick 425.8K Reputation points MVP
    2020-12-08T15:24:54.627+00:00

    You can read on here about this.
    https://support.microsoft.com/en-us/help/175767/how-multiple-adapters-on-the-same-network-are-expected-to-behave

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Milan Mudrinic 1 Reputation point
    2020-12-08T15:31:36.723+00:00

    Yep i already read that (one of first post i read). I know all about problems using two NIC thats why ask question. I dont have clear solution. I make something but without IPSec. When i include IPsec everything is fail.

    With regards.

    0 comments No comments

  3. Dave Patrick 425.8K Reputation points MVP
    2020-12-08T15:37:18.697+00:00

    Multi-homing a domain controller will always cause no end to grief for active directory domain DNS. It isn't recommended to install other applications / roles on a domain controller. Better option is to install active directory domain services on it's own windows instance and application's on another separate instance of windows. If hyper-v isn't an option you may need another hypervisor solution or possibly separate physical boxes to accomplish the task.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments