Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Symantec caused Exchange 2013 to stop functioning

Posted on 2016-07-29
7
Medium Priority
?
52 Views
Last Modified: 2016-08-22
We have Exchange 2010 and 2013 SP1 running in the same environment for migration purposes. The server is 2012 R2 and once we installed symantec endpoint protection the migrated mailboxes no longer receive/send emails. After uninstalling SEP the problem is still there. The Exchange transport service will not start. After disabling all the receive connectors the service starts but cannot send mail. During migration the primary exchange (2010) relays mail to 2013 and 2013 relays mail back to 2010 to send. The connection between the two systems seems to be broken.

We have restored an older backup on the 2012 Exchange 2013 server and now the server is at 100% CPU useage. The services are all started but nothing is working.
0
Comment
Question by:Hodor
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 

Author Comment

by:Hodor
ID: 41735306
CPU at 100% solved, VM was set to a single processor. We still cannot send or recieve emails on the new exchange
0
 
LVL 5

Expert Comment

by:Eric C
ID: 41735354
I have no clue how to solve your problem, but I wanted you to know that every time someone holds the door for me, I shed a little tear.
1
 
LVL 16

Expert Comment

by:Todd Nelson
ID: 41735840
Did you set your exclusions so the AV tool doesn't break Exchange?  Also, McAfee used to block port 25 by default unless it was explicitly opened--maybe SEP is doing something similar.

http://exchangeserverpro.com/powershell-script-exchange-2013-antivirus-exclusions/

Personally, I would never recommend AV on an Exchange server with mailboxes.
0
Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 41735925
Did you really install Exchange 2013 SP1 and not something more recent?
If not, start by installing the latest cumulative update. Then reboot the machine.

Check if you can actually telnet to port 25 on the server.

As for the Symantec software doing what it does - that doesn't surprise me. Symantec's garbage AV has been providing me with a steady stream of consultancy work for over ten years.
0
 
LVL 29

Expert Comment

by:Dr. Klahn
ID: 41736151
My experience with Norton Symantec ... I have not yet seen a system that worked right after Norton / Symantec was installed.  These products hook deeply into the system and can never be completely removed even using the Norton Removal Tool.  Usually this manifests by breaking some aspect of networking.

Suggest that you restore the system from the most recent backup prior to installing Symantec, or if this is not possible, try to go back to the Restore Point you created just prior to installing Symantec.
0
 

Accepted Solution

by:
Hodor earned 0 total points
ID: 41737530
Turns out Issue was not related to Symantec. We installed 2013 SP3 because we already owned the software and we don't upgrade to the newest product without sufficient testing in real environments. This helps build a better support community in case issue arise. We ended up connecting Microsoft. Below is their resolution.

Issue Description
==========================
 
- Unable to send/receive emails getting error "4.7.0 Temporary server error. Please try again later. PRX4" on Exchange 2013 Server [EXCHANGE]
 
Issue Resolution
==========================
- Unable to Inbound proxy from Frontend to Hub Transport as Default Receive Connector's binding was set on Port 2525 & Transport Role was defined as “FrontendTransport” hence changed it to “HubTransport” & issue stands resolved
Related TechNet Article
==========================
 
Receive connector Exchange 213:  https://technet.microsoft.com/en-us/library/aa996395(v=exchg.160).aspx
0
 
LVL 5

Expert Comment

by:Eric C
ID: 41737562
Hodor.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

636 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