Announcement

Collapse
No announcement yet.

SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

    Hi.
    I have posted this thread in the forum last week.The SYSVOL shares are missing on the Windows 2000 Domain controller.i CAN,T LOGON TO THE DOMAIN FROM ANY OF THE DESKTOPS neither can i join a computer to a domain.
    I have two winodows 2000 domain controllers in one of child domains.One of my domain controllers crsahed due to hardware error.i seized the roles using NTDSUTIL to my additional domain controller and removed the failed DC.However i am trying to add a Winodows 2003R2 Server to the Domain.I am getting the following error.
    Cannot join to the Domain ,A Domain controller is not availble.The details of this error are:
    Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

    The domain name admin might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin:

    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.admin

    Common causes of this error include the following:

    - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

    10.5.6.6
    10.8.2.2

    - One or more of the following zones do not include delegation to its child zone:

    Admin
    . (the root zone)

    For information about correcting this problem, click Help.

    I am getting the error in the Event Viewer for SYSVOL as:

    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13566
    Date: 3/29/2007
    Time: 10:34:22 AM
    User: N/A
    Computer: COMP1
    Description:
    File Replication Service is scanning the data in the system volume. Computer COMP1 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.

    To check for the SYSVOL share, at the command prompt, type:
    net share

    When File Replication Service completes the scanning process, the SYSVOL share will appear.

    The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.

    On Running the DCDIAG/FIX on the WIndows 2000 Domain controller i am getting a lot of errors:
    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator>cd \

    C:\>cd program files

    C:\Program Files>cd support tools

    C:\Program Files\Support Tools>dcdiag.exe /fix

    DC Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial non skippeable tests

    Testing server: Admin\COMP1
    Starting test: Connectivity
    ......................... COMP1 passed test Connectivity

    Doing primary tests

    Testing server: Admin\COMP1
    Starting test: Replications
    [Replications Check,COMP1] No replication recently attempted:
    From COMP5 to COMP1
    Naming Context: CN=Schema,CN=Configuration,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:50.00 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From COMP5 to COMP1
    Naming Context: CN=Configuration,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:49.37 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From comp3 to COMP1
    Naming Context: DC=fin,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:53.20 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From comp3 to COMP1
    Naming Context: DC=mab,DC=fin,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:52.40 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From COMP5 to COMP1
    Naming Context: DC=rab,DC=fin,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:52.16 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From COMP5 to COMP1
    Naming Context: DC=fin,DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:51.33 (about 6 hours ago)
    .
    [Replications Check,COMP1] No replication recently attempted:
    From COMP5 to COMP1
    Naming Context: DC=test,DC=com
    The last attempt occurred at 2007-03-29 05:51.10 (about 6 hours ago)
    .
    ......................... COMP1 passed test Replications
    Starting test: NCSecDesc
    ......................... COMP1 passed test NCSecDesc
    Starting test: NetLogons
    ......................... COMP1 passed test NetLogons
    Starting test: Advertising
    Fatal ErrorsGetDcName (COMP1) call failed, error 1355
    The Locator could not find the server.
    ......................... COMP1 failed test Advertising
    Starting test: KnowsOfRoleHolders
    ......................... COMP1 passed test KnowsOfRoleHolders
    Starting test: RidManager
    ......................... COMP1 passed test RidManager
    Starting test: MachineAccount
    ......................... COMP1 passed test MachineAccount
    Starting test: Services
    SMTPSVC Service is stopped on [COMP1]
    ......................... COMP1 failed test Services
    Starting test: ObjectsReplicated
    ......................... COMP1 passed test ObjectsReplicated
    Starting test: frssysvol
    Error: No record of File Replication System, SYSVOL started.
    The Active Directory may be prevented from starting.
    There are errors after the SYSVOL has been shared.
    The SYSVOL can prevent the AD from starting.
    ......................... COMP1 passed test frssysvol
    Starting test: kccevent
    ......................... COMP1 passed test kccevent
    Starting test: systemlog
    ......................... COMP1 passed test systemlog

    Running enterprise tests on : test.com
    Starting test: Intersite
    ......................... test.com passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
    5
    A Good Time Server could not be located.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
    A KDC could not be located - All the KDCs are down.
    ......................... test.com failed test FsmoCheck

    C:\Program Files\Support Tools>netdiag.exe /fix

    .....................................

    Computer Name: COMP1
    DNS Host Name: COMP1.ADMIN.test.com
    System info : Windows 2000 Server (Build 2195)
    Processor : x86 Fatesty 6 Model 11 Stepping 1, GenuineIntel
    List of installed hotfixes :
    Q147222


    Netcard queries test . . . . . . . : Passed

    AutoConfiguration results. . . . . . : Passed

    Default gateway test . . . : Passed

    NetBT name test. . . . . . : Passed
    [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
    r Service', <20> 'WINS' names is missing.

    WINS service test. . . . . : Passed


    Global results:


    Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the local
    machine. This machine is not working properly as a DC.


    Autonet address test . . . . . . . : Passed


    IP loopback ping test. . . . . . . : Passed


    Default gateway test . . . . . . . : Passed

    Winsock test . . . . . . . . . . . : Passed

    DNS test . . . . . . . . . . . . . : Passed
    [WARNING]: The DNS registration for 'COMP1.ADMIN.test.com' is correc
    t only on some DNS servers.
    Please wait 15 min for replication and run the test again.
    PASS - All the DNS entries for DC are registered on DNS server '10.6.6.2' an
    d other DCs also have some of the names registered.


    List of NetBt transports currently bound to the browser
    NetBT_Tcpip_{BC509DD8-114D-41F3-8757-7AB643ABA2E5}
    The browser is bound to 1 NetBt transport.


    DC discovery test. . . . . . . . . : Failed
    [FATAL] Cannot find DC in domain 'ADMIN'. [ERROR_NO_SUCH_DOMAIN]


    DC list test . . . . . . . . . . . : Failed
    'ADMIN': Cannot find DC to get DC list from [test skipped].


    Trust relationship test. . . . . . : Skipped


    Kerberos test. . . . . . . . . . . : Skipped
    'ADMIN': Cannot find DC to get DC list from [test skipped].


    LDAP test. . . . . . . . . . . . . : Failed
    Cannot find DC to run LDAP tests on. The error occurred was: The specified d
    omain either does not exist or could not be contacted.



    Bindings test. . . . . . . . . . . : Passed


    WAN configuration test . . . . . . : Skipped
    No active remote access connections.


    Modem diagnostics test . . . . . . : Passed

    IP Security test . . . . . . . . . : Passed
    IPSec policy service is active, but no policy is assigned.

    Will appreciate for your help.

    Imran.

  • #2
    Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

    so you only had one DC at the site during the failure?

    this will be difficult if you seized the roles of a non-existant domain.

    have you restarted the FRS since this started? ideally the FRS should recreate the sysvol shares correctly...

    the file tree looks like:
    \SYSVOL
    ________\domain
    ________________\DO_NOT_REMOVE_NtFrs_PreInstall_Di rectory
    ________________\Policies
    ________________\Scripts
    ________\scripts
    ________\staging
    ________\staging areas
    ________________\domain_name
    ________\sysvol (shared as SYSVOL)
    ________________\domain_name
    ________________________\DO_NOT_REMOVE_NtFrs_PreIn stall_Directory
    ________________________\Policies
    ________________________\Scripts (shared as NETLOGON)

    if the files arent made, you can make the tree yourself and then restart the netlogon and FRS...

    do you have any backup media containing anything that may be pertinate to say, recovery after a hardware failure?

    backup, backup, backup... tapes are your friend.
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

      Hi James.
      The site was having two Windows 2000 domain controllers.One of the domain controller crashed due to hardware failure.I have seized the roles to the other dc using ntdsutil and metadata cleanup.i can access the active directory users and computers snapin,AD Domains and Trust snapin etc,However i cannot join any computer to the domain neither i have the SYSVOL SHARED AND NETLOGON is also missing.Actually this is one of the child domains.How do i recreate the tree itself.

      Regards,
      Imran

      Comment


      • #4
        Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

        I have been very nice to you (don't ask me why) and deleted your other double post (this one has the better title). NEVER double post again. By rights you should have received a 2 week ban for that. Bah, I am going soft. Maybe you get the 2 week ban after your DC is fixed.

        When posting logs, errors etc, put them in a TXT file and attach them to your post. Makes it easier to follow the thread if it isn't several hundred feet long.

        What does the C:\WINDOWS\debug\dcdiag.txt file say?
        List the step you took with the 2003 Server.
        Have you tried restoring from tape and this has happened? http://support.microsoft.com/kb/316790
        Troubleshooting missing shares. http://support.microsoft.com/kb/257338
        How to rebuild the SYSVOL tree and its content in a domain. http://support.microsoft.com/default...b;en-us;315457

        Did you bother to Google this problem?
        1 1 was a racehorse.
        2 2 was 1 2.
        1 1 1 1 race 1 day,
        2 2 1 1 2

        Comment


        • #5
          Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

          hmmm. at this point, not having enough information to throw out a simple answer, i will instead refer you to a microsoft publication that will answer the questions youre asking...


          Best Practices: Active Directory Forest Recovery
          Brief Description
          This paper is a best practice recommendation for recovering an Active DirectoryŽ forest after forest-wide failure has rendered all domain controllers (DCs) in the forest incapable of functioning normally. One section of the paper describes how you can reset trust passwords on one side of the trust.


          http://www.microsoft.com/downloads/d...C-933FEBA08CFE

          i cant imagine you will need more info than this. if you need any clarification, feel free to ask or PM me if need be. im kinda bored today.

          How do i recreate the tree itself.
          ummm.. by right clciking and creating a new folder, then naming it what its supposed to be. the tree is above, as generic as it looks... just create and name them the same, then make sure the share names are the same (including capitals).

          take a good gander thru the link i posted, as this is your best bet at fixing the problem.

          good luck!
          Last edited by James Haynes; 2nd April 2007, 21:12.
          its easier to beg forgiveness than ask permission.
          Give karma where karma is due...

          Comment


          • #6
            Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

            Imran, have you fixed your problem yet?
            1 1 was a racehorse.
            2 2 was 1 2.
            1 1 1 1 race 1 day,
            2 2 1 1 2

            Comment


            • #7
              Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

              Bump......
              1 1 was a racehorse.
              2 2 was 1 2.
              1 1 1 1 race 1 day,
              2 2 1 1 2

              Comment


              • #8
                Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

                This problem seems like a problem I had recently which was resolved by seizing the FSMO roles of the failed domain controller.

                Comment


                • #9
                  Re: SYSVOL and Netlogon shares missing on Windows 2000 Domain controller.

                  The names of the domains are raising some questions...

                  What is the forest root domain DNS name ? is it test.com or is it "admin" (single label domain).

                  I see 2 references to domain names: test.com and "admin".
                  What is the relationship between those two ?
                  Which one is functioning ? Which one is broken ?
                  Guy Teverovsky
                  "Smith & Wesson - the original point and click interface"

                  Comment

                  Working...
                  X