how can i open port 25 for backup exec notifications???

Hello

I need some help

I have backup exec, versions 9.1, 10d and 11d running on different sites and servers and i would like to set up email notfications on these.
I have correctly configured backup exec but there are issues in getting the email to send from the servers.

I have opened a call with symantec technical support who said backup exec was configured correctly but because port 25 on the servers was not open then

They said "I have done research on the issue and the only way to fix it is to open port 25. For same, we have to setup relay on exchange side so that both the servers can communicate over port 25, and for this you can consult your Exchange Admin. "

How do I open this port and set all of this up, is this best practice and is there another way of setting all of this up?

Current sites setups are that backup exec is installed on the DC whilst exchange is setup on a seperate server.

If you require any more information please contact me and hopefully we will be able to sort this issue out

Thanks in advance

peachplcAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
honmapogConnect With a Mentor Commented:
If you cannot be entirely sure that McAfee is not the problem, why not uninstalling it temporarily?
It does sound to me like McAfee is still the problem.
Can you telnet to the Exchange server on port 25 from a system that does not have McAfee installed?
0
 
honmapogCommented:
Follow the procedure in http://searchexchange.techtarget.com/general/0,295582,sid43_gci1280938,00.html to use telnet to test port 25. If you get a response to the telnet command on port 25, then port 25 is open.
If not, check firewalls or antivirus programs on the DC and Exchange server - or in between both servers.

If the telnet works, check relaying information inside Exchange - you may have to configure Exchange to allow relaying for the DC. http://www.microsoft.com/technet/security/prodtech/exchangeserver/excrelay.mspx may help.
0
 
peachplcAuthor Commented:
Telnet does not work to port 25 on either machine, one has got no antivirus on at all and the other has McAfee Antivirus Enterprise 8.5.

Do you have any other ideas as to what it could be.

I have ran a piece of software that gives me a list of open ports but port 25 isnt there on either
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
honmapogCommented:
Your McAfee AntiVirus Enterprise version prevents the use of port 25. See http://security.ittoolbox.com/groups/technical-functional/mcafee-virusscan-l/mcafee-scan-preventing-sending-emails-1576803 on how to turn this off.
0
 
peachplcAuthor Commented:
It only prevents backup exec 11d from sending emails, exchange sends them fine. Seems like no one can help me with this, Symantec have been through all the settings on all my servers running BE and they all check out, what to do next?
0
 
honmapogCommented:
Is McAfee AntiVirus Enterprise installed on the Backup Exec server? If so, make sure it does not block port 25 on the Backup Exec server as per above article http://security.ittoolbox.com/groups/technical-functional/mcafee-virusscan-l/mcafee-scan-preventing-sending-emails-1576803. Please confirm.
0
 
peachplcAuthor Commented:
I have created a new policy using Mcafee and taken the "Prevent mass mailing worms from sending mail" out but I still have the issue
0
 
honmapogCommented:
Can you still not telnet from the BE server to the Exchange server on port 25 either?
0
 
peachplcAuthor Commented:
i cant telnet no, i was having some error on mcafee but i have got rid of all them now. I cant be entireley sure that mcafee isnt the problem. The logs arent recording anything so im assuming they can get through that. I just wonder what else it could be.

BTW exchange is running fine on this and sends and recieves so im not sure what is wrong.

0
 
peachplcAuthor Commented:
McAfee was to blame, it was the ePO servers fault in the end, misconfiguration on our side on a new server we have aquired. Thanks for your help
0
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.