KIXTART produces an event ID 1789

  • Thread starter Thread starter rob
  • Start date Start date
R

rob

Our KIXTART logon script is 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 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?
 
In
rob said:
Our KIXTART logon script is 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 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?
Click to expand...


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 refrence. Make sure as well that you are NOT using an ISP's
DNS server in any machine, or that can cause this and many other errors.

Hope that helped.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top