Event ID 9236

[Stephen Pynn]

I keep getting this event on my remote exchange server. I can't seem to
track down the cause of the error. I can see the entry with adsi edit, I
just don't want to make thing worse by changing anything with that tool.
Any info would be greatly appreciated.

Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9236
Date: 8/14/2007
Time: 9:21:47 AM
User: N/A
Computer: BLALBANY1
Description:
Referral Interface received a request for the DNS hostname of the Exchange
server with legacyExchangeDN '/O=Barton and
Loguidice/OU=BARTON/cn=Configuration/cn=Servers/cn=BLMAIL1'. The returned
DNS hostname is 'blmail1.barton.local'.

For more information, click http://www.microsoft.com/contentredirect.asp.

Steve Pynn
IT Manager

[Ed Crowley [MVP]]

What version of Exchange? Do you have your SMTP virtual server configured
to use a different DNS server than the default for the network?
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Stephen Pynn" <py...@yahoo.com> wrote in message
news:OhW0Hcn3...@TK2MSFTNGP03.phx.gbl...

[Stephen Pynn]

Ed,

Thanks for getting back to me.

Server Info:
Exchange 2003 SP2 is running on server 2003 SP1 configured as a DC and is a
GC. The server is running DNS so the DNS configuration of the nic is
pointing to 127.0.0.1.
We have 2 Exchange servers: Main Office BLAMIL1 and our remote office
BLALBANY1.

I checked the to see if I have SMTP virtual server is configured to use an
alternate DNS and it is not.

The remote server BLALBANY1 is getting event error, the main office Exchange
server has no errors in the event log. This error started popping up around
a year ago. There has been no issues in email flow. I just want to see if
I can make this go away.

"Ed Crowley [MVP]" <curs...@mvpsnospam.org> wrote in message
news:OK5Bh5r3...@TK2MSFTNGP05.phx.gbl...

[Ed Crowley [MVP]]

I don't know what that error means. If it's important enough to you, then
you might want to place a support call with Microsoft PSS. If you do so,
please post back here with the results so we can all benefit.

--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Stephen Pynn" <py...@yahoo.com> wrote in message

news:OgvHtkE4...@TK2MSFTNGP04.phx.gbl...

[Stephen Pynn]

Thank you for taking a look. The error does not seem to be causing a
problem. I'm not sure if it's worth $250 to call MS on this or not. If I
find the answer I will definitely post it.

"Ed Crowley [MVP]" <curs...@mvpsnospam.org> wrote in message

news:OOesPWG4...@TK2MSFTNGP04.phx.gbl...

[www.bongovan.com]

Although this is reported as an Error in the Application log, it is actually generated by Exchange 2003 Diagnostics Logging. Go to Exchange System Manager -> Properties of the Exchange Server -> Diagnostics Logging -> MSExchangeSA and lower the logging level (or change to None if not required).