Problem - After Setting up NIC Teaming on Server 2012 the team does not identify the network as a Doman Network.

OS- Windows Server 2012 Datacenter (Fully Patched)

Teaming Mode :  LACP

Load Balancing Mode:  Address Hash

Switch Config:  Cisco 3560X

interface Port-channel15
 switchport mode access

interface GigabitEthernet0/2
 switchport mode access
 spanning-tree portfast
 channel-group 15 mode active

interface GigabitEthernet0/1
 switchport mode access
 spanning-tree portfast
 channel-group 15 mode active

Everything is working ok with the Domain/network.  IP Config is right, dns points to same AD Dns servers as everything else.

Any Ideas?

This is the log from the Switch.  Looks like LACP is working fine.

018312: Jan 25 11:29:53.683: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
018313: Jan 25 11:29:54.589: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
018314: Jan 25 11:29:54.682: %LINK-3-UPDOWN: Interface Port-channel15, changed state to up
018315: Jan 25 11:29:55.688: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel15, changed state to up

I don't see any LACP configured on the switch.

Check this: http://www.cisco.com/en/US/docs/switches/lan/catalyst3750x_3560x/software/release/12.2_53_se/configuration/guide/swethchl.html#wp1275680

Don't use the Port Aggregation Protocol (PAgP) - this is only switch related.

• Edited by Torsten Jahnke Friday, January 25, 2013 8:56 PM
• Proposed as answer by Nick Gu - MSFTMicrosoft contingent staff, Moderator Sunday, February 03, 2013 2:57 PM
• Marked as answer by Nick Gu - MSFTMicrosoft contingent staff, Moderator Tuesday, February 05, 2013 9:29 AM

Hi,

Your problem sounds like the issue I had when setting up teaming on a domain joined Windows Server 2012 box. If your problem is the same as mine, the workaround is to restart the Network Location Awareness Service and afterwards your computer will show as being back on the domain network. This will stick until the next reboot when you'll have to restart the service again to return to domain joined network status.

Note, when you restart the Network Location Awareness service, it will also want to restart the Network List Service. No problem - let it do this. Also, if you try to restart Network Location Awareness too soon after booting up it will fail with an error message (I can't remember what it said). Just wait about 60 seconds and try again and it'll work.

As information, the problem went away after I promoted the Windows 2012 Server with the issue to a DC. I have no idea what causes the problem in the first place on a domain joined Server 2012 box or why making the computer a DC fixes it (or why restarting Network Location Awareness is a workaround).

Hope this helps.

Steve W.

• Proposed as answer by Nick Gu - MSFTMicrosoft contingent staff, Moderator Sunday, February 03, 2013 2:58 PM
• Marked as answer by Nick Gu - MSFTMicrosoft contingent staff, Moderator Tuesday, February 05, 2013 9:29 AM

Hi we have the same problem on just installed Windows 2012 R2 servers, using delayed start on the Location Awareness service works on one of the servers, but not the other... 

So i guess that my real question is - when will MS Release a hotfix for this general problem ? 

We use HP Servers with 4 netcards on the motherboard and Cisco switches (and they are configured for this).

Yours Erling B. Kjeldsen

Hi, we had the same problem with all of our Windows 2012 R2 servers which were using teamed NICS.  We originally had each port on the Cisco switch configured to use Portfast however this resulted in the same problem.  We then configured Portfast on the Portchannel itself which appears to have alleviated the problem for us.

Regards,

Daniel T.

Steve W. got half of it, the issue is with Network Location Awareness but restarting the service is just sidestepping a symptom of the real problem.  The root of this problem in on your switch.  Set Spanning Tree to fastmode (or Edge Port) for the port you are using or if it is a nic team set it for each port individually and then also for the entire nic team.  This is based on this info here:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/6478e2d9-9fa3-4dff-9259-e8e2a2d8cde8/unidentified-network-with-server-2012-r2-domain-nic-teaming?forum=winserver8gen

• Proposed as answer by Samuel S Miller 12 hours 43 minutes ago