Announcement

Collapse
No announcement yet.

Unable to Access Shared Folder by UNC

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

  • Unable to Access Shared Folder by UNC

    Hi All,

    We have a 2003 DC with integrated DNS and acting as a Filerserver. Recently we are unable to access the Shares by UNC NAME but can access by ip. "The Target Account Name is incorrect".

    Moreover the DNS server shows "The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code." Any Help would be greatly apprecited...


    ipconfig/all

    Host Name . . . . . . . . . . . . : SERVER
    Primary Dns Suffix . . . . . . . : testserver.com
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : testserver.com

    ernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.1.100
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 192.168.1.100

  • #2
    Check the event logs for AD and DNS related events
    What IS the error code?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      The DNS related Event ID is 4000 and Directory service Event ID is 1126 (Active Directory was unable to establish a connection with the global catalog.

      Additional Data
      Error value:
      1355 The specified domain either does not exist or could not be contacted.
      Internal ID:
      3200d33.

      here is the dcdiag /test:dns result

      C:\Documents and Settings\Administrator>dcdiag /test:dns

      Domain Controller Diagnosis

      Performing initial setup:
      Done gathering initial info.

      Doing initial required tests

      Testing server: Default-First-Site-Name\SERVER
      Starting test: Connectivity
      ......................... SERVER passed test Connectivity

      Doing primary tests

      Testing server: Default-First-Site-Name\SERVER

      DNS Tests are running and not hung. Please wait a few minutes...

      Running partition tests on : ForestDnsZones

      Running partition tests on : DomainDnsZones

      Running partition tests on : Schema

      Running partition tests on : Configuration

      Running partition tests on : newage

      Running enterprise tests on : newage.com
      Starting test: DNS
      Test results for domain controllers:

      DC: SERVER.newage.com
      Domain: newage.com


      TEST: Forwarders/Root hints (Forw)
      Error: Forwarders list has invalid forwarder: 4.2.2.2 (<name
      unnavailable>)
      Error: Forwarders list has invalid forwarder: 8.8.4.4 (<name
      unnavailable>)
      Error: Root hints list has invalid root hint server: a.root-
      rvers.net. (198.41.0.4)
      Error: Root hints list has invalid root hint server: b.root-
      rvers.net. (192.228.79.201)
      Error: Root hints list has invalid root hint server: c.root-
      rvers.net. (192.33.4.12)
      Error: Root hints list has invalid root hint server: d.root-
      rvers.net. (199.7.91.13)
      Error: Root hints list has invalid root hint server: e.root-
      rvers.net. (192.203.230.10)
      .............

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

      DNS server: 192.112.36.4 (g.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.112.36.4

      DNS server: 192.203.230.10 (e.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.203.230.10

      DNS server: 192.228.79.201 (b.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.228.79.201

      DNS server: 192.33.4.12 (c.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.33.4.12

      DNS server: 192.36.148.17 (i.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.36.148.17

      DNS server: 192.5.5.241 (f.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.5.5.241

      DNS server: 192.58.128.30 (j.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 192.58.128.30

      DNS server: 193.0.14.129 (k.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 193.0.14.129

      DNS server: 198.41.0.4 (a.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 198.41.0.4

      DNS server: 199.7.83.42 (l.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 199.7.83.42

      DNS server: 199.7.91.13 (d.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 199.7.91.13

      DNS server: 202.12.27.33 (m.root-servers.net.)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 202.12.27.33

      DNS server: 4.2.2.2 (<name unavailable>)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 4.2.2.2

      DNS server: 8.8.4.4 (<name unavailable>)
      1 test failure on this DNS server
      This is not a valid DNS server. PTR record query for the 1.0.0.
      7.in-addr.arpa. failed on the DNS server 8.8.4.4

      Summary of DNS test results:

      Auth Basc Forw Del Dyn RReg Ext
      __________________________________________________ _____________
      Domain: newage.com
      SERVER PASS PASS FAIL PASS WARN PASS n/a

      ......................... newage.com failed test DNS

      Comment


      • #4
        What have you tried to fix this? There are several event 4000 troubleshooting resources on the net for W2k-W2k3.

        A recent poll suggests that 6 out of 7 dwarfs are not happy

        Comment


        • #5
          I have followed several links and ideas but bothing worked. Today Morning I reset the secure channels to DC (using netdom Command )after that the error is not showing up. The only problem I am facing now is the DC is not resolving the domain names.


          IPconfig/all



          Host Name . . . . . . . . . . . . : SERVER
          Primary Dns Suffix . . . . . . . : newage.com
          Node Type . . . . . . . . . . . . : Unknown
          IP Routing Enabled. . . . . . . . : No
          WINS Proxy Enabled. . . . . . . . : No
          DNS Suffix Search List. . . . . . : newage.com

          ernet adapter Local Area Connection 3:

          Connection-specific DNS Suffix . :
          Description . . . . . . . . . . . : Broadcom NetLink
          Physical Address. . . . . . . . . : 00-1A-4D-DB-A4-3
          DHCP Enabled. . . . . . . . . . . : No
          IP Address. . . . . . . . . . . . : 192.168.1.100
          Subnet Mask . . . . . . . . . . . : 255.255.255.0
          Default Gateway . . . . . . . . . :
          DNS Servers . . . . . . . . . . . : 192.168.1.100

          Comment


          • #6
            Do you mean internal or external domain names?
            Since you don't have a default gateway specified, you cannot resolve external ones
            Is DNS AD integrated or stand alone?
            Tom Jones
            MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
            PhD, MSc, FIAP, MIITT
            IT Trainer / Consultant
            Ossian Ltd
            Scotland

            ** Remember to give credit where credit is due and leave reputation points where appropriate **

            Comment


            • #7
              External Domains.After Giving the GW, it is working Fine. Thanks a lot...................

              Comment

              Working...
              X