Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Connection problem between SEP and SEPM

Updated: 21 May 2010 | 17 comments
sscfss's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi,

I had to uninstall and reinstall completly SEPM and SEP (clients).
Since this reinstall, no one could communicate with my SEPM (installalled on a SBS 2003 SP2, with 4GB RAM).

I join the Sylinkmonitor file to this message.
Could someone help me in reconnecting the client to the SEPM? BTW, the clients are shown as connected in SEPM, but not on the client machine.

Thanks in advance.

Comments

AravindKM's picture
17
Nov
2009
0 Votes 0
Login to vote

try this

Troubleshooting Client Communication 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

sscfss's picture
17
Nov
2009
0 Votes 0
Login to vote

Thank you for your fast

Thank you for your fast answer.
I have already try that.
Did my log (sylink.txt) (upper), gives you some more information?
I have no idea of what to seek... But I am on this problem since 2 days...
Thanks for your help.

Secars, test ok,
Communication with server: ok
Sylink file already change

AravindKM's picture
17
Nov
2009
0 Votes 0
Login to vote

Any proxy you are using ? Try

Any proxy you are using ?
Try by removing it (both in server and client) 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

AravindKM's picture
17
Nov
2009
1 Vote -1
Login to vote

Remove Internet explorer

Remove Internet explorer enhanced security configuration also..
 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Farzad's picture
17
Nov
2009
0 Votes 0
Login to vote

AravindKM! The solution is

AravindKM!
The solution is not related

Symantec Certified Specialist  \  MCSE +Security  \  CCNSP

pete_4u2002's picture
17
Nov
2009
1 Vote +1
Login to vote

from the logs Signature

from the logs

Signature verification FAILED for Index File Content..
11/17 12:48:01 [4228] <GetIndexFileRequest:>RECEIVE STAGE COMPLETED

Check this solution guide and check if it resolves your issue

http://service1.symantec.com/support/ent-security.nsf/docid/2007111311223900

Farzad's picture
17
Nov
2009
2 Votes +2
Login to vote

Have you imported the Server

Have you imported the old Server Private Key?
Seemingly you haven't!
Please let us know if you have done so. 

Symantec Certified Specialist  \  MCSE +Security  \  CCNSP

AravindKM's picture
17
Nov
2009
0 Votes 0
Login to vote

 hi Farzad he is created an

 hi Farzad he is created an new sylink file from his newly installed SEPM and replaced in the client.Then what is the requirement of old Server Private Key?

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

sscfss's picture
17
Nov
2009
0 Votes 0
Login to vote

AravindKM: I am not using any

AravindKM: I am not using any proxy. The client on my SBS 2003 server is not working too (communication, I mean).

Pete_4u2002: Thanks for your proposal. I try it, but it did not work. Sorry
The client in SEPM was deleted and after a "smc -stop" then "smc -start" on my client, my machine is back in the SEPM group.

Farzad: I have not imported the old server private key. Is it important and how must I do.
Note that I have deleted all old group and recreate new one for my server and my computers.

Thanks for your help again.

AravindKM's picture
17
Nov
2009
0 Votes 0
Login to vote

 hi sscfss can you tell upto

 hi sscfss
can you tell upto now what are the things you done?
After reinstalling the old SEPM do you restored that old database?
Any keys (server.xml,kestore.jks) you restored?
You are telling Communication with server: ok means you are getting green dot in SEPM console and in client?
Whether you tried by disabling windows firewall? 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

sscfss's picture
17
Nov
2009
0 Votes 0
Login to vote

Hello AravindKM, So I have

Hello AravindKM,

So I have done:

After reinstalling the old SEPM do you restored that old database? 
yes

Any keys (server.xml,kestore.jks) you restored?
 No key restored. What could I do or should do? (all clients were reinstalled with the SEPM console).

You are telling Communication with server: ok means you are getting green dot in SEPM console and in client?
I mean, that I am able to communicate with Secars, Exchange, etc on my SBS server.
An interesting things, is that in SEPM, my client are "green doted", but not on the client. The communication is lost after 5 or 6 seconds (noted on the logs).

Whether you tried by disabling windows firewall? 
If the windows Firewall was a problem, so the client (SEP) on my server should work, and it did not.

AravindKM's picture
17
Nov
2009
4 Votes +4
Login to vote

If you are restoring Database

If you are restoring Database you have to restore those files also.
If you are having those files copy keystore.jks to Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc and copy server.xml to Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\conf and reconfigure your server. You will get all your clients back in our server...
If you don't having those files i will recoment tou to install freshly do not restore database
Create Groups and sylink file replace in clients ...(You will lose all the policies you are created in your ols SEPM)

In IIS manager goto symantec site properties and check in ip address colum whether you are selected all assigned ...

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

sscfss's picture
17
Nov
2009
0 Votes 0
Login to vote

ok thanksI will try to find

ok thanks
I will try to find a backup and do what you said, then I come back to you (Probably tomorrow, my backup is not here).

BTW, why is this key so important? I do not understand.
Thanks for your infos.

sscfss's picture
18
Nov
2009
0 Votes 0
Login to vote

THANK YOU! it worked great. I

THANK YOU!
it worked great. I had just to delete the jks and the xml file in the directory you cited and to replace them by my backup (with a change of name), then a config of SEPM and all is working great.
A new start of client had be necessary but all is working great now.
Thank you again.

Vikram Kumar-SAV to SEP's picture
17
Nov
2009
0 Votes 0
Login to vote

These keys are very important

These keys are very important when it comes to Disaster Recovery.

However, Read this document carefully to understand the procedure and to restore communication with and without database backup and/or Keys.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082112135948




sscfss's picture
18
Nov
2009
0 Votes 0
Login to vote

Thank you for your answer.I

Thank you for your answer.
I prefer the way of AravindKM

AravindKM's picture
18
Nov
2009
0 Votes 0
Login to vote

Happy to hear your problem

Happy to hear your problem got solved.......
 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind