Announcement

Collapse
No announcement yet.

Domain ug to 2k8r2 gone a little wrong.

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

  • Domain ug to 2k8r2 gone a little wrong.

    Guys,

    I have just completed an domain & server upgrade to 2k8r2. 2 old 2k3 servers demoted l/rebuilt and promoted back. The issue I'm having is the clients are taking a long time to start up and when they logon they can't get mapped drives via script. The event logs have 1054 errors saying it cant access the policy and gptinit errors where logon scripts aren't running.

    For some reason I can't access the scripts folder on dc01 which is the first dc. I can't access the c$ admin share or browse the server in network neighborhood. However I can browse and see the c$ share on dc02 which was the second to be promoted, I can see the sysvol of that server also.

    There don't seem to be any dhcp/dns issues as the servers can be pinged resolved and nslookup is working as expected.

    Is there any special security setting I have missed? I built both the servers in the same way too..

    Thanks for any help!
    James

  • #2
    Re: Domain ug to 2k8r2 gone a little wrong.

    did you demote and rebuild ALL the servers?

    run dcdiag and see if the FSMO roles are correct..
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Domain ug to 2k8r2 gone a little wrong.

      i did indeed demote/rebuild both the 2k3 dcs.. Here is a dcdiag report.
      Attached Files

      Comment


      • #4
        Re: Domain ug to 2k8r2 gone a little wrong.

        You have a reference to the following KB listed for both domain controllers and some FRS warnings:

        http://support.microsoft.com/kb/312862

        I'd give that article a bash and see what happens.

        Comment


        • #5
          Re: Domain ug to 2k8r2 gone a little wrong.

          It will be worth reviewing the Network security: LAN Man authentication level. See if some computers via GPO or manually have LM and NTLM only whilst others have NTLMv2 only.

          May not be the cause but always worth checking.

          Comment


          • #6
            Re: Domain ug to 2k8r2 gone a little wrong.

            A few things to check/modify:

            1. Turn off the Firewall (enabled by default on W2k8 r2)
            2. Turn off User Account Control (see User Accounts section in Control Panel).
            3. Turn on Network discovery, file sharing in the Network Centre

            Comment


            • #7
              Re: Domain ug to 2k8r2 gone a little wrong.

              Is the new DC a GC? Is DNS correct in DHCP?
              1 1 was a racehorse.
              2 2 was 1 2.
              1 1 1 1 race 1 day,
              2 2 1 1 2

              Comment

              Working...
              X