Endpoint Protection Small Business Edition

I have gotten everything restored, the database and manager running properly, and they correct keystore installed (Same as the creation time of the domain).  All thanks to the Connect community, thanks!

One last issue:
Now that the server is happy, none of my clients are connecting.  After checking the DomainID on my clients, and the server, they are matching.  The SyLink.xml page points to the correct server, IP, and Domain.
On startup, the RADIUS server said it could not start because of the port 1812 being used.  A quick netstat revealed a machine on my network using it, which I quickly cut off.  It was just a client machine.
I know the database is correct, just none of my clients are connecting to the Manager.

Thanks again for all the great support from the community!

 After restoring the Database and Keystroke
In SEPM -Clients - Right Click on My Company - Run command on group - Update content.

Wait for some time and then check if the clients are updating .

One more thing right now your SEPM might have been installed on port 8014 in IIS. Was it installed on 8014 earlier as well or on 80.Look in the sylink and check if you find 8014 or not.

Checked the sylink on the manager, and it has HttpPort="8014"

Forgive me, as I was kind of thrown into this position, but does this need to be changed, and where?

virkram wants you to check the port number of symantec webserver in IIS
is that 8014 ?? or 80 ?? 

Sorry, that took me a minute to find.  Not 100% familiar with some things yet.

TCP port: 8014 in IIS for Symantec Web Server.

do you have firewall enbled on the server on client?
can you run secars test and let us know the results.?
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101711140148

check this

https://www-secure.symantec.com/connect/forums/clients-not-comunicating-after-reinstall#comment-3396761
 

Secars responds OK.

I also found https://www-secure.symantec.com/connect/sites/default/files/SylinkReplacer.pdf
Is it possible that this may help?  I see VK was all over that one last week.

Sorry, Vikrum Kumar.  Got overzealous with my acronyms.

 Yes it might.
however to see if that will help or not manually replace the sylink on any client.If you get the green dot then go ahead and run the sylinkreplacer utility.

Copy sylink from any one of the folders from
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\.

then start - run -> smc -stop
replace the sylink
smc -start
check if it gets the green dot.

If yes then run the sylinkreplacer utility.

Green Dot.  Going to run the utility now.  I'll let you know/mark solved afterward.

Now the key will be to run it almost every day for two weeks to catch up with machines that might be off at the time! haha.  Probably just write a .bat script for it.