Endpoint Protection

 View Only
  • 1.  Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 11:01 AM
      |   view attached

    Hi

    Im facing issue in most of the server that Connection status : Not Connected Error: Could not connect to server, when i click on error details im getting the below link.I have also tried replacing the sylink but no lock

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

    Port is also opened for the same.Kindly find the attachment

     

     

     



  • 2.  RE: Connection status : Not Connected || Symantec Client not communication

    Broadcom Employee
    Posted Sep 29, 2012 11:06 AM

    whats the version?

    can you pas son the sylink log?



  • 3.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 11:09 AM

    12.1



  • 4.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 11:16 AM

    HI,

    Are you able to telnet SEPM server ?

    Testing Communication from an Endpoint Protection client to the Endpoint Protection Manager

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



  • 5.  RE: Connection status : Not Connected || Symantec Client not communication

    Broadcom Employee
    Posted Sep 29, 2012 11:44 AM

    can you check the communication troubleshooting

    Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting

    http://www.symantec.com/docs/TECH160964



  • 6.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 12:22 PM

    Im able to ping the server and ports are opened too,but when i tried to check the below suggestion,Im getting page cannot be displayed.

    http://<SEPM_Server_IP_or_Machine_Name:Port>/secars?hello,secars<sepm_server_ip_or_machine_name:port></sepm_server_ip_or_machine_name:port>

     



  • 7.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 12:26 PM

    HI,

    Check this

    Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting

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

    Try to one client

    Check in the registry (HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings) those keys
    "ProxyEnable"=dword:00000001
    "ProxyServer"="test:80"

    2. Change ProxyEnable to 0
    3. Delete ProxyServer key

    These settings are also cached in Hex format in the following location: HKU\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections
    -DefaultConnectionSettings
    -SavedLegacySettings

    If DefaultConnectionSettings and SavedLegacySettings are present, they will re-populate the proxy settings. If they are NOT present, they will be generated with the current proxy settings. This can cause issues if the customer tries to alter just "HKU\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ProxyEnable" without also purging DefaultConnectionSettings/SavedLegacySettings before a reboot.

     



  • 8.  RE: Connection status : Not Connected || Symantec Client not communication

    Broadcom Employee
    Posted Sep 29, 2012 12:28 PM

    did you use the IP and port?

    can you post the sylink log?



  • 9.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 29, 2012 12:46 PM

    Ashish:

    ProxyEnable"=dword:00000001  - this key is already set to 0
    "ProxyServer"="test:80"  - not able to find this key

    pete :

    I used telnet IP:port and port is opened, also its pinging to the SEPM server

     



  • 10.  RE: Connection status : Not Connected || Symantec Client not communication

    Broadcom Employee
    Posted Sep 29, 2012 12:59 PM

    ok, can you pass on the sylink log?

     



  • 11.  RE: Connection status : Not Connected || Symantec Client not communication

    Posted Sep 30, 2012 03:46 AM

    hi Niyaz,

    How many system are having problem ?

    Can You Pass syslink Log ?

    Try to export syslink.xml and replace some system..