Symantec Endpoint Protection Manager

Symantec Endpoint Protection Manager. We, the people i work with, are trying to install this on our SLAN (secret lan which will now be referred to as STTN or STTNDC2) and we're encountering a problem that apparently MANY people have encountered before.

The problem, once we install it, and then run the setup wizard to create the login and everything, reboot the server, everything works fine EXCEPT the fact that the actual service doesn't start. If we go into services and start it (its suppose to start automatically but the following explains why we have to start it manually, or try to anyway) and it will start for about...3 seconds...if we're lucky, and then stop.

Here are a couple of cases, as I've called them, where OTHER people have had the same issue.

Case 1

Case 2

Here are some of the MANY things we've tried to trouble shoot this problem.

Trouble shoot #1

Hmm...well i was able to find a couple more things from my work computer...now i can't >.< anyway...if you name it, chances are we've tried it. only thing we haven't done and probably will not do no matter what is rebuild the server...

sttndc2, i believe, has windows server 2003, don't quote me on it. The only thing the network itself is used for is to allow users in the 3 buildings we work in to be able to deal with classified information without having to go through NMCI. That's as simple as i can put it. There is no internet, the only thing it can access is our local website. No exchange server. just dc1 dc2 and a couple other things that dont matter. tryin to install on sttndc2.

Any insight, suggestions...ANYTHING would be awesome. I've read some places that people have troubleshot this for 1 month+ and couldn't figure it out. And its pissing everyone off at work because we're all IT's and we can't figure it out. LOL.

 

It looks to me like the new service is trying to use a port that is already being used by another service. For example, if you already have IIS running a web service (by default it serve its web root on port 80, when you install it) and this new service also wants to use port 80, you'll get the symptoms you describe.

What port does the Symantec system use?