none
'Domain authenticated' profile to an adapter

    Question

  • Hi Guys,

    We have a virtual adapter which is used by our application for traffic forwarding. But we see strange behavior by windows when the user system is under domain. Sometime, our adapter is assigned 'domain authenticated' profile and sometime its not.

    Can someone give definite criteria and procedure by which windows assigns 'domain authenticated' profile to an adapter.

    Also, if I try to use SetCategory API of INetwork interface, it gives error :

     Error:  0x80070005 (ACCESS DENIED)
    Thursday, February 02, 2017 7:22 AM

All replies

  • Hi Ukrz,

    >>Sometime, our adapter is assigned 'domain authenticated' profile and sometime its not.

    Did you mean that network location of adapter is domain authenticated?

    Have you joined client in domain?

    If yes, please ensure connection is correct between client and PDC.

    Here is information about network location for your reference:

    Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles

    https://blogs.technet.microsoft.com/networking/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles/

    Best Regards

    John


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by John Lii Monday, February 27, 2017 9:28 AM
    Friday, February 03, 2017 11:43 AM
  • Thanks john for your response.

    Yes, I meant sometimes that network location of adapter is domain authenticated and sometime its not.

    Sometimes it also shows "attempting to authenticate".

    Yes, client have joined domain and physical interface's location is shown as 'Domain Controlled'

    Connection between client and PDC is fine and physical adapter's location is shown as 'Domain Controlled' but our virtual adapter's location is shown as 'public'

    I have already seen that link but windows don't seem to behave according to that document.

    Monday, February 06, 2017 6:19 AM
  • Hi Ukrz,

    Please check link below try to configure network location:

    http://evansblog.thebarrs.info/2013/02/windows-server-force-your-network.html

    Hope it is helpful for you.

    Best Regards

    John


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 07, 2017 11:08 AM
  • Hi Ukrz,

    Was your issue resolved?

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards

    John


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 27, 2017 9:29 AM