Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

All SEP clients are unable to connect to SEPM but showing online in SEPM console

Created: 04 Mar 2013 | 6 comments

Hi All,

We have one issue in central SEPM server. All SEP clients are unable to connect with the Management server (where multiple priorities are configured) but the same is showing as online in SEPM console. We have a management server list configured with fallback option but none of the clients are swaitched to the fallback SEPM if they are unable to communicate with the Central SEPM. We have restarted both SQL and SEPM servers but no luck. Can anybody please help me.

Regards,

Sabyasachi

Operating Systems:

Comments 6 CommentsJump to latest comment

Brɨan's picture

Can you post the sylink log from one of the affected clients

How to enable Sylink debugging for the Symantec Endpoint Protection 11.x and 12.1 client in the Windows Registry

padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;">Article:TECH104758 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 0px;font: 12px Arial; text-align: left;">Created: 2008-01-18 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Updated: 2013-02-26 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Article URL http://www.symantec.com/docs/TECH104758

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Ambesh_444's picture

Hello,

Please check 80 port is open or not and if it is open then check that port 80 is getting telnet or not.

Thank& Regards,

Ambesh

"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

Sabya_Dash's picture

Hi,

Thanks for your response. Please find the same for one of the problematic client.

AttachmentSize
Sylink.7z 3.55 KB
Rafeeq's picture

need few more info after this line

 
03/04 17:22:25.041 [4060] 17:22:25=>Send HTTP REQUEST
03/04 17:22:25.337 [2520] 17:22:25=>HTTP REQUEST sent
03/04 17:22:25.337 [2520] 17:22:25=>QUERY return code
whats the return code you find?
Rafeeq's picture

Follow these documents 

1.   Open the registry (Start->Run->type "regedit").

2.  Go to HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings\connections

3.  Delete the registry keys "DefaultConnectionSettings" and "SavedLegacySettings".

4.  Reboot the machine.

Note:  These registry keys will automatically regenerate after reboot of machine.

Also, this also could be caused due to incorrect proxy server information in the following registry location: HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings

Removing the incorrect proxy info from this key and then rebooting allowed the client to communicate normally.

One important thing to keep in mind is that any incorrect proxy information must also be removed from the following two locations as well:

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\SavedLegacySettings

If the settings are not removed from these two keys, they will repopulate the Internet Settings key after every reboot.

Remove the incorrect proxy information from all 3 registry locations noted above, then reboot.

==========================================================

and this document too, if it fails , post a fresh sylink please.

http://www.symantec.com/business/support/index?page=content&id=TECH139251