Windows can not determine user or computer name event id (1000)

  • Thread starter Thread starter JSolis
  • Start date Start date
J

JSolis

I am getting the following error while trying to log in
into the AD, (Naming information can not be located
because the target principal name is incorrect, contact
your system admin to verify that your domain is properly
configure and online), in addition I've looked at the
event viewer and it gives me event ID 1000, windows can
not determine user or computer name return value (1326).

because of this error clients are not being authenticated,
and I have no access to the AD. I do have a BDC but I can
not make it the PDC because it can not contact the PDC
(FSMO holder).

Help Please, I've worked on this problem for the pass 2
days and I'm about to throw the server out the window!!!
 
Hello,

How is your clients DNS configure on your clients and Windows 2000 DC?

It's key for the clients to be able to resolve the Windows 2000 Domain Controller and your Active Directory DNS zone is properly configure.

Here are my recommendations:
1. Start troubleshooting the Windows 2000 DC first.
a. Check the System Event log for Netlogon Errors or Warnings, this will indicate an issue registering the SRV records in DNS. (Watch out for 5781, 5774, or 5775)
b. Ensure that Windows 2000 Domain Controller is pointing to DNS Server that allows Dynamic Updates. In a single Windows 2000 domain controller configuration, it is
common to point the Primary DNS to the Domain Controller's IP Address, with DNS installed on the server. (Note: You may need to configure Forwarders to allow Internet
Domain resolution.)
c. Once DNS is configure properly, restart the netlogon services to verify the errors do not re-occur. (Typically you will receive two Browser Events 8015, if netlogon is
working properly)
d. Once you verify that name resolution is working, re-apply group polices to ensure there are no issues. (type the following command "secedit /refreshpolicy
machine_policy /enforce) Check the application log for a Event ID 1704. (Watch out for 1000, 1001, 1202 from userenv ot scecli)

2. Start Troubleshooting the Windows 2000 clients.
a. Make sure Primary DNS Setting is pointing to the Windows 2000 Server.

320099 A security policy does not process restricted groups correctly
http://support.microsoft.com/?id=320099

324383 Troubleshooting SCECLI 1202 Events
http://support.microsoft.com/?id=324383

837513 Domain controller is not functioning correctly
http://support.microsoft.com/?id=837513

Thank you,

Ben Ybarra [MSFT]
Microsoft Corp.

--

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Back
Top