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
loosainAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
Can you run this command and post the result.

test-servicehealth
set l
ipconfig /all
0
loosainAuthor Commented:
[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
0
Justin YeungSenior Systems EngineerCommented:
in command line check which site your exchange server is belonging to

nltest /dsgetsite

and of course check your services if they are started.

if possible post the error message from event log.

check also machine logon server

echo %logonserver%

run gpupdate so then you can tell if server is talking to AD.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Miguel Angel Perez MuñozCommented:
I can not see DNS servers configured on Ethernet cards. Ensure your server has DNS configured (point to DC on this case).
0
AmitIT ArchitectCommented:
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.
0
loosainAuthor Commented:
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?
0
AmitIT ArchitectCommented:
192.168.80.100 is your dns server?
0
Justin YeungSenior Systems EngineerCommented:
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.
0
loosainAuthor Commented:
Ok. we just installed a new Server 2012 with a new installation of Exchange 2013 SP1.
Worked like a charm.
After uninstalling symantec from the client it automatically filled all fields when creating a new profil by using Email (system settings).
All hooks were green...
But if i start Outlook, it says that outlook could not started. Login error at exchange.
Same credentials in OWA working fine...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AmitIT ArchitectCommented:
0
loosainAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.