Link to home
Start Free TrialLog in
Avatar of loosain
loosain

asked on

Exchange 2013 doesn´t talk to my activedirectory / domain

Hi,

we installed a fresh domaincontroller (2012 R2) and a fresh Exchange 2013 (2012 R2). Both as virtual servers on hyperV (2012 R2). We got no errors during installation. The Exchange Server is member in the domain. But now, if i want to create a new user in Exchange, it can´t search the AD. It says that ther would be no domain...
In exchange-shell get-domaincontrollers lists my DC...
Could you help me. I am installing and searching now for hours. I think i can´t see the wood for the trees...

Thanks

loosain
SOLUTION
Avatar of Amit
Amit
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of loosain
loosain

ASKER

[PS] C:\Windows\system32>test-servicehealth


Role                    : Postfachserverrolle
RequiredServicesRunning : False
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeIS, MSExchangeMailboxAssistants, MSExchangeRPC,
                          MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {MSExchangeDelivery, MSExchangeRepl, MSExchangeSubmission, MSExchangeThrottling,
                          MSExchangeTransportLogSearch}

Role                    : Clientzugriffs-Serverrolle
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC,
                          MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Unified Messaging-Serverrolle
RequiredServicesRunning : False
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {MSExchangeUM}

Role                    : Hub-Transport-Serverrolle
RequiredServicesRunning : False
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
                          MSExchangeTransport, W3Svc, WinRM}
ServicesNotRunning      : {MSExchangeTransportLogSearch}



[PS] C:\Windows\system32>set l
[PS] C:\Windows\system32>ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Exchange
   Primäres DNS-Suffix . . . . . . . : dom-mz.local
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : dom-mz.local

Ethernet-Adapter Ethernet:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Hyper-V-Netzwerkadapter
   Physische Adresse . . . . . . . . : 00-15-5D-01-33-04
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   Verbindungslokale IPv6-Adresse  . : fe80::e05e:db96:a0a:131e%12(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.80.101(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.80.1
   DHCPv6-IAID . . . . . . . . . . . : 201332061
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-1D-B6-AB-59-00-15-5D-01-33-04
   DNS-Server  . . . . . . . . . . . : 192.168.80.100
                                       192.168.80.1
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Tunneladapter isatap.{8F92B6B2-157E-43B4-A006-14460FC42767}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I see DG is also set as DNS

  DNS-Server  . . . . . . . . . . . : 192.168.80.100
                                        192.168.80.1

Check if you have defined proper DNS Server.
Avatar of loosain

ASKER

What specialy do you mean by proper DNS? It points the Domain to dc and autodiscover.Maildomain.com points to Exchange. Exchange and dc have correct ip s Set too... Anything Else neccesary?
192.168.80.100 is your dns server?
used tool "nltest" ?

also it looks like your machine is a HyperV VM.

can you check if you can ping the DC directly?

and ping the AD domain name.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of loosain

ASKER

Found it. i couldn´t ping the domain. I just (to test) entered an entry in hosts and now outlook runs. I have to fix it in dns...
So 2 problems: symantec on client and no ip for the domain dom.local in the dns.