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.

I have had a lot of problems with the Windows XP's
Personal Firewall and AD domains. For some reason when
that is running I have issues either with logging into a
domain or obtaining access to objects on that domian. Have
you tried turning that off to see if you get a better
result. The only other thing I can think of is to ensure
that you don't have any other devices with the same naming
convention as what you are using to log in with.

Hope this helps.

Rich

>-----Original Message-----
>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.
>.
>

Rich, I am not running XP's firewall on the machine. I
have also changed the machine name to see if that would
make a difference, and it did not help.

Josh

>-----Original Message-----
>I have had a lot of problems with the Windows XP's
>Personal Firewall and AD domains. For some reason when
>that is running I have issues either with logging into a
>domain or obtaining access to objects on that domian.
Have
>you tried turning that off to see if you get a better
>result. The only other thing I can think of is to
ensure
>that you don't have any other devices with the same
naming
>convention as what you are using to log in with.
>
>Hope this helps.
>
>Rich
>
>>-----Original Message-----
>>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.
>>.
>>
>.
>

On Tue, 30 Mar 2004 11:19:45 -0800, "Josh"
wrote:

>Rich, I am not running XP's firewall on the machine. I
>have also changed the machine name to see if that would
>make a difference, and it did not help.
>
>Josh
>
>>-----Original Message-----
>>I have had a lot of problems with the Windows XP's
>>Personal Firewall and AD domains. For some reason when
>>that is running I have issues either with logging into a
>>domain or obtaining access to objects on that domian.
>>Have
>>you tried turning that off to see if you get a better
>>result. The only other thing I can think of is to
>ensure
>>that you don't have any other devices with the same
>naming
>>convention as what you are using to log in with.
>>
>>Hope this helps.
>>
>>Rich
>>
>>>-----Original Message-----
>>>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.
>>>.
>>>
>>.
>>

How is your client DNS set up?

Cheers,

Cliff

{MVP}

On Tue, 30 Mar 2004 11:19:45 -0800, "Josh"
wrote:

>Rich, I am not running XP's firewall on the machine. I
>have also changed the machine name to see if that would
>make a difference, and it did not help.
>
>Josh
>
>>-----Original Message-----
>>I have had a lot of problems with the Windows XP's
>>Personal Firewall and AD domains. For some reason when
>>that is running I have issues either with logging into a
>>domain or obtaining access to objects on that domian.
>Have
>>you tried turning that off to see if you get a better
>>result. The only other thing I can think of is to
>ensure
>>that you don't have any other devices with the same
>naming
>>convention as what you are using to log in with.
>>
>>Hope this helps.
>>
>>Rich
>>
>>>-----Original Message-----
>>>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.
>>>.
>>>
>>.
>>