Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Nic Teaming - Unidentified Network

Answered Nic Teaming - Unidentified Network

  • Friday, January 25, 2013 4:32 PM
     
     
    Sign In to Vote
    0

    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?

     

All Replies

  • Friday, January 25, 2013 4:35 PM
     
     
    Sign In to Vote
    0

    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

     
  • Friday, January 25, 2013 8:54 PM
     
     Answered
    Sign In to Vote
    0

    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.
     
  • Wednesday, January 30, 2013 12:02 AM
     
     Answered
    Sign In to Vote
    0

    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.