• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1392
  • Last Modified:

Can't install Exchange 2013 - 500pnts

I am trying to install the first Exchange 2013 server onto out network.

I've update the Schema which has work and Prep the AD and confirmed by using ADSI Edit.

Also I can confirm I am logged on as the Domain administrator which is a member of the correct groups etc.

The DNS appears to have the LDAP SRV records in DNS - I'll attached a screen dump

I've run Nslookup to try and find LDAP server this was the result.

D:\>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  192.168.2.220

> setq=rr_type
Server:  UnKnown
Address:  192.168.2.220

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
> _ldap._tcp.dc._msdcs.wiseman.co.uk
Server:  UnKnown
Address:  192.168.2.220

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
Name:    _ldap._tcp.dc._msdcs.wiseman.co.uk

The ExchangeSetupLog seems to suggest that the The LDAP server is unavailable, but the exchange box is a member server and part of the domain.

[04/11/2014 17:28:36.0562] [0] Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information on this error.
[04/11/2014 17:28:36.0562] [0] Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.
[04/11/2014 17:28:36.0562] [0] The LDAP server is unavailable.

I've attached the ExchangeSetupLogs.txt file
ExchangeSetup.log
0
ise438
Asked:
ise438
  • 2
2 Solutions
 
ise438Author Commented:
Ok it's installed now - I had 8.8.8.8 set in the DNS as third DNS server - I removed it and Exchange installed.

But I don't understand Why?

500pnt still up for grabs
DNS.bmp
0
 
Adam BrownSr Solutions ArchitectCommented:
How was 8.8.8.8 configured as a DNS server? Was it a forwarder, or configured on the server's NIC? Incidentally, the lookup you did in NSLOOKUP won't work unless you do
set type=SRV
Which servers were configured for DNS on the Exchange server?
0
 
nylexSupport TechCommented:
I would assume that 8.8.8.8 was set on the NIC of the exchange server based on that behavior.  Microsoft DNS supports round robin processing, so it was probably running the AD test on all of the available DNS servers to make sure that no matter which DNS came up in the round robin table that exchange could resolve the DC addresses.  When it hits the 8.8.8.8 address it fails the test as exchange servers should only have internal DNS configured on the NIC with a forwarder on the internal DNS server to get out to the internet.

More info on round robin DNS can be found here: http://en.wikipedia.org/wiki/Round-robin_DNS
0
 
ise438Author Commented:
8.8.8.8 was installed on the Servers NIC - But thank now I under
1

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now