Solved

Event ID 7010 and 7004 between EX2003 servers

Posted on 2004-08-05
3
1,281 Views
Last Modified: 2012-08-14
Hi

We have two exchange servers here both are running exhange 2003 SP1 on windows 2003. The backend Exchange server is an enterprise server and the front end is a Standard version.

I have just installed this new front end server as the previous one got wrecked - its a long story.

I am now receiving these error messages :

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      SMTP Protocol
Event ID:      7010
Date:            05/08/2004
Time:            14:14:32
User:            N/A
Computer:      ENTERPRISE
Description:
This is an SMTP protocol log for virtual server ID 1, connection #37. The client at "xx.xx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first  ". The full command sent was "xexch50 1020 2".  This will probably cause the connection to fail.

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

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and on the front end server I get:

Event Type:      Error
Event Source:      MSExchangeTransport
Event Category:      SMTP Protocol
Event ID:      7004
Date:            05/08/2004
Time:            14:14:32
User:            N/A
Computer:      BILBO
Description:
This is an SMTP protocol error log for virtual server ID 1, connection #59. The remote host "192.168.20.40", responded to the SMTP command "xexch50" with "504 Need to authenticate first  ". The full command sent was "XEXCH50 1020 2  ".  This will probably cause the connection to fail.

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

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Also If look at the queues on the backend server I see that there is a queue for bilbo.xxxxxxxx.com and messages that have not been delivered. that are from enterprise-is@xxxxxx.com

I seem to remember reading a while back that you need to use ADSIEdit.msc to add the sending servers name i.e Domain\Computername$ to the SMTP virtual server object and give it SendAs permissons. Is this right?? I never received these errors with the old exchange server (also exchange 2003 std on win2003)

The other difference I noticed is that in the backend exchange queue there is no x400 entry for new server, like there was for the old server before we replaced the frontend exchange.

Anybody out there know how to resolve this?? I have done lots of googling and to no avail

Thanks

Rob
0
Comment
Question by:r_gibson
  • 2
3 Comments
 
LVL 21

Accepted Solution

by:
marc_nivens earned 250 total points
ID: 11730289
These errors are not usually problematic.  Regarding the queued messages, they would appear to be PF replication messages from the server enterprise to the server bilbo.  Since you're not even supposed to have a public store on the FE server, you can delete it and these messages will stop queueing.

Besides the PF messages and these events, are you having any noticable mail flow issues between these servers?
0
 

Author Comment

by:r_gibson
ID: 11751356
I have already deleted the public store as well as the messages on enterprise and I still get these messages.

We had a smarthost on the backend which was pointing to our mailsweeper machine. Since removing that smarthost I have also noticed that mail cannot flow from enterprise (backend) to bilbo (frontend) but can flow from bilbo to enterprise. It seems that this could be a permission problem???

Any ideas

0
 

Author Comment

by:r_gibson
ID: 11808679
Seems to have been sorted and settled down. Thanks for the advice marc_nivens
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…

770 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