Backup Exec 12 Not Sending Email Notification through Exchange 2007
#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required
Diagnostic information for administrators:
Generating server: exchange.yourdomain.local
#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##
Original message headers:
When you're encountering a problem sending Backup Exec 12 email notification alerts through an Exchange 2007 server, check the following
Test that you can access port 25 (SMTP port number) on the Exchange server by using telnet.
telnet ip-address-of-exchange-server 25
ehlo domainname.gr
mail from:backup@domainname.gr
rcpt to:administrator@domainname.gr
data
backup exec
.
Your will then get a confirmation the mail has been queued for delivery
If the mail gets delivered you know port 25 in not blocked or restricted in any way you have permission to send e-mail.
If you do not connect, check to see if there is any software blocking the connection like software or hardware firewalls. Antivirus programs now come with firewall features to stop worms from sending out email from the computer they are infecting. Stop the services and try again. Once you have successfully telneted and sent the test email but backup exec still does not send email notifications then check the following.
The Backup Exec software might not be authenticating properly so be sure you have used an actual real email address with an active domain account as the sender address. The name is a description and can be anything but the email address has to an account in the domain - Exchange wants it that way. If you already have an active domain account as the sender address in backup exec, like administrator@domainname.gr, check the account's inbox and look for NDR (non-delivery reports as they may provide an important clue to why your email not being delivered.
Other tools that are handy to utilize when troubleshooting this problem is the the transport receive logs in exchange, they will determine if the email has even been received by the exchange server. When email is accepted into the Exchange email organization by the transport server (it could be the same server as the mailbox server), it will be logged. A simple log generated by exchange is very useful for problems such as this one.
Another tool I often used for determining if a program is trying to communicate information to another system over the network is a simple little program call Active Ports. This is a free program hat show you the running processes and what they are doing in terms of sending or receiving data. It has a very small foot print and installs in seconds so it is worth a look at. You can accomplish the same thing with a command line command but this GUI based tool gives you nearly realtime information which is important for something like SMTP send that could take only less than a second to occur.
The NDR information shown at the top of this email is an example of what someone was getting when they called for assistance. After going through the regular trouble shooting options as discussed above for determining the problem. If you are reading this you most likely have Symantec Backup Exec 12 and Exchange 2007. The way Backup Exec sends their email notifications has not changed in years and version 12 or 12.5 has also not changed. the new culprit is Exchange 2007. There are some additional security options included in the groups and users that are implemented through the domain schema update that has to be run in order to install Exchange 2007. One of those new options is in the domain group properties especially if you are using a distribution list to send the notification to. Uncheck the option to authenticate all users in group. That was the cure for the problem described in the NDR report shown at the beginning of this blog.
Microsoft Exchange email delivery issues as well as issues on the client side can be resolved using online remote support software. Online remote support accounts for a majority of help-desk solutions. Microsoft Exchange can be repaired remotely as well as email clients like Micrsooft Outlook.
#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required
Diagnostic information for administrators:
Generating server: exchange.yourdomain.local
#550 5.7.1 RESOLVER.RST.AuthRequired; authentication required ##
Original message headers:
When you're encountering a problem sending Backup Exec 12 email notification alerts through an Exchange 2007 server, check the following
Test that you can access port 25 (SMTP port number) on the Exchange server by using telnet.
telnet ip-address-of-exchange-server 25
ehlo domainname.gr
mail from:backup@domainname.gr
rcpt to:administrator@domainname.gr
data
backup exec
.
Your will then get a confirmation the mail has been queued for delivery
If the mail gets delivered you know port 25 in not blocked or restricted in any way you have permission to send e-mail.
If you do not connect, check to see if there is any software blocking the connection like software or hardware firewalls. Antivirus programs now come with firewall features to stop worms from sending out email from the computer they are infecting. Stop the services and try again. Once you have successfully telneted and sent the test email but backup exec still does not send email notifications then check the following.
The Backup Exec software might not be authenticating properly so be sure you have used an actual real email address with an active domain account as the sender address. The name is a description and can be anything but the email address has to an account in the domain - Exchange wants it that way. If you already have an active domain account as the sender address in backup exec, like administrator@domainname.gr, check the account's inbox and look for NDR (non-delivery reports as they may provide an important clue to why your email not being delivered.
Other tools that are handy to utilize when troubleshooting this problem is the the transport receive logs in exchange, they will determine if the email has even been received by the exchange server. When email is accepted into the Exchange email organization by the transport server (it could be the same server as the mailbox server), it will be logged. A simple log generated by exchange is very useful for problems such as this one.
Another tool I often used for determining if a program is trying to communicate information to another system over the network is a simple little program call Active Ports. This is a free program hat show you the running processes and what they are doing in terms of sending or receiving data. It has a very small foot print and installs in seconds so it is worth a look at. You can accomplish the same thing with a command line command but this GUI based tool gives you nearly realtime information which is important for something like SMTP send that could take only less than a second to occur.
The NDR information shown at the top of this email is an example of what someone was getting when they called for assistance. After going through the regular trouble shooting options as discussed above for determining the problem. If you are reading this you most likely have Symantec Backup Exec 12 and Exchange 2007. The way Backup Exec sends their email notifications has not changed in years and version 12 or 12.5 has also not changed. the new culprit is Exchange 2007. There are some additional security options included in the groups and users that are implemented through the domain schema update that has to be run in order to install Exchange 2007. One of those new options is in the domain group properties especially if you are using a distribution list to send the notification to. Uncheck the option to authenticate all users in group. That was the cure for the problem described in the NDR report shown at the beginning of this blog.
Microsoft Exchange email delivery issues as well as issues on the client side can be resolved using online remote support software. Online remote support accounts for a majority of help-desk solutions. Microsoft Exchange can be repaired remotely as well as email clients like Micrsooft Outlook.
