Setting Up VLANS within a barebones Microsoft Windows Server 2016

[90Ninety]

I have been 'playing' with VLANS within a physical lab environment for some time ( several cisco switches , routers and computers) . I am able to set up trunks between switches and routers , this I understand .

However I want some clarification on how to configure Microsoft server with multiple DHCP scopes . My understanding is:

• When deploying Microsoft server with multiple DHCP scopes over different networks ,the server will need multiple VLAN Interfaces , these can be physical or logical . When there is several physical NIC interfaces , each of the LAN ports connected should be connected to the switch , one for each subnet/Vlan .
• Logical virtual NICs Can also be used , If using one only one Physical NIC ,VLAN interfaces have to be created within a vendor specific software application ( e.g; Intel/Realtek/Dell/White-label ) and not part of the stock operating system
• NIC teaming is not needed for VLANS , and is only required for fail-over and load balancing .

I have been trying for a few weeks to get computers over several VLANS authenticated by the server . My current desktop server ( re-purposed Dell Desktop ) with Realtek RTL8168E Ethernet Controller has its own Software application called 'Realtek Ethernet Diagnostic' where VLANS are created , this works with the DHCP server , though its intermittent and not officially supported by Windows Server . I am planning on finding a more suitable PCIE Ethernet Controller , if my understanding is correct ?

Continue reading...