Error Occurred Package Security Specific
Contents |
your account only takes a few minutes. Join Now I set up a new Windows 7 PC for a user, like many times in the past. I didn't do anything different. When I tried to do some remote Computer Management, I get the error: a security package specific a security package specific error occurred 1825 error occurred (1825) I did a search for it but didn't find anything specifically to Computer Management. Any
A Security Package Specific Error Occurred Dns
suggestions? Thanks! Brian Reply Subscribe View Best Answer RELATED TOPICS: Possible to authenticate as a different user using remote computer management? What port do I a security package specific error occurred backup exec need to open to use remote computer management? Locate Remote Computer   7 Replies Datil OP Best Answer Rambling Biped Oct 25, 2012 at 2:35 UTC Looks like an authentication error. Check for duplicate IPs? Disjoin/rejoin the domain? 2 a security package specific error occurred wmi Tabasco OP Garak0410 Oct 25, 2012 at 2:37 UTC I'll give it a shot...he was having some Excel lock ups with files on the server this morning too... 0 Tabasco OP Garak0410 Oct 25, 2012 at 3:26 UTC Yep...can I please use my "duh" for the day? Didn't even think of duplicate IP's...that was it! 0 Datil OP Rambling Biped Oct 25, 2012 at 3:49 UTC Excellent! Glad it was an easy fix! 1 Serrano OP Iforgotmydisplayname
A Security Package Specific Error Occurred Remote Debugging
Apr 9, 2013 at 1:44 UTC Sorry for commenting on an old post, but DNS was the problem when I got this error message. There were two entries in DNS for the machine. I deleted one, restarted the computer and everything was fine. Thanks for pointing me in the right direction. 2 Thai Pepper OP wRx7M Sep 18, 2013 at 5:25 UTC I know it is an old thread but mine was a duplicate IP problem also. Not sure why my DHCP server would have done this. EDIT: Looks like the it was DNS that had an old record from a system that had been powered off. So DHCP server did not have the IP showing as leased to it. I guess the DNS record did not get scavenged. Maybe I need to increase the frequency of the scavenging to more closely match the DHCP server lease times. Edited Sep 18, 2013 at 5:45 UTC 1 Chipotle OP Der Geist Aug 30, 2016 at 3:08 UTC Just to add to this. The Win7 workstation I had issues with ended up being out of sync. I triggered a remote GP Update and remotely set the time. It's an old shop PC that the old man doesn't reboot often. Checking the IP/DNS didn't turn up anything in this instance. 0 Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more a security package specific error occurred dcom Top Tags 5746× prtg 1841× snmp 1466× sensor 935× wmi 622× notifications 465× maps View all a security package specific error occurred remote debugger Tags 80070721: A security package specific error occurred- Note: the OS version of the device could not b Votes:0 Your Vote: Up Down
A Security Package Specific Error Occurred 80070721
Getting this error on all WMI sensors for a new VM I created recently. What is strange to me is that this VM is a clone of another VM which has no PRTG sensor issues. I can't find anything https://community.spiceworks.com/topic/270119-remote-computer-management-problems different about this VM. Any ideas? prtg windows-2008-r2-sp1 wmi Created on Jul 25, 2014 10:14:49 PM by Peter Bollwerk (0) ●1 Permalink 3 Replies Votes:0 Your Vote: Up Down Full text of the error: 80070721: A security package specific error occurred- Note: the OS version of the device could not be determined, WMI might not work reliably. Add comment Created on Jul 28, 2014 5:22:27 PM by Peter Bollwerk (0) ●1 Permalink Votes:0 Your Vote: Up Down The https://kb.paessler.com/en/topic/61027-80070721:-a-security-package-specific-error-occurred-note:-the-os-version-of-the-device-could-not-b error here is related to security issues directly in PRTG or the target Windows. It's an error-message directly from the targets DCOM. I'm afraid it's very hard to solve such sporadic issues with WMI Sensors, where the actual error originates within the target DCOM/WMI. Over which PRTG or we do not have any control or influence over. So there is very little we can do to be honest, except of course try the usual tips with WMI Issues, use longer scanning intervals, maybe use Remote Probes to distribute WMI load or do local WMI access. It seems though using the FQDN instead of 'just' hostnames helps with this error as well: http://blogs.technet.com/b/brad_rutkowski/archive/2011/03/08/solution-for-a-security-package-specific-error-occurred.aspx Add comment Created on Jul 29, 2014 8:25:23 PM by Greg Campion [Paessler Support] Permalink Votes:0 Your Vote: Up Down I was able to resolve this and the solution turned out to be easy. The problem was because I had mistakenly joined the server to the wrong domain in the forest - e.g. contoso.com, when it should belong to dev.contoso.com I had already moved the server to the correct domain a while ago, but the "old" computer account still existed in AD under contoso.com. Once I verified that it existed also in dev.contoso.com, I deleted the one under contoso.com and voila! Problem solved. In case anyone is curious, here is an event in the system event log for the server that
event log of a server. For this task there is no need to log in using remote desktop. However when I fired up the event log viewer and tried to connect to the NetBIOS name of my server I got http://setspn.blogspot.com/2010/11/security-package-specific-error.html the following error: Using remote desktop I could connect just fine to the server. At least that's what it looked like. Locally I could open the event log without issues. But I saw events which couldn't possibly be logged https://support.symantec.com/en_US/article.TECH88325.html on this server. And then it came clear, there was an IP conflict! To be honest it's a lab environment so these things can happen occasionally. The reason this fails is because my client (my administration pc) asks AD error occurred for a Kerberos Ticket for server x whilst when connecting I'm actually presenting this Kerberos Ticket to server y. This results in a server receiving a ticket encrypted with a password other than it's own. Result: the above error. Thomas, we should have updated the CMDB, Vuylsteke
Related Posts , , , Posted by Thomas at 3:57 PM Labels: Kerberos, Windows 2003, Windows 2008, Windows 2008 R2 6 Response to A security package specific error occurred(1825) Anonymous a security package 22 November, 2010 13:02 This error can also occur when the time on your server is incorrect... m3Rlin 14 June, 2011 15:23 In my case it was incorrect time on the machine I was trying to connect to. Thomas 14 June, 2011 23:29 Thanks for the feedback! Definately interesting to keep in mind. Anonymous 09 November, 2011 23:14 Two records on the same DNS address can do this too. Anonymous 01 April, 2015 22:56 THis can also happen if the password stored in the Credential manager is old/ Remove the credentail and should work. Sadtaco 09 September, 2015 00:15 Greetings. Add Your Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Follow Me Categories .NET 3PAR Active Directory AD CS AD FS AD FS 2016 ADMT App-V Award Azure Azure AD Blade Commvault Debug DFS Direct Access DNS DSC Dynamics Ax 2012 Exchange Exchange 2010 Failover Clustering FIM FIM 2010 R2 Forefront GAL Sync HP HP RDP HP SIM IIFP IIS ILM iLO ISA Kerberos Kerberos Troubleshooting Tips Microsoft MIM 2016 Networking Office 2010 PowerShell Print Services Printing RemoteApp SCCM SCDPM SCOM SharePoint SharePoint 2010 SQL SSPR TFS TMG UAG 2010 Virtual Machine Visual Studio VMware Web Application Proxy Windows 10 Windows 2003 Windows 2008 Windows 2008 R2 Windows 2012 Windows 2012 R2 Windows 7 Windows 8 Windows 8.1 Windows XP AD Mailing List Blog Archive ► 2016 (3) &PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Error: A security package specific error occurred TECH88325 January 7th, 2004 http://www.symantec.com/docs/TECH88325 Support / Error: A security package specific error occurred Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Artic