Share via

"Unidentified network" with Server 2012 R2 - Domain & NIC teaming

Question

Saturday, December 21, 2013 6:17 PM | 1 vote

Hello,

I have some trouble with network profile on my Windows Server 2012 R2 system. 

The server has four NICs, three of them are joined in a team. The fourth NIC is used as "management port". The server is joined to a domain and runs Hyper-V role. The Team-NIC is used as network interface for Hyper-V only! It isn't shared with the host system for common use. 

If I reboot the server, the management NIC will change to the network profile "public" with "Unidentified network" shown in the network center. To re-recognize the domain profile I have to turn off and on the IPv4 or IPv6 module in the settings of this port or restart the service "NLA (Network Location Awareness)". Then it recognize the domain. If I reboot the server, I have to do the same thing again.

Is this some kind of bug with teaming or something else? The network adapter is not included in the team, so I'm not sure if there is any connection between them for this problem. I already tried to set the start of the service NLA to "delayed start" (I read this in another topic) but this didn't help either!

I hope somebody can help me. Thank you very much!

Greets,

Burak

All replies (9)

Saturday, December 21, 2013 9:12 PM

Does your managemet work after restart? If you do not restart NLA, what happen after some time (next day)?

IMHO the functionality is primary and "automatic recognition" is secondary and work with some delay. Are all servers including host server members of domain od at least are all servers registered in domain DNS?

Regards

Milos

Monday, December 23, 2013 5:55 PM

Hello,

it still stays on "unidentified network" after I wait for some hours or one day, nothing changes here. The server is member server of the domain and it is registered in the domain DNS. Everything looks fine here.

I am talking about this problem in the german section to get more information about this. If this help someone, here is the link: "Nicht identifizertes Netzwerk"

I tried something more and I recognized, if I use static link aggregation mode or switch independent mode, it just works. Only if I use "LACP" it does not work! Like I said in the first post, the NIC is not a part of a team. Anyway it has trouble if other NICs are part of a team with using LACP as team mode.

Any ideas about this?

Regards,

Burak

Sunday, December 29, 2013 8:27 PM

Same issue with Windows 2012R2 and Hyper-V.  No NIC teaming.  If I restart the "NLA (Network Location Awareness)" only, the domain profile comes up ok.  A delayed start on this service does not help.  If I remove the manual IPv4 config and use DHCP, all is fine.

This would suggest an underlying issue beneath NIC teaming.

Is there a Microsoft moderator that could chime in on this?

Thanks,

Skip

Tuesday, February 25, 2014 9:12 PM | 3 votes

Hello,

I found a solution, finally!

The problem is not Port Trunking, it is Spanning-Tree.

I have three network cards. One for management and the other two in an teaming as Hyper-V port.

I configured on my switch that it should use fastmode (or Edge Port) on the ports where the network cards are connected. The ports will switch directly to the Forwarding state if some device is attached to it.

Be careful! If you use fastmode on a port which is connected to another switch, it can create loops!

Read more one: http://vstepic.blogspot.de/2013/07/unidentified-network-on-teamed-interface.html

I did not only set fastmode on the swtich for my teaming NICs, also for the non-teaming management NIC.

Thursday, August 28, 2014 9:01 AM

I noticed this behaviour on a HP Procurve 2810. The interface in question was NOT teamed. Instead it was a dedicated management NIC for the Hyper-V host that worked parallel to the teamed guest NICs. Spanning tree was disabled on the whole switch (should not make a difference for an un-teamed NIC I guess). It did look like DHCP requests would take ages, could not find out why. On a different Procurve I have had no problems with teaming + dhcp + NLA so far.

Edit: Not the switch / STP caused the delay. Instead I was overzealous with the Windows Firewall rules + not every server had applied the new group policies yet. Note: leave the DHCP IN rule open in all profiles (Public, Domain, Private) as the default state is 'public' and you need to be able to receive the DHCP response as well!

Wednesday, January 21, 2015 11:19 PM

I had a similar problem, I resolved it by setting up a DHCP reservation for the NIC Teams IP and MAC Address then put the team into DHCP mode knowing that they will always get the same IP Address.

Wednesday, May 27, 2015 2:32 PM

This was driving me crazy.  Turning spanning-tree to fastmode on my dell switch fixed it.  Thanks.

Friday, July 10, 2015 4:26 PM

Yes, fastmode (or Edge Port) also fixed our issue but our network admin had to run the command to change the setting against not only the team but against each individual port in the team also

Friday, September 11, 2015 6:13 PM

I had the same problem and turning on Fast Link in my Dell switch also solved the issue.  Thank you very much for posting this.

IT Director, Tyler Beverages, Inc.