To find the specific cause for the Java -1 error, look in the scm-server log. Provide feedback on this article Request Assistance Print Article Products Related Articles Subscribe to this Article Manage your Subscriptions Search Again Situation Symantec Endpoint Protection Manager (SEPM) 12.1 is logging errors Click View Log. This causes network discovery of computers by the Client Deployment Wizard to fail and generates the error(s) above. Source
Thank you for your feedback! You can use the server IP address in place of the computer name. If the client connects, the client's connection problem is probably not a network issue. From the default Symantec firewall policy: The 6th rule allows local file sharing to local computers.
You can test the communication between the client and the management server in several ways. Type a name for the log, and click OK. Note: Disable the log after you view it because the log uses unnecessary CPU resources and hard disk space. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more.
When you modify the Windows Registry, the management server generates the logs (ersecreg.log and exsecars.log). Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. This password is the one that you entered for the database when you installed the management server. https://www.symantec.com/connect/forums/clients-unable-browse-windows-network PHP checks for a global configuration file (php.ini).
The Home, Monitors, and Reports pages display an HTTP error. In the ODBC tab, verify that the Data source name drop-down list is SymantecEndpointSecurityDSN. Cause The local network is using an unconventional IP address range and therefore the rule that allows the local traffic (and has higher priority than the blocking rule) is not applied. In the SEPM, export the communication file (sylink.xml) from the client group to which you want the client computer to connect.
Check that the management server heap size is correct You may need to adjust the heap size that is appropriate for the management server's operating system. printers) from other machines on the local network, or just cannot see other computers in Windows "My network places". In the Windows Registry, turn on debugging in the client under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\smc_debuglog_on. Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation After installing or upgrading to Endpoint Protection 12.1, users are not
Click OK. this contact form Error On the client machines, in the Network threat protection logs (View logs->Network threat protection->Traffic log), you will see entries similar to the ones below. Try these resources. If you use the tool on the command line, read the SylinkDrop.txt file for a list of the tool's command parameters.
Try these resources. Check that the Symantec Endpoint Protection firewall or third-party firewall does not cause any network problems. Don't have a SymAccount?
Create a SymAccount now!' Unable to access shared folders or resources with Endpoint Protection 12.1 Small Business Edition TECH170110 January 17th, 2012 http://www.symantec.com/docs/TECH170110 Support / Unable to access shared folders or The management server service does not stay in a started state. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Verify that the network connection between management server and the SQL database is correct.
The rule "Block Local File Sharing to external computers"blocks the traffic,even thoughyour machines are on the local network. Use a browser to test the connectivity to the management server on the client computer On the client computer, open a web browser. In the left pane, click Debug Logs. Check This Out Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more.
Then restart the Client Deployment Wizard." Cause On Windows Server 2008 & 2008 R2, the Computer Browser service is set to disabled by default. If the client has communication problems with the management server, status messages about the connection problem appear in the logs. The Home, Monitors, and Reports pages are blank. Click Next.
The Home, Monitors, and Reports pages display a continuously loading progress bar, without displaying any content. If the management server runs the remote SQL database, perform the following actions: Verify that you have specified a named instance when you installed and configured Symantec Endpoint Protection Manager. Don't have a SymAccount? In the browser command line, type the following command, where management_server_address is the management server's DNS name, NetBios name, or IP address: http://management_server_address:8014/secars/secars.dll?hello,secars When the Web page appears, look for one
Click Login. This file usually appears in \Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\log.