The client is prompted to check in with its parent server. Downloaded trial NS-TW-22.0.0-EN-US.exe and ran it - note this automatically uninstalls Norton 360. The install asks for a restart, which I did. At this point, I got the 'cannot connect' message. After several rounds with this (uninstalling with the removal tool, and then attempting the reinstall again with the same results). I decided to try to contact Norton by chat. Not surprisingly, If problems persist after you complete the steps in this document, contact Symantec Technical Support for assistance. weblink
Norton Security |Trialware |Expires 03/14/2015" So I simply clicked on the Next button and NS opens with 29 days remaining.... Right-click My Computer, and click Properties. I found this among many other articles about t-shooting communication problems on the symantec website. Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation When you view or change the configuration for a group of clients https://support.symantec.com/en_US/article.TECH100216.html
What To Do If the endpoint is centrally managed ensure the computer is in a group with a correct updating policy. An old version of SAV is installed on the endpoint computer and fails to be updated. If you use a different firewall, do one of the following to determine whether the firewall blocks communication from Symantec System Center: Look at the firewall logs .
Failed to reveal datbase user password , reason :Obscure:Invalid algorithm ident=144 createAccessToken: LogonUser failed Provider cannot be found. Some users had called up phone numbers which advertised to be Norton techs, but turned out not to be. Note:You may also see a 'Failure Audit', Event ID 18456 from source MSSQL$SOPHOS in the application event log. This is an important step as the unique error text may only be mentioned at the end of the message.
If the error shown in the computer's Event Viewer is not listed above run the Sophos Diagnostic Utility (SDU) on the management server and submit the output file to Support. The second time I restarted the computer and I did unsuccessfully to update the program. Connect with top rated Experts 12 Experts available now in Live! https://www.symantec.com/connect/forums/symantec-antivirus-server-cannot-communicate-2-clients rms59 Newbie1 Reg: 29-Oct-2014 Posts: 10 Solutions: 0 Kudos: 0 Kudos0 Re: Cannot connect to symantec server Posted: 29-Oct-2014 | 4:14PM • Permalink Thanks for the replies but I don't even
Verify that the test succeeds. If the word OK does not appear, the client computer cannot connect to the management server; the problem is likely at the server's end. Sorry for all the questions, but trying to get some background information. The dates, times, server address, and port numbers are available for troubleshooting connection problems.
Thank you. Me Too0 Last Comment Replies1 2 Krusty13 Guru Norton Fighter25 Reg: 31-May-2011 Posts: 12,856 Solutions: 486 Kudos: 3,342 Kudos0 Re: Cannot connect to symantec server Posted: 02-Oct-2014 | 5:29PM http://www.helpinfo.com/index.jsp?k2dockey=1021096110270174307&formwassubmitted=true Success always occurs in private and failure in full view. Yes No Comment Submit Sophos Footer T&Cs Help Cookie Info Contact Support © 1997 - 2016 Sophos Ltd. If the address is correct confirm that the address can be reached - either via 'Start | Run' (for UNC address) or via a web browser (for http addresses).
Check that the management server does not have a network problem. have a peek at these guys If your server group appears, but you continue to have communication problems, go to the "Make sure that Symantec System Center works correctly" section of this document. The desktop goes through the install process but when it gets to the "Connecting to Semantic Server" it fails to connect. That being said, I am left with the only alternative being to go to the competitors, and use their product, which is still functioning quite nicely, though they were not, as
Stop the services in the following order: Symantec System Center Discovery Service Intel Alert Handler Intel Alert Originator Intel File Transfer Intel PDS Symantec AntiVirus (Symantec AntiVirus Server , in Symantec In the Add Standalone Snap-in window, click Group Policy, and then click Add. In Active Directory 'Users and Computer' check any computer names listed in the 'Log On To...' dialog under the account's properties, on the 'Account' tab. check over here also i tried the "discovery" and the "find computer" and also it is not working.
I downloaded the trial version of Bit-Defender and it installed without any user intervention in less than 10 minutes including the time it took to automatically uninstall Norton Security. Solution The communication channels between all of the Symantec Endpoint Protection components must be open. Check Update virus definitions from parent server.
For help with this setting, follow the directions under "To change the Default Impersonation Level using Dcomcnfg.exe" in the "Technical Information" section of this document. This problem most commonly happens after installation and does not typically recur during normal use. Perform the following tests: Check that the SQL Server service referenced in the connection string established above is started. this content Neither will open. The original install was on my laptop and that's working with 366 days remaining.
All of these issues display a Java -1 error in the Windows Event log. For more information on re-obfuscating the password see article13094. [ TOP ] createAccessToken: LogonUser failed Note: This message maybe seen: createAccessToken: LogonUser failed ----- [outer exception] ----- -- error: 0x8000FFFF (Catastrophic Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more.
© Copyright 2017 deftmag.com. All rights reserved.