J
Josh
I have been having a problem with an XP Pro SP1
workstation. When I try to log on to our active directory
domain, I get the message "Windows cannot connect to this
domain, either because the domain was not found or the
password was incorrect". I have tried multiple accounts,
to no avail. When I log on as local administrator and
look at the application event log, there is this entry:
This computer could not authenticate with
\\gwuapps.gardner-webb.net, a Windows domain controller
for domain WEBBNET, and therefore this computer might
deny logon requests. This inability to authenticate might
be caused by another computer on the same network using
the same name or the password for this computer account
is not recognized. If this message appears again, contact
your system administrator.
I can ping all of our domain controllers, including
gwuapps, and I can get out to the internet and check
email once I log on as local admin. If I take the
computer out of the domain, then put it back in, the
problem is temporarily resolved, only to reappear a week
later. Any suggestions? Feel free to email me at:
jstroup(at)gardner-webb.edu. Thanks.
workstation. When I try to log on to our active directory
domain, I get the message "Windows cannot connect to this
domain, either because the domain was not found or the
password was incorrect". I have tried multiple accounts,
to no avail. When I log on as local administrator and
look at the application event log, there is this entry:
This computer could not authenticate with
\\gwuapps.gardner-webb.net, a Windows domain controller
for domain WEBBNET, and therefore this computer might
deny logon requests. This inability to authenticate might
be caused by another computer on the same network using
the same name or the password for this computer account
is not recognized. If this message appears again, contact
your system administrator.
I can ping all of our domain controllers, including
gwuapps, and I can get out to the internet and check
email once I log on as local admin. If I take the
computer out of the domain, then put it back in, the
problem is temporarily resolved, only to reappear a week
later. Any suggestions? Feel free to email me at:
jstroup(at)gardner-webb.edu. Thanks.