Managed clients don't connect to the server
Updated: 22 May 2010 | 9 comments
This issue has been solved. See solution.
hello, I have a problem with Symantec endpoint 11.0.5. the clients which I deplyed the package result not managed by the server
If I try to manually run a scan the command can't be executed becouse the client has not connected to the server yet.
i tried to reistall the package but nothing change.
the only managed client result to be the server which has the server installed.
I made a rule on the firewall to let open the ports on the server but i'm not sure i made i right.
Could you be so kind to hel me?
Discussion Filed Under:
Comments
hi
I think the firewall is blocking it
you need to open port 8014 on both clients and servers
in IIS the it should be allowed access for all ip address
start -run - inetmgr
rigth click symantec web server - properties
under directory access
ip address and restriction ; it should be all allowed.
follow this document
https://www-secure.symantec.com/connect/articles/troubleshooting-client-communication
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
thaks to your link I probably
thaks to your link I probably found the solution:
I replaced the sylink.xml file on a client and it seems to work fine.
tomorrow I'll made a script to do it on other clients to finissh the tests.
thank you
Another thing to consider, is
Another thing to consider, is this a fresh install of SEP, a migration from a previous version of SAV/SEP, or a disaster recovery? If it's not a fresh/first install of SEP, the clients may be holding on to the previous installation/version communication settings - which are not overwritten by default with a new deployment.
If this is the case, you need to replace the sylink.xml file the clients use to communicate with the manager. A couple ways to accomplish this:
http://service1.symantec.com/support/ent-security....
Symantec Technical Specialist (SCTS)
hi
You can get the remote sylink replacer it wil make things lot easier just read the pdf , you will be good to go.
https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Oh yeah. I love me some
Oh yeah. I love me some Sylink Replacer!
And, you answered my question
And, you answered my question while I was composing the post.
Symantec Technical Specialist (SCTS)
Would this also be an issue
Would this also be an issue if when creating your export package you check to delete the old settings? I've run into this same issue but I've always been sure to check the option to install the fresh communication settings. Just curious if this might be the solution to a problem I've been having as well...
Yes, this is the option to
Yes, this is the option to choose if you've built a new SEPM and are migrating clients from a retired SEPM, or performed a disaster recover without a database backup. If you use the Migration & Deployment Wizard, this is taken care of for you automatically, although it is a good idea to use this option in the package you build to deploy - just to be certain.
Symantec Technical Specialist (SCTS)
SOLVED
It was the sylink.xml file. I replaced it on all the clients and now they are ok
thank you very much
Would you like to reply?
Login or Register to post your comment.