Hello Nald,
I did some research and found the following solution for the event ID 1000
with return value 1326.
CAUSE
==========
This problem can occur if the original release version of Windows 2000 is
installed on a Windows NT 4.0 domain controller that has a DNS suffix
defined in the Network control panel applet. Windows 2000 setup
automatically unchecks the Change primary DNS suffix when domain membership
changes check box and sets the primary DNS suffix to the first suffix
listed in the Network control panel applet. Once promoted, the domain
controller will attempt to register and resolve DNS records in the DNS zone
that matches its primary DNS suffix. This problem does not occur if any of
the following are true:1. The Windows NT 4.0 domain controller does not
have a DNS suffix defined prior to the upgrade.
2. The Windows NT 4.0 domain controller is upgraded to Windows Server 2003.
3. The Windows NT 4.0 domain controller is upgraded to Windows 2000 where
the setup files have been integrated (slipstreamed) with SP1 or later.
Windows 2000 and Windows Server 2003 both support a disjoint namespace as a
valid configuration, provided DNS is properly configured. In a majority of
cases however, the disjoint namespace is unintentional, and DNS is not
configured to support it. When this happens, domain controllers will not
register in DNS, which results in a variety of problems with Active
Directory.
For the resolution steps go thru
http://support.microsoft.com/?id=257623
For more information
================
Value 1326 - "Logon failure: unknown user name or bad password." - I had
this error filling up my event viewers on two servers for days. I had
scheduled backups under my user name and password. After I changed my
password I started getting the errors. I fixed it by rescheduling the jobs
under my user name and new password; problem resolved.
This error may occur when an user account is left logged onto a PC, and is
disabled by an administrator in the background. Once the Disabled ID is
logged off, the error goes away.
I had this problem on a Windows 2000 DC. It turned out it wass caused by
ZoneAlarm firewall
Value 1326 = ""Logon failure: unknown user name or bad password." - This
will occur if a Terminal Session is disconnected and not logged off and
susequently the users logon password is changed. You will still have access
to the "stale" session with the new password. This commonly happens with
Administrators, who leave the session open by disconnecting so as to leave
a program running. Since an Administrator can log back onto the session
with the new password it can be overlooked. Terminate the Terminal Services
session by logging out and the problem will disappear.
I hope the above information will help you to solve the problem.
thanks,
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.
