Hi guys,
I'm becoming pretty desperate on this one.
I have an Exchange setup in two sites with one Namespace - mail.company.com:
Site A - 192.168.50.0/24
- Server A = Server 2012 with AD Services (PDC)
- Server B = Server 2012 with Exchange 2013 CU3
Site B - 192.168.60.0/24
- Server A = Server 2012 with AD Services
- Server B = Server 2012 with Exchange 2013 CU3
The Sites are connected via IPsec VPN and AD sync works like a charm.
But when I run a cmdlet like "Get-OwaVirtualDirectory" on any of the two servers, it displays the information of the local site and then spins and spins and spins for about 30 minutes. Then it finishes and displays the remote site information.
This is the case in almost EVERY cmdlet that is fetching or setting information from or to a remote site. For example: I can set a certificate for a service on both servers in both directions in a blink of an eye ... changing a virtual directory url
on the other hand takes 30-40 minutes.
Does anyone have a clue what this could cause?
Greetings,
Vasko
Edit: I've set the LogLevel to Expert and both exchange servers are getting the following Warning:MSExchange ADAccess ID 2128
Process MSExchangeHMWorker.exe (ExHMWorker) (PID=6268). Object CN=Configuration,DC=domain,DC=xxx was not found on the Domain Controller ServerA.domain.tld. This may indicate a replication or permission issue.
Same Warnings exist for other executables. I checked the DCs: No replication/sync or DFRS Errors.