Exchange Server

Guest

I have this problem with the current and last previous version of
ExBPA. I am in a multi site Exchange Org and this is happening on both
sites (both Administrative Groups).

I have this on problem reported on every exchange server:

"Active Directory server for DSAccess

An error occurred during round trip calculation between Exchange server
[servername] and Active Directory server [DCName]. The ping command
returned the error '11010'"

The advanced help on this subject reveals this simply means "Request
timed out".

However, I am able to ping all the DC's from all Exchange servers using
the default 32 byte packets as well as "ping -l 4096 -n 6 [servername]"
as has been suggested in some other topics on this board. The DC's and
Exchange servers are all on the same domain by the way.

I have tried DCDIAG /S:[DCName] from my Exchange servers to all the
DC's, and they pass all tests. NETDIAG passes all the tests it should
pass. All the services that should be running on both the DC's and the
Exchange servers are all running.

My questions:

Why is ExBPA reporting this error, and how can I recreate what it is
trying to do?
I am not noticing any unusual problems. Should I be worried about this?

Thanks,
Ben Stokes

Paul Bowden [MSFT] · Guest

Hi Ben,

ExBPA calls the Win32_PingStatus WMI class and looks at the returned
response time and status. Here's a VBScript that simulates the ExBPA logic.
Snip this into a .vbs file, change MYADSERVER to the name of the domain
controller that ExBPA is reporting, then run the script on the Exchange
server. If you don't want to run it on the Exchange server, change the "."
in strComputer to the name of your Exchange server, then you can run it from
a workstation.

=======================================
On Error Resume Next
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_PingStatus where
Address='MYADSERVER' and BufferSize=4096",,48)
For Each objItem in colItems
Wscript.Echo "ResponseTime: " & objItem.ResponseTime
Wscript.Echo "StatusCode: " & objItem.StatusCode
Next
=======================================

As you mention in your message, a PING with a 4096 buffer size should also
simulate the same action. To answer your question, if you're not seeing any
problems on the Exchange server, and the large PING works, then I wouldn't
been too concerned.

Cheers,
--
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers

This posting is provided "AS IS" with no warranties, and confers no rights.

<benstokes1@gmail.com> wrote in message
news:1134657789.841245.325750@g49g2000cwa.googlegroups.com...

Guest

Paul,

I appreciate the reply. I ran the script on one of my Exchange servers
and the result was:

"ResponseTime: 1"

I won't worry about this then if it's only a large ping, as manual
pings using the same buffer size are working ok each time I test.

Thanks,
Ben Stokes

	Exchange Server Forum Index -> Clients	All times are GMT
Page 1 of 1