locked
Unable to connect to the NETLOGON share! RRS feed

  • Question

  • I was installed secondary domain controller but netlogon \ sysvolume  location's are not created as usual.

    Unable to connect to the NETLOGON share! An net use or lsapolicy operation failed with error 67,  error apear when run dcdiag /test:netlogons command.

    How to resolve this issue?

    Sunday, January 15, 2017 1:40 PM

All replies

  • Sunday, January 15, 2017 1:48 PM
  • Hello,

    check below article to resolve your issue

    https://support.microsoft.com/en-us/kb/2958414


    Mahdy

    • Proposed as answer by Wendy Jiang Friday, January 20, 2017 9:29 AM
    Sunday, January 15, 2017 2:00 PM
  • Maybe AD is not replicating correctly. Is this a second DC you promote for the first time or were there other DC's in this forrest prior? Is there were other DC's (orphaned) that might be the problem.

    Try a D2/D4 burflag authorative restore on the PDC and a non authorative restore on the member server.

    https://support.microsoft.com/en-us/kb/290762


    Miguel Fra
    Falcon IT Services
    https://www.falconitservices.com

     


    • Edited by Miguel Fra Sunday, January 15, 2017 9:26 PM
    • Proposed as answer by Wendy Jiang Friday, January 20, 2017 9:29 AM
    Sunday, January 15, 2017 9:25 PM
  • The first thing to check is that you are using correct IP settings to make sure that DNS registration / resolution works fine and that ports needed for AD replication are opened in both directions between your DCs. Check my troubleshooting guide which will help you when checking: http://www.ahmedmalek.com/web/fr/articles.asp?artid=23

    If everything is fine then a non-authoritative restore of SYSVOL/Netlogon on the new DC usually fixes the issue. The details are shared within the guide.


    This posting is provided AS IS with no warranties or guarantees , and confers no rights.

    Ahmed MALEK

    My Website Link

    My Linkedin Profile

    My MVP Profile

    • Proposed as answer by Awinish Tuesday, January 17, 2017 6:51 AM
    Sunday, January 15, 2017 11:36 PM
  • Hi Gayan Abeydeera,

    6..7 Months ago i was also facing the same Prob. during ADC server P2V migration activity. i tried a lot of options but finally it has been resolved as below:

    1-As per Article https://support.microsoft.com/en-in/kb/947022  i have share netlogon. 

    2-On Primary Domain Controller-Authoritative restore & On Additional Domain Controller-Non-Authoritative restore. 

    Hope it may also helpful for you. But before doing it pl. check the basic configuration as TCP/IP and DNS configuration on DC & ADC. 


    Tuesday, January 17, 2017 6:05 AM
  • Hi,

    I am checking how the issue going, if you still have any questions, please feel free to contact us.

    And if the replies as above are helpful, we would appreciate you to mark them as answers, and if you resolve it using your own solution, please share your experience and solution here. It will be greatly helpful to others who have the same question.

    Appreciate for your feedback.

    Best regards,

    Wendy


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

    Friday, January 20, 2017 9:29 AM