Event ID's 7010, 7002 and 3017

On my Exchange 2003 server I m having 3 Event ID errors I can t solve. The ID s are 7010, 7002 and 3017. The ID of 3017 concerns me the most. We have 2 front end servers and two back end servers. The error is happening on EXBE01
For the 3017 event ID error I have checked that no DNS internal or External are setup.  Under routing groups connectors there are 3 connectors and they have EXBE01 as the Default SMTP server.  And it s setup to use DNS to route to each address space on this connector.
Below are the SMTP Virtual server the Fully-qualified Domain name
Front end servers
EXFE01   exfe01.domain.local
EXFE02   exfe02.domain.local
Back End servers
EXBE01   mail.emaildomainname.org
EXBE02   mail.emaildomainname.org
Who is Participating?
SembeeConnect With a Mentor Commented:
Did you make the change that I have outlined in my first response?
Having both servers with the same FQDN on the SMTP virtual server is not a good idea and it will cause problems.
Unless you have a good reason not to, I would suggest that you configure SMTP Connectors to route email out through the frontend servers. Then ensure that the frontend servers have their own DNS names, with matching reverse DNS entries etc.

Error IDs are useless on their own.
You need to post the full error message.

However if you have routing groups the entry on the SMTP virtual server under FQDN becomes important.
That can be resolved by changing the SMTP IP address setting from All Unassigned to the specific IP address of the server. Then recreate the routing group connectors.

soupy66Author Commented:
First  event ID error 3017
A non-delivery report with a status code of 5.3.5 was generated for recipient rfc822;email@Domain.com (Message-ID  <OF062D1F8C.F533AC92-ON85257368.003F14CD-85257368.003F1F14@rohmhaas.com>).  
Causes: A looping condition was detected. (The server is configured to route mail back to itself). If you have multiple SMTP Virtual Servers configured on your Exchange server, make sure they are defined by a unique incoming port and that the outgoing SMTP port configuration is valid to avoid looping between local virtual servers.    
Solution: Check the configuration of the virtual serverÆs connectors for loops and ensure each virtual server is defined by a unique incoming port.

I've checked the setting for the solution I found and still receive this error.
soupy66Author Commented:
This can be close as we can't make any changes until December as thats a slow month and this is are busy month.
Oh thats no good, I was having the same issue - and was monitoring the posts
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.