Problema do Active Directory / DNS

Question

Problema do Active Directory / DNS

#1 resposta do (3 votos)
#2 resposta do (0 votos)

3

Estou tendo alguns problemas com nossa resolução de nome de domínio local por algum motivo. Uma breve descrição da minha rede inteira é: Temos dois escritórios. Cada escritório tem seu próprio DC e seu próprio firewall, mas ambos os escritórios são replicados entre si. Agora, uma das redes do escritório está funcionando bem, a que estou tendo problemas é a que estou usando atualmente.

Como exemplo, posso acessar \\ server1 \ myshare, mas não consigo acessar \\ mydomain.net \ myshare na minha rede atual. Na outra rede, tudo está funcionando bem. Agora, em intervalos aleatórios quando estou no RDP no servidor1, consigo acessar o domínio, mas outras vezes não consigo. Acredito que localizei o culpado, mas ainda não sei como começar a corrigir esse problema. Aqui está a saída do dcdiag:

C:\Users\Administrator>dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = BGS-HQ-VRDSVR01
   * Identified AD Forest.
   Ldap search capabality attribute search failed on server BGS-CP-VRDSVR01,
   return value = 81
   Got error while checking if the DC is using FRS or DFSR. Error:
   Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail
   because of this error.
   Done gathering initial info.

Doing initial required tests

   Testing server: BGS-HQ\BGS-HQ-VRDSVR01
      Starting test: Connectivity
         The host 6282bfca-ade1-41c8-84dc-516ce19b49be._msdcs.billsgs.net could
         not be resolved to an IP address. Check the DNS server, DHCP, server
         name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your
         firewall settings.
         ......................... BGS-HQ-VRDSVR01 failed test Connectivity

Doing primary tests

   Testing server: BGS-HQ\BGS-HQ-VRDSVR01
      Skipping all tests, because server BGS-HQ-VRDSVR01 is not responding to

Agora ... a parte divertida disso é que eu corri o seguinte:

C:\Users\Administrator>nslookup 6282bfca-ade1-41c8-84dc-516ce19b49be._msdcs.bill
sgs.net
Server:  bgs-hq-vrdsvr01.billsgs.net
Address:  192.168.40.13

Name:    bgs-hq-vrdsvr01.billsgs.net
Address:  192.168.40.13
Aliases:  6282bfca-ade1-41c8-84dc-516ce19b49be._msdcs.billsgs.net

Qualquer sugestão sobre isso seria muito apreciada. Eu sou um programador, não um administrador de rede, então eu certamente não conheço muitas técnicas de depuração com isso, e especialmente com o Windows Server.

Além disso, como nota lateral, desativamos o servidor de replicação por enquanto, por algum motivo, ele está literalmente usando todos os 12 GB de RAM no servidor. Eu não tenho certeza se isso está relacionado, mas a partir de agora está em segundo plano.

EDIT: Peço desculpas, estamos executando o Windows Server 2008 R2 e abaixo é um ipconfig / all do servidor.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : BGS-HQ-VRDSVR01
   Primary Dns Suffix  . . . . . . . : billsgs.net
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : billsgs.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-03-BA-38
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.40.13(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.40.254
   DNS Servers . . . . . . . . . . . : 192.168.40.13
                                       192.168.40.254
   Primary WINS Server . . . . . . . : 192.168.40.13
   Secondary WINS Server . . . . . . : 192.168.41.17
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{ADEC15A8-2603-40EB-964C-489CCBD11E08}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

EDIT: Aqui está a saída de um teste de DNS que eu corri.

C:\Users\Administrator>dcdiag /test:DNS

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = BGS-HQ-VRDSVR01
   * Identified AD Forest.
   Ldap search capabality attribute search failed on server BGS-CP-VRDSVR01, return value = 81
   Got error while checking if the DC is using FRS or DFSR. Error: Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail because of this error.
   Done gathering initial info.

Doing initial required tests

   Testing server: BGS-HQ\BGS-HQ-VRDSVR01
      Starting test: Connectivity
         The host 6282bfca-ade1-41c8-84dc-516ce19b49be._msdcs.billsgs.net could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
         ......................... BGS-HQ-VRDSVR01 failed test Connectivity

Doing primary tests

   Testing server: BGS-HQ\BGS-HQ-VRDSVR01

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... BGS-HQ-VRDSVR01 passed test DNS

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : billsgs

   Running enterprise tests on : billsgs.net
      Starting test: DNS
         Test results for domain controllers:

            DC: BGS-HQ-VRDSVR01.billsgs.net
            Domain: billsgs.net


               TEST: Basic (Basc)
                  Error: No LDAP connectivity
                  Warning: adapter [00000007] Intel(R) PRO/1000 MT Network Connection has invalid DNS server: 192.168.40.254 (<name unavailable>)
                  No host records (A or AAAA) were found for this DC

               TEST: Forwarders/Root hints (Forw)
                  Error: All forwarders in the forwarder list are invalid.
                  Error: Both root hints and forwarders are not configured or broken. Please make sure at least one of them works.

               TEST: Delegations (Del)
                  Error: DNS server: bgs-cp-vrdsvr01.billsgs.net. IP:192.168.41.17 [Broken delegated domain _msdcs.billsgs.net.]
                  Error: DNS server: bgs-cp-vrdsvr01.billsgs.net. IP:192.168.41.17 [Broken delegated domain cp.billsgs.net.]

               TEST: Dynamic update (Dyn)
                  Warning: Failed to add the test record dcdiag-test-record in zone billsgs.net

               TEST: Records registration (RReg)
                  Network Adapter [00000007] Intel(R) PRO/1000 MT Network Connection:
                     Warning:
                     Missing CNAME record at DNS server 192.168.40.254:
                     6282bfca-ade1-41c8-84dc-516ce19b49be._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.22017278-29d1-493a-b72d-e44b31411a70.domains._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kerberos._tcp.dc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.dc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kerberos._tcp.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kerberos._udp.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kpasswd._tcp.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.BGS-HQ._sites.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kerberos._tcp.BGS-HQ._sites.dc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.BGS-HQ._sites.dc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _kerberos._tcp.BGS-HQ._sites.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.gc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _gc._tcp.BGS-HQ._sites.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.BGS-HQ._sites.gc._msdcs.billsgs.net

                     Error:
                     Missing SRV record at DNS server 192.168.40.254:
                     _ldap._tcp.pdc._msdcs.billsgs.net

               Error: Record registrations cannot be found for all the network adapters

         Summary of test results for DNS servers used by the above domain controllers:

            DNS server: 192.168.41.17 (bgs-cp-vrdsvr01.billsgs.net.)
               2 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.41.17
            DNS server: 128.63.2.53 (h.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
            DNS server: 192.112.36.4 (g.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4
            DNS server: 192.168.40.254 (<name unavailable>)
               1 test failure on this DNS server
               Name resolution is not functional. _ldap._tcp.billsgs.net. failed on the DNS server 192.168.40.254

            DNS server: 192.203.230.10 (e.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.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
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 199.7.83.42
            DNS server: 202.12.27.33 (m.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
            DNS server: 209.253.113.10 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.253.113.10
            DNS server: 209.253.113.2 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.253.113.2
         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: billsgs.net
               BGS-HQ-VRDSVR01              PASS FAIL FAIL FAIL WARN FAIL n/a

         ......................... billsgs.net failed test DNS

e .. a saída "repadmin / bind BGS-VRDSVR01" ..

C:\Users\Administrator.BILLSGS>repadmin /bind BGS-HQ-VRDSVR01
Bind to BGS-HQ-VRDSVR01 succeeded.
NTDSAPI V1 BindState, printing extended members.
    bindAddr: BGS-HQ-VRDSVR01
Extensions supported (cb=48):
    BASE                             : Yes
    ASYNCREPL                        : Yes
    REMOVEAPI                        : Yes
    MOVEREQ_V2                       : Yes
    GETCHG_COMPRESS                  : Yes
    DCINFO_V1                        : Yes
    RESTORE_USN_OPTIMIZATION         : Yes
    KCC_EXECUTE                      : Yes
    ADDENTRY_V2                      : Yes
    LINKED_VALUE_REPLICATION         : Yes
    DCINFO_V2                        : Yes
    INSTANCE_TYPE_NOT_REQ_ON_MOD     : Yes
    CRYPTO_BIND                      : Yes
    GET_REPL_INFO                    : Yes
    STRONG_ENCRYPTION                : Yes
    DCINFO_VFFFFFFFF                 : Yes
    TRANSITIVE_MEMBERSHIP            : Yes
    ADD_SID_HISTORY                  : Yes
    POST_BETA3                       : Yes
    GET_MEMBERSHIPS2                 : Yes
    GETCHGREQ_V6 (WINDOWS XP PREVIEW): Yes
    NONDOMAIN_NCS                    : Yes
    GETCHGREQ_V8 (WINDOWS XP BETA 1) : Yes
    GETCHGREPLY_V5 (WINDOWS XP BETA 2): Yes
    GETCHGREPLY_V6 (WINDOWS XP BETA 2): Yes
    ADDENTRYREPLY_V3 (WINDOWS XP BETA 3): Yes
    GETCHGREPLY_V7 (WINDOWS XP BETA 3) : Yes
    VERIFY_OBJECT (WINDOWS XP BETA 3): Yes
    XPRESS_COMPRESSION               : Yes
    DRS_EXT_ADAM                     : No
    GETCHGREQ_V10                    : Yes
    RECYCLE BIN FEATURE              : No
Site GUID: afe99967-2bae-4850-b6c8-a84fc37cbd87
Repl epoch: 0
Forest GUID: 1c4eb6fd-77b5-46de-a4b0-c9c51087eb7d
Security information on the binding is as follows:
    SPN Requested:  LDAP/BGS-HQ-VRDSVR01
    Authn Service:  9
    Authn Level:  6
    Authz Service:  0

Além disso, aqui está uma lista de processamento ...

link

active-directory domain windows-server-2008-r2

por Dalton Conley 29.07.2011 / 18:09

2 respostas

Tags active-directory domain windows-server-2008-r2

HP laserjet mostra off-line no servidor, mas é passível de ping É possível obter um detalhamento do uso de largura de banda por arquivo no AWS CloudFront?

score 3 · Answer 1

Para ver se isso é relacionado ao firewall baseado em host, desative temporariamente o domínio e os perfis público e privado. Você tem várias interfaces, como no Windows Server 2008, o perfil mais restritivo está em vigor. Execute isso a partir do prompt de comando elevado

netsh advfirewall define o estado do publicprofile desativado
netsh advfirewall define estado do perfil de privacidade desativado
netsh advfirewall define o estado do perfil de domínio desativado

O uso da memória pode ser enganoso. Muitas vezes é usado, mas liberado quando necessário. Consulte o log de eventos operacionais do detector de exaustão de recursos (abra eventvwr e vá para aplicativos e serviços / microsoft / windows / resource exaustment detector / operating) para determinar se a falta de memória está acabando.

Use o Process Explorer para ver o uso da memória e ver o que está disponível. Se a aparência estiver baixa, verifique com o RAMMap da Syinternals para ter uma idéia do uso. Veja o RAMmap explicado no link porque tive casos em que metarquivo estava "consumindo" isso. Mas era um comportamento esperado.

O erro 81 no DCDiag indica que o servidor LDAP estava inacessível. Você tem algum produto de terceiros no próprio DC fornecendo o comportamento incluído do Antivirus + Firewall? Se você puder acessar o LDAP enquanto estiver no DC, mas não remoto, e se tiver certeza de que nenhum firewall baseado em host está em uso, eu verificaria se algum dispositivo de rede intermediário está filtrando / descartando pacotes.

score 0 · Answer 2

Se você tiver uma rede pública em qualquer um dos adaptadores, certifique-se de que o servidor DNS principal seja o "ip público de si mesmo" que resolveu o problema para mim.