Troubleshooting Client Communication issue with symantec endpoint protection manager on windows 2008 server.
Created: 12 May 2009 | 2 comments
ISSUE
• Clients not communicating with Symantec endpoint protection manager.
• Server offline under help & support troubleshooting.
CAUSE
• The traffic on IIS port is been blocked by windows firewall.
SOLUTION
• Check the IIS port for Symantec Web Server.
• Create a firewall rule to allow traffic on port used by Symantec web server.
• Usually in windows 2008 server the traffic on port 80 would be allowed.
• If Symantec endpoint protection manager is installed on custom web site with some different port the communication will be blocked.
blog entry Filed Under:
About Security Community Blog
The Security Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Security community. Any authenticated Connect member can contribute to this blog. Filter by:
Blog Tags
Endpoint Protection (AntiVirus) 11.x Data Loss Prevention (Vontu) Tip/How to Endpoint Protection Small Business Best Practice Messaging Gateway 10.x Installing Basics Reporting Configuring Symantec Information Manager General Symantec Mobile Security 9.x and Earlier Features Security Risks Network Access Control Critical System Protection Upgrade Symantec Protection Suites (SPS) Control Compliance Suite Endpoint Encryption 12.x
Comments
You can also check the same
You can also check the same by running the below command in I.E
http://<serveripaddres>/secars/secars.dll?hello,secars
If it says OK then your client-server communication is reported to be working fine.
Rgrds,
SAM
custom website and port
Please note that many people have implemented SEPM on a custom website with a different port like 8014.
Then the URL should read:
http://<serveripaddres>:8014/secars/secars.dll?hello,secars
Would you like to reply?
Login or Register to post your comment.