Error 1789 Kixtart

Add-on Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. TheEventId.Net for Splunk Add-onassumes thatSplunkis collecting information from Windows servers and workstation via the Splunk Universal Forwarder. read more... Event ID: 1789 Source: KIXTART Source: KIXTART Type: Error Description: failed Error: The trust relationship between this workstation and the primary domain failed. (0x6fd/1789). English: Request a translation of the event description in plain English. Comments: EventID.Net Reported functions: - GetPG: LookupAccountSid - GetPrimaryGroup - GetSid As is the case with most of the events fom Kixtart, the event id represents actually the network error code that Kixtart got when it tried to use the function listed in the event description. These functions are used by Kixstart to query various variables configured in the script. LookupAccountSid for example, retrieves the name of the account for this SID and the name of the first domain on which this SID is found. So when Kixstart tried to use this function got the 1789 error which means "The trust relationship between this workstation and the primary domain failed". x 8 Private comment: Subscribers only. See example of private comment Links: Kixstart Home Page, Error code 1789 Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links... Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Login here! Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended booksNewsletter Links Follow us on FacebookFiregen Log Analyzers Link to us © Copyright 2001-2016 EventID.Net

360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://www.eventid.net/display-eventid-1789-source-KIXTART-eventno-2856-phase-1.htm Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/976494 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States)‎ Terms of use Privacy & cookies Trademarks © 2016 Microsoft

producing an event ID 1789, on 2000 and XP clients, I have tried rejoining one of the computers to the domain, but it still has the problem. Our logon script works with 3.62 of Kixtart with these Event errors, but after upgrading to 4.22 INGROUP fails, so we're still http://www.pcreview.co.uk/threads/kixtart-produces-an-event-id-1789.1474412/ on 3.62 with the Event errors. We also get Event ID: 15 "AutoEnrollment" errors in our XP client https://www.experts-exchange.com/questions/23584013/Weird-problems-DHCP-slow-to-respond-domain-trusts-continually-failing.html event logs. MS KB docs indicate these problems are related to DNS, perhaps! Note We have 2 historical issues that may well be the root cause: 1: Our DNS server used to be on our Linux server, and was not moved until after upgrading to W2k. 2: Our NT4 Domain name was PSS and the server was upgraded to w2k using the zone name pso.org.nz. 3: After moving the DNS to the error 1789 w2k server several changes had to be made to the DNS to add "PSS" to the forward lookup zones (I think). I only want a file server not all this agro with huge consultant expenses! (I've used MS experts) Can anyone advise? rob, Jun 15, 2004 #1 Advertisements Ace Fekay [MVP] Guest In news:1cad801c452a9$a063eb30$, rob <> posted their thoughts, then I offered mine > Our KIXTART logon script is producing an event ID 1789, on > 2000 and XP clients, I have tried rejoining one of the > computers to error 1789 kixtart the domain, but it still has the problem. Our > logon script works with 3.62 of Kixtart with these Event > errors, but after upgrading to 4.22 INGROUP fails, so > we're still on 3.62 with the Event errors. > > We also get Event ID: 15 "AutoEnrollment" errors in our XP > client event logs. MS KB docs indicate these problems are > related to DNS, perhaps! > > Note We have 2 historical issues that may well be the root > cause: > 1: Our DNS server used to be on our Linux server, and was > not moved until after upgrading to W2k. > 2: Our NT4 Domain name was PSS and the server was upgraded > to w2k using the zone name pso.org.nz. > 3: After moving the DNS to the w2k server several changes > had to be made to the DNS to add "PSS" to the forward > lookup zones (I think). > I only want a file server not all this agro with huge > consultant expenses! (I've used MS experts) Can anyone > advise? Haven;t used Kixstart in years. Anyway, that said, a forward lookup zone called PSS won't work with DNS since it's a single label name and DNS follows a hierarchal naming tree. The Primary DNS Suffix of your clients MUST be set to the SAME exact name as your DNS forward lookup name for AD. So if its pso.org.nz, then that's what they need to be, otherwise DNS registration will fail. Maybe you'll need to go thru your script and update to all the new names and remove the PSS

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Weird problems - DHCP slow to respond, domain trusts continually failing Want to Advertise Here? Solved Weird problems - DHCP slow to respond, domain trusts continually failing Posted on 2008-07-21 SBS DHCP Active Directory 3 Verified Solutions 23 Comments 1,899 Views Last Modified: 2012-08-14 G'day A client of mine recently had a RAID controller crash which resulted in us having to do a bare metal restore of Windows Small Biz Server 2003 - reinstall a fresh O/S, restore file system, then restore AD (all from the same backup sets). Restore was done from tape via BackupExec 12. Crash was on a Monday afternoon, last backup was from a Friday night. After getting it up and running at the end of June, I have noticed two major issues. - DHCP responses seem really slow, many records in event viewer from user workstations saying that they were unable to get an IP from the system, which is causing netlogon/group policy processing errors (as the user is logging on under cached credentials). Most of the time there is only one error in the event viewer, some times two, before an IP is assigned. - Domain trusts keep failing on various machines, even after removing them from the domain and rejoining, trying the NETDOM RESET commands, etc. When joining new computers to the domain via the ConnectComputer utility in SBS, the domain trust fails straight away after reboot. I rejoined a system yesterday, and today the domain trust