asked on 7/15/2015

exchange 2010, Active directory

I am getting error on my exchange server -HIGH LDAP search time .sustained for 2 minutes .yellow (>100 milliseconds)

what should I do, should I ignore

Active Directory Exchange

Last Comment

Scott C

7/15/2015

Will Szymkowski

7/15/2015

Did this event just start happening? How many DC do you have in the site where Exchange is hosted? Basically it is stating that it cannot keep up to the queries that users are requesting. I would check to see what your DC are doing and make sure that they have available resources as well (CPU and memory). You should also check and make sure the you network latency is also good.

Checking DC replication also wouldn't hurt. Probably not a good idea to just let this go. Are your clients complaining?

Will.

pramod1

7/15/2015

ASKER

this error was generated 3 hrs back and is from exchange relay server

pramod1

7/15/2015

ASKER

how do I check network latency

Will Szymkowski

7/15/2015

A simple ping can show the network latency. You can also use pathping as well.

I personally think it is to do with the resources on the DC's

Will.

pramod1

7/15/2015

ASKER

what should be ldap normal search time

pramod1

7/15/2015

ASKER

as I did tracert to google.com , all hops show less than 30 ms

pramod1

7/15/2015

ASKER

what should be ldap normal search time , all dc are in site

pramod1

7/15/2015

ASKER

if tracert is less than 25ms , what should be the ldap search time?

Will Szymkowski

7/15/2015

you get 25ms on the same LAN? That seems high.

Or is this over a MPLS or IPSec VPN?

What about the resources on the DC's?

Will.

ASKER CERTIFIED SOLUTION

Scott C

7/15/2015

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

pramod1

7/15/2015

ASKER

tracert to google took less than 10ms

Scott C

7/15/2015

Just saw you accepted my solution.

Glad to have been able to help you so quickly.

When I was an Exchange Escalation engineer for MS this was the first thing we did when seeing high LDAP times.