help with DNS configuration

E

Edward

Guest
I have a domain controller IP 192.168.1.2
I now try to set up an exchange server on another server 192.168.1.3
For some reason, the exchange server could not see my domain controller.
"dcdiag.exe" gave the report below which I suspect is due to DNS
configuration error.
Any help or suggestion?
(NB: my DNS server is also my domain controller and the forward looking zone
is pointed towards my ISP's DNS server)

Thanks.

===== dcdiag.exe report below =========================

Domain Controller Diagnosis

Performing initial setup:
*** Warning: could not confirm the identity of this server in the
directory versus the names returned by DNS servers.
If there are problems accessing this directory server then you may
need to check that this server is correctly registered
with DNS
[192.168.1.2] Directory Binding Error 87:
The parameter is incorrect.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\domain_controller
Starting test: Connectivity
The host bccc172f-3120-4fa1-8e59-8596f7008183._msdcs.my_domain.com
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
......................... domain_controller failed test
Connectivity

Doing primary tests

Testing server: Default-First-Site\domain_controller
Skipping all tests, because server domain_controller is
not responding to directory service requests


 


L

Lanwench [MVP - Exchange]

Guest
Edward <hsmmsc@hotmail.com> wrote:
> I have a domain controller IP 192.168.1.2
> I now try to set up an exchange server on another server 192.168.1.3
> For some reason, the exchange server could not see my domain
> controller. "dcdiag.exe" gave the report below which I suspect is due
> to DNS configuration error.
> Any help or suggestion?
> (NB: my DNS server is also my domain controller and the forward
> looking zone is pointed towards my ISP's DNS server)
>
> Thanks.
>
> ===== dcdiag.exe report below =========================
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> *** Warning: could not confirm the identity of this server in the
> directory versus the names returned by DNS servers.
> If there are problems accessing this directory server then
> you may need to check that this server is correctly registered
> with DNS
> [192.168.1.2] Directory Binding Error 87:
> The parameter is incorrect.
> This may limit some of the tests that can be performed.
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site\domain_controller
> Starting test: Connectivity
> The host
> bccc172f-3120-4fa1-8e59-8596f7008183._msdcs.my_domain.com could not
> be resolved to an IP address. Check the DNS server, DHCP,
> server name, etc ......................... domain_controller
> failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site\domain_controller
> Skipping all tests, because server domain_controller is
> not responding to directory service requests

Are you running dcdiag on this server, or on the DC? Run it on the DC. Run
netdiag on the would-be Exchange server. You might also post an unedited
ipconfig /all from each server - and mention whether your workstations are
having any problems communicating with the DC.


 
L

Lanwench [MVP - Exchange]

Guest
Edward <hsmmsc@hotmail.com> wrote:
> I have a domain controller IP 192.168.1.2
> I now try to set up an exchange server on another server 192.168.1.3
> For some reason, the exchange server could not see my domain
> controller. "dcdiag.exe" gave the report below which I suspect is due
> to DNS configuration error.
> Any help or suggestion?
> (NB: my DNS server is also my domain controller and the forward
> looking zone is pointed towards my ISP's DNS server)
>
> Thanks.
>
> ===== dcdiag.exe report below =========================
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> *** Warning: could not confirm the identity of this server in the
> directory versus the names returned by DNS servers.
> If there are problems accessing this directory server then
> you may need to check that this server is correctly registered
> with DNS
> [192.168.1.2] Directory Binding Error 87:
> The parameter is incorrect.
> This may limit some of the tests that can be performed.
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site\domain_controller
> Starting test: Connectivity
> The host
> bccc172f-3120-4fa1-8e59-8596f7008183._msdcs.my_domain.com could not
> be resolved to an IP address. Check the DNS server, DHCP,
> server name, etc ......................... domain_controller
> failed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site\domain_controller
> Skipping all tests, because server domain_controller is
> not responding to directory service requests

Are you running dcdiag on this server, or on the DC? Run it on the DC. Run
netdiag on the would-be Exchange server. You might also post an unedited
ipconfig /all from each server - and mention whether your workstations are
having any problems communicating with the DC.


 

Top