New Symantec agents are not able to connect to the server
Created: 16 Jan 2013 | Updated: 29 Jan 2013 | 18 comments
This issue has been solved. See solution.
I have recently upgraded my SEPM server to 12.1.2 and everthing seemed to go fine with the upgrade. The only issue I am having is every new agent I install is offline. All of the current agents that were on the server are communicating fine.
Thanks for the help.
Discussion Filed Under:
Comments 18 Comments • Jump to latest comment
Did you reboot the SEP client after the upgrade?
A very similar thread here:
https://www-secure.symantec.com/connect/forums/sep...
SEP Knowledge Base
Endpoint SWAT
Hi,
Do you have create NEW package ?
SEP 12.1 RU2 and Reset Client Communication
https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication
Symantec Endpoint Protection: Troubleshooting Client/Server Connectivity
http://www.symantec.com/docs/TECH105894
Troubleshooting Client Communication with SEPM
http://www.symantec.com/docs/TECH95789
Thanks In Advance
Ashish Sharma
SEPM Knowledgebase Documents
What is the status of the Client-Server connection if you check in the SEP client GUI -> Troubleshooting -> Management -> General Information?
Does the client has newest policy from SEPM and the current definitions?
How are you performing the new installations? Push deployment? Autoupgrade from SEPM? Manual installation?
was the package managed client?
can you post the sylink log?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
are the new agents cloned?
How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 clients
http://www.symantec.com/business/support/index?pag...
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Thank you for the quick response on this issue.
@Brian81 I did Reboot the computers after the install finishes
@Ashish These are all new endpoint that I am adding to the server so they have never had Symantec on them.
@SebastianZ It shows offline for the server connection. I am pushing the install with the deployment of our imaging system, but The install is not in the image. We use Dell Kace and it pushes it as a Post deployment install.
@pete_4u2002 It was a fresh install and the package was created by the server
I did find this while I was looking around it show that the client knows about the server but the server can't make the connection.
HI,
Try to export sylink.xml and replace.
also check connectivity
Symantec Endpoint Protection: Troubleshooting Client/Server Connectivity
http://www.symantec.com/docs/TECH105894
Troubleshooting Client Communication with SEPM
http://www.symantec.com/docs/TECH95789
Thanks In Advance
Ashish Sharma
SEPM Knowledgebase Documents
Replace the sylink file on one client with the one from the SEPM. Right click on a group in SEPM and Export Communication Settings and replace on the client. See if it makes the connection than
SEP Knowledge Base
Endpoint SWAT
From the error message you posted:
I tried the Sylink.xml replacement and it didn't change. I upgraded from 12.1 the latest version before 12.1.2 so I don't think any major changes happened.
Hi,
Can you check Client Connectivity between SEP Client and SEPM server ?
are you able Telnet Port 8014 ?
Symantec Endpoint Protection: Troubleshooting Client/Server Connectivity
http://www.symantec.com/docs/TECH105894
Thanks In Advance
Ashish Sharma
SEPM Knowledgebase Documents
Can you check the scm.server.log from SEPM for any repeated errors?
-> SEPM install folder/tomcat/logs/scm-server-0.log
-> SEPM install folder/tomcat/logs/scm-server-1.log
How many clients are in your network which are already installed and working fine?
Also please check you have another license available to manage the new clients from Server. This may be the reason for the client offline..
https://www-secure.symantec.com/connect/forums/sepm-121-licensing-status
Regards
Sumit G.
Hi
Please try to ping the SEPM server
Regards
Waiting for your revert on above comment.
Regards
Sumit G.
Agreed with above comments, Please follow the same will get your solution.
Thank& Regards,
Ambesh
Please mark your thread as 'SOLVED' with the answer that helps you.
I'm sorry for not getting back to everybody got pulled away on another project. The issue is actually resolved I'm still not sure what was wrong but I created a new sylink package from the server and installed it on one of the new clients. It started to be able to talk to the server along with all the other client that had been blocked. I am not sure what the new sylink package opened up that the old one did not have (made from the same server) but it allowed the server to start talking to the new clients.
Thanks for getting back to us. Just a follow-up question. Did you install a package to the new clients or did you install the non-managed client from the CD?
Would you like to reply?
Login or Register to post your comment.