Se houver um firewall entre o servidor host e seus controladores de domínio, você precisará garantir que ele esteja configurado para permitir a passagem do tráfego aplicável entre eles. A Microsoft tem um KB sobre o que é necessário:
Estou com dificuldades para entrar no meu Windows Server no domínio, posso saber qual poderia ser o problema?
Suspeito que exista um firewall entre esse site interno de DR e a DMZ em que o Forefront TMG 2010 está implantado?
DCDiag /s: result:
Directory Server Diagnosis
Performing initial setup:
[DCDNS01.domain.com] LDAP bind failed with error 1326,
Win32 Error 1326.
Server DCDNS01.domain.com resolved to these IP addresses: 192.168.127.10,
but none of the addresses could be reached (pinged). Please check the
network.
Error: 0x2b02 "Win32 Error 11010"
This error more often means that the targeted server is shutdown or
disconnected from the network.
ok, do portqry eu recebo o seguinte resultado enquanto o resto com saídas com código de retorno 0x00000000 significa que está OK? então por que existem alguns com o código de saída 1 e 2?
UDP port 389 (unknown service): LISTENING or FILTERED
Using ephemeral source port
Sending LDAP query to UDP port 389...
LDAP query to port 389 failed
Server did not respond to LDAP query
portqry.exe -n 192.168.12.5 -e 389 -p BOTH exits with return code 0x00000001.
=============================================
Starting portqry.exe -n 192.168.12.5 -e 53 -p BOTH ...
Querying target system called:
192.168.12.5
Attempting to resolve IP address to a name...
IP address resolved to DR-DCDNS01-vm.domain.com
querying...
TCP port 53 (domain service): LISTENING
UDP port 53 (domain service): LISTENING or FILTERED
Sending DNS query to UDP port 53...
DNS query timed out
portqry.exe -n 192.168.12.5 -e 53 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n 192.168.12.5 -e 88 -p BOTH ...
Querying target system called:
192.168.12.5
Attempting to resolve IP address to a name...
IP address resolved to DR-DCDNS01-vm.domain.com
querying...
TCP port 88 (kerberos service): LISTENING
UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n 192.168.12.5 -e 88 -p BOTH exits with return code 0x00000002.
=============================================
Starting portqry.exe -n 192.168.12.5 -e 138 -p UDP ...
Querying target system called:
192.168.12.5
Attempting to resolve IP address to a name...
IP address resolved to DR-DCDNS01-vm.domain.com
querying...
UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n 192.168.12.5 -e 138 -p UDP exits with return code 0x00000002.
=============================================
Starting portqry.exe -n 192.168.12.5 -e 42 -p TCP ...
Querying target system called:
192.168.12.5
Attempting to resolve IP address to a name...
IP address resolved to DR-DCDNS01-vm.domain.com
querying...
TCP port 42 (nameserver service): FILTERED
portqry.exe -n 192.168.12.5 -e 42 -p TCP exits with return code 0x00000002.
qualquer tipo de ajuda seria muito apreciado.
Se houver um firewall entre o servidor host e seus controladores de domínio, você precisará garantir que ele esteja configurado para permitir a passagem do tráfego aplicável entre eles. A Microsoft tem um KB sobre o que é necessário: