Domain user prompted for password

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi:

Recently we have been facing a couple of issues - one on the DC (2kAS) while
the other on an XP client machine and are unable to figure out if they are
related somehow. Your help would be appreciated.

ISSUE I:
The domain user on the particular client is unable to access network
resources which earlier would open without prompting for the domain username
password. On entering the correct password, the following error prompt is
thrown at the domain user.
"Logon Unsuccessful: The user name you typed is the same as the user name
you logged in with. That username has already been tried. A Domain
Controller cannot be found to verify that user name."

Incidently, the domain admin is able to login through the prompt.

ISSUE II:

"Some" XP machines on the domain have had their Network Connection icons
missing. Loggin in locally as administrator (local) and re-registering
certain network connection related dll's solves the problem. However, on
again logging into the domain, the issue crops up. This happens on some XP
machines only.

ISSUE III:

The domain controller seems to have been busy generating the following error
Event ID: 1126
Event Source: NTDS General
Event type: Informational
Description: Unable to establish connection with global catalog

It is replicating the policies and the like as has been debugged.


TIA
 
Could be alot of things, but first port of call when computers can't locate
the DC is to check your DNS config. The DC (or whichever server provides
authoritative DNS for the domain) must be FIRST in the DNS-server list on the
clients.
 
1. DNS wont be the issue as only some machines face the error. And the DNS
is the first on their list anyway. Also, as administrator of the domain, the
servers allow me to access shares from the machines. So that should not be
the problem.


I also rolled back all domain policies on a test machine to work on the
issues.

2. Noticed that the Net Logon service would start and stop intermittently.
So I reset the Domain Policy on the same. RPC Locater was another one for
which I had to reset the policy.

3. Also added a registry key on server 'DependOnService' = LanmanServer
under HKLM\System\CCS2\Services\NetLogon\

ISSUE RESOLVED
4. The servers allow auto login to domain clients (test machine in this case)
5. Server has stopped generating the NTDS error.

ISSUE UNRESOLVED
6. The network connections are still not visible. (I have installed /
uninstalled couple of updates from the test machine but does not seem to work)

Any further suggestions?
 
Back
Top