RE: Event ID: 2501

That Key looks good.

Can you add the following Registry key.

HKLM\Software\Policies\Microsoft\Netlogon\Parameters

Create a key for SiteName and provide the proper site name.

Now restart the Netlogon.

Also check NIC binding order whether the one with DNS is at the top. And
also what is the use of second NIC card with out DNS entries. If possible
gateways and DNS and uncheck the settings for registering it in DNS.

check nltest /dsgetsite

Now restart ADTopology Service.

check for errors again.



"Dagre" wrote:

Hi ashwin,

New findings. nltest produces intermittent proper responses. In your
suggestions you mentioned the key SiteName. In that path, the key is named
DynamicSiteName. Is that the same thing?

"Dagre" wrote:

Thanks for writing. When I run dsgetsite it reports back properly. This is
an Exchange only server the is in the Default-First-Site. In AD Sites and
Services the subnet is defined. The only thing unusual about this server is
that it has a second NIC that is configured with only a IP and Subnet. No
Default Gateway, DNS or anything else. It is used to connect to a backup
server. Could these errors have to do with that?

"Ashwin" wrote:

Run
nltest /dsgetsite

if this errors out, then it means it is having issues with site name.

Now make sure only internal DNS servers are listed in th NIC card of
Exchange Server. and also subnet of Exchange is added in AD Sites and
Services to appropriate Site.

Now again run nltest /dsgetsite.

look for below registry.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\SiteName

Remove the sitename key and restart the Netlogon Service or servver.
If you remove the SiteName registry value, Windows automatically joins the
appropriate Active Directory site.

Now try to restart Microsoft Exchange AD Topology Service (if Exchange 2007)
or Microsoft Exchange SystemAttendant service (if exchange 2000/2003).

Again check nltest /dsgetsite.

This should show a proper site name. And issue should get resolved.

Regards,
Ashwin


"Dagre" wrote:

We constantly get the following error:

***********************************************************
Process MSEXCHANGEADTOPOLOGY (PID=3792). The site monitor API was unable to
verify the site name for this Exchange computer - Call=DsGetSiteNameW Error
code=800703e5. Make sure that Exchange server is correctly registered on the
DNS server.
************************************************************


We have checked DNS and there is no trouble finding the Exchange server.
Used ASDI edit to check permissions as suggested in the text below:

***********************************************************
Configuration Container > Sites > "The site which the Exchange Server
is installed"

Right click on the Site > Properties > Security Tab

Ensure that Authenticated Users has Read Permissions to the Site, this
will allow the local system account to read the Site information, and
then populate the following entry:

Configuration Container > Services > Microsoft Exchange > "Your
Organization Name" > Administrative Groups > "Your Administrative
Group" > Servers > Server Name

Right Click Server Name > Properties

Look for the following Attribute, it should be set to the following:
CN="Your AD Site Name (ie: default first site
name)",CN=Sites,CN=Configuration,DC="Your Domain Name",DC="Your Domain
Name Suffix (ie: com)"
If the Authenticated Users group does not have read permissions to all
AD Sites which Exchange 2007 will be installed, you're going to have
issues

************************************************************
All seems to match as suggested. We've run the Exchange Best Practices
Analyser and passed all the scans available there. Are there any other
diagnostic utilities that might point us to the problem?
.

Relevant Pages

  • RE: Event ID: 2501
    ... The nltest response seems stable now. ... Can you add the following Registry key. ... an Exchange only server the is in the Default-First-Site. ...
    (microsoft.public.exchange.admin)
  • RE: Event ID: 2501
    ... Can you add the following Registry key. ... Also check NIC binding order whether the one with DNS is at the top. ... an Exchange only server the is in the Default-First-Site. ...
    (microsoft.public.exchange.admin)
  • Re: OWA Access Problem
    ... See if it outlines the following, which can cause a 400 bad request for OWA ... users on an Exchange Backend: ... Exchange Server Analyzer Tool reads the following registry ... The Exchange Server Analyzer also examines the following registry entry to ...
    (microsoft.public.exchange.admin)
  • Re: OWA Access Problem
    ... See if it outlines the following, which can cause a 400 bad request for OWA ... users on an Exchange Backend: ... Exchange Server Analyzer Tool reads the following registry ... The Exchange Server Analyzer also examines the following registry entry to ...
    (microsoft.public.exchange.admin)
  • RE: Event ID: 2501
    ... nltest produces intermittent proper responses. ... an Exchange only server the is in the Default-First-Site. ... This should show a proper site name. ...
    (microsoft.public.exchange.admin)
Loading