Windows Server 2016 NIC Teaming - No internet
-
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
I have a server 2016 machine that when I enable NIC teaming (Switch independent) works just fine until I set a static IP on it.
Then it shows the static IP but also assigns it an APIPA address as well for some reason. That is causing issues (obviously) with network connectivity.
In the NIC Teaming area it shows both adapters connected. Both NIC's are not shared with any management adapters (Lights out, DRAC, etc.).
What do you mean by "working fine"? Do you set the IP on the Team or the individual NICs? VLANs involved?
-
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
I have a server 2016 machine that when I enable NIC teaming (Switch independent) works just fine until I set a static IP on it.
Then it shows the static IP but also assigns it an APIPA address as well for some reason. That is causing issues (obviously) with network connectivity.
In the NIC Teaming area it shows both adapters connected. Both NIC's are not shared with any management adapters (Lights out, DRAC, etc.).
What do you mean by "working fine"? Do you set the IP on the Team or the individual NICs? VLANs involved?
Working fine means it can get to the internet, is seen by other computers on the network, etc.
I set a static IP on the team but not on the NIC's. There is no IPv4 on the NIC's after putting them into a team.
-
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
I have a server 2016 machine that when I enable NIC teaming (Switch independent) works just fine until I set a static IP on it.
Then it shows the static IP but also assigns it an APIPA address as well for some reason. That is causing issues (obviously) with network connectivity.
In the NIC Teaming area it shows both adapters connected. Both NIC's are not shared with any management adapters (Lights out, DRAC, etc.).
What do you mean by "working fine"? Do you set the IP on the Team or the individual NICs? VLANs involved?
Working fine means it can get to the internet, is seen by other computers on the network, etc.
I set a static IP on the team but not on the NIC's. There is no IPv4 on the NIC's after putting them into a team.
Correct. I assume it works if it gets an IP by DHCP because you said things went south once you set a static address?
-
@thwr That's exactly right. DHCP is working but once I assign a static it doesn't work. I am using an unused IP address and am putting in the correct subnet, default gateway and DNS.
-
Curious - is Windows Server 2016 installed directly on the hardware?
-
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
-
@dashrender said in Windows Server 2016 NIC Teaming - No internet:
Curious - is Windows Server 2016 installed directly on the hardware?
Yes
-
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Asked that before, he's configuring the team, not the NICs
-
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Yes, that's what I am doing. You can't set static on the adapters.
-
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
@thwr That's exactly right. DHCP is working but once I assign a static it doesn't work. I am using an unused IP address and am putting in the correct subnet, default gateway and DNS.
That's really odd. Any chance you made a mistake / typo?
-
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Asked that before, he's configuring the team, not the NICs
Before it's a team you can mess with the NIC settings, and it effects the Team afterwards (in my experience).
-
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@ccwtech said in Windows Server 2016 NIC Teaming - No internet:
@thwr That's exactly right. DHCP is working but once I assign a static it doesn't work. I am using an unused IP address and am putting in the correct subnet, default gateway and DNS.
That's really odd. Any chance you made a mistake / typo?
You could - and I don't think it makes any difference - try to unplug one cable (or disable one of the physical NICs). Maybe there's something on the switch side like a blocked port or an old VLAN config on that port or...
-
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Asked that before, he's configuring the team, not the NICs
Before it's a team you can mess with the NIC settings, and it effects the Team afterwards (in my experience).
Should not happen because Windows will unbind all IP protocols (v4 and v6) from each member NIC. At least in theory.
-
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Asked that before, he's configuring the team, not the NICs
Before it's a team you can mess with the NIC settings, and it effects the Team afterwards (in my experience).
Should not happen because Windows will unbind all IP protocols (v4 and v6) from each member NIC. At least in theory.
Don't ya just love theory???
-
@dashrender said in Windows Server 2016 NIC Teaming - No internet:
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
@thwr said in Windows Server 2016 NIC Teaming - No internet:
@tim_g said in Windows Server 2016 NIC Teaming - No internet:
Are you setting the NICTeam IP or one of the adapters making the team.
Leave the individual adapters alone, and just set the Team
Asked that before, he's configuring the team, not the NICs
Before it's a team you can mess with the NIC settings, and it effects the Team afterwards (in my experience).
Should not happen because Windows will unbind all IP protocols (v4 and v6) from each member NIC. At least in theory.
Don't ya just love theory???
I'm more on the practical side.
