No Exchange Server object found for server_name on domain controller

Posted on 2004-11-18
Last Modified: 2012-08-14

What does it mean "No Exchange Server object found for server_name on domain controller, server_name is an external server (not in the Exchange Org)."
Does this relate to Event id 2012 smtpsvc error messeges I am getting in my event log.

When I run a dnsdiag on my exchange server I get the following results:

Running in debug/verbose mode.
The DNS flags are not explicitly set in the metabase, assuming default flags - 0
These are the local IP addresses (server-bindings)
Microsoft Exchange is installed on this machine.
Querying domain controller for configuration.
The domain controller server which will be used for reading configuration data i
s ndc01.nwmls.loc
Connecting to ndc01.nwmls.loc over port 389
configurationNamingContext is "CN=Configuration,DC=nwmls,DC=loc"
This will be used as the Base DN for all directory searches.
Checking if the target server exchange is an Exchange server
Searching for an Exchange Server object for exchange on the domain controller
No Exchange Server object found for exchange on domain controller, exchange is an external server (not in the Exchange Org).
Checking on DC if the VSI being simulated is configured with external DNS server
Searching for an Exchange Server object for exchange.nwmls.loc on the domain con
LDAP search returned some results, examining them.
Examining next object for attributes we are interested in.
Successfully read the distinguishedName attribute on the Exchange Server object.
 The value of the attribute is CN=EXCHANGE,CN=Servers,CN=First Administrative Gr
oup,CN=Administrative Groups,CN=NwmlsMail,CN=Microsoft Exchange,CN=Services,CN=C
The search returned the following 6 values for the networkName attribute for the
 Exchange Server object for exchange.nwmls.loc
Attempting to match the TCP/IP networkName of the Exchange Server object returne
d from the domain controller against the FQDN we are searching for
0> networkName: ncacn_vns_spp:EXCHANGE...match failed
1> networkName: netbios:EXCHANGE...match failed
2> networkName: ncacn_np:EXCHANGE...match failed
3> networkName: ncacn_spx:EXCHANGE...match failed
4> networkName: ncacn_ip_tcp:exchange.nwmls.loc...match succeeded
exchange.nwmls.loc is an Exchange Server in the Org.
DN for the virtual server is "CN=1,CN=SMTP,CN=Protocols,CN=EXCHANGE,CN=Servers,C
N=First Administrative Group,CN=Administrative Groups,CN=NwmlsMail,CN=Microsoft
The attribute msExchSmtpExternalDNSServers was not found on the SMTP virtual ser
ver being simulated.
No external DNS servers on VSI. Using global DNS servers.
Using the default DNS servers configured for this computer.
Created Async Query:
        QNAME = exchange
        Type = MX (0xf)
        Flags =  UDP default, TCP on truncation (0x0)
        Protocol = UDP
        DNS Servers: (DNS cache will not be used)

Connecting to DNS server over UDP/IP.
Connected to DNS over UDP/IP.
Response received from DNS server.
Received DNS Response:
        Error: 9002
        Description: Not available.
Querying via DNSAPI:
        QNAME = exchange
        Type = A (0x1)
        Flags =  No flags, (0x0)
        Protocol = Default UDP, TCP on truncation
        Servers: (DNS cache will be used)
        Default DNS servers on box.

Received DNS Response:
        Error: 0
        Description: Success
        These records were received:
        exchange.nwmls.loc    A

No CNAME records in reply.
Checking reply for A record for exchange
1 A record(s) found for exchange
Local host's IP is one of the target IPs.
Discarding all equally or less-preferred IP addresses.
DNS configuration error (loopback), messages will be NDRed.
Local host's IP address is the most preferred MX record.
Shutting down ATQ
Shutting down IISRTL
Exit code: 4
Question by:logiksnac
    LVL 104

    Expert Comment

    I think this is the key:
    "... server_name is an external server (not in the Exchange Org)."

    Have you got any external DNS servers configured anywhere in the network configuration on the Exchange server? If so, they need to be removed. An Exchange server MUST use ONLY Domain Controllers for DNS.


    Author Comment

    The way I read it is Exchange (the name of the email server) is an external server not in the exchange org. Which seems strange as it is the exchange org. But no, the only DNS servers referenced in the exchange both for the TCP/IP settings and the smtp virtual server is the local dns servers. I am concerned that this is related to Active Directory as I had at one time installed Exchange, removed it from the domain and reinstalled it (I did follow the MS KB article on it though). I wonder if there are some lurking hidden items related to this. But I cannot tell, the only clue I have is the dnsdiag util stating that messege and tons of event id 2012 and 2013 ( I have proactively added dnscmd server /config /enableednsprobes 0 and enabled larger dns packet sizes on my pix.)
    LVL 104

    Expert Comment

    When I first read the messages I thought it was a simple Exchange not talking to the domain correctly. That was my first instinct, until I picked up that message above.
    Have you looked at the Exchange objects in ADUC to ensure that they refer to this live server only? You may have to enabled the advanced options in ADUC to see them.

    When you reinstalled Exchange, did you forestprep and domainprep again? It cannot do any harm to do those again anyway. Do it using the Exchange CD but on a domain controller.

    Any errors on the DCs?


    Author Comment

    Yes, I did a forestprep and domainprep at time of reinstall. Will do again to see if it helps. No errors on the DCs. I look in the ADUC, I do not see what you mean by what Exchange objects and how they refer to the live server only? I see Microsoft Exchane System Objects, but they have no real properites or pointers. I have used the dcdiag on each server but they have all passed. Any other AD tools to check the health of my AD? I have used the Exchange Best pratices tool with no errors as well.


    LVL 104

    Expert Comment

    To be honest I am not sure what I wrote there either. It was the end of the day on Friday (I am in the UK) and my brain was probably fried.

    Need to see whether the forest and domain prep resolve anything. Exchange has been known to operate for a little while with incomplete domain objects. Make sure that you give it enough time to replicate everything.

    Whiz through this Q:
    Some of the issues are very similar.


    Author Comment

    OK, here is the recent rundown:

    I ran dnsdiag exchange -d -v 1 which provides the results that started this conversation:
    No Exchange Server object found for exchange on domain controller, exchange is an external server (not in the Exchange Org).
    Checking on DC if the VSI being simulated is configured with external DNS servers.
    No external DNS servers on VSI. Using global DNS servers.
    Received DNS Response:
            Error: 9002
            Description: Not available.

    Trying to find out what the above means about my dns and AD stability and if it relates to any Exchange issues.

    To resolve I have so far done the following:
    Ran Forestprep again - no problem
    domainprep - no problem
    nslookup - no problem
    smtpcheck - no problem
    have no internet message filter
    netdiag - no problem
    Exchange best practice tool - no problem
    I also ran support\exdeploy\exdeploy.exe /gc:global catalog server name /t:orgprepcheck  - no problem
    Event viewer on DCs - no error
    Event viewer on Exchange - Event ID 2012 and 2013 sporadically . Have applied the appropriate changes to help fix this via microsoft knowledge base, so we shall see.
    added dnscmd server /config /enableednsprobes 0 to all dns servers to use tcp not udp to try to enable issues with dns resolution and email
    added fixup protocol dns maximum-length 1024 to pix firewall to enable larger than default 512 dns requests and replies, to try to help with email issues

    It was a good article and I have tried its suggestions as well as a few others and found nothing that resolves or explain it.

    I am wondering if these are valid error messages and how to fully check the stability of AD and Exchange. I have no specific issues, just random ghosts and gremlins. It is a new AD2003 and Exchange 2003 install and setup separately, not migrated.

    Hopefully not too much information.

    Thanks for help and suggestions.
    LVL 104

    Accepted Solution

    I have tried very hard over the last week to replicate the error message - and have failed.
    What does this mean for you? To be honest I don't really know. Without hard evidence of a failure elsewhere it could be a false positive message. I cannot find much in Google about it, so it isn't something that is seen often, or people aren't running the test.

    Personally if Exchage/AD is working correctly then I would leave it to get on with it.
    Otherwise the only option I can come up with is to call MS.


    Author Comment

    Well thank you for all your research and suggestions. I could not find anything either, which is why I thought I would post. As there are not any blatant issues I can point to I will take the false positive message. Hopefully the gremlins will calm down over time, or become a more identifiable, replicatable problem.

    Thanks again.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Learn more about how the humble email signature can be used as more than just an electronic business card. When used correctly, a signature can easily be tailored for different purposes by different departments within an organization.
    Granting full access permission allows users to access mailboxes present in their database. By giving full access permission one can open and read the content of any mailbox but cannot send emails from that mailbox.
    In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
    This video discusses moving either the default database or any database to a new volume.

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now