On my Win2003 server I accidently removed a workstation(POS04) in AD
users and computers. I recreated the machine at the server now we get
the following event log message

I can reboot the POS04 workstation(XP Pro) and it acts like it logs in
fine and runs everythink ok, but the event log is and issue I'd like
to fix.

Any ideas?

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5722
Date: 2/13/2007
Time: 5:20:28 AM
User: N/A
Computer: SERVER3
Description:
The session setup from the computer POS04C failed to authenticate. The
name(s) of the account(s) referenced in the security database is POS04C
$. The following error occurred:
Access is denied.

For more information, see and Support Center at http://
go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0 "..À

On Feb 13, 7:43 am, lope...@gmail.com wrote:
> On my Win2003 server I accidently removed a workstation(POS04) in AD
> users and computers. I recreated the machine at the server now we get
> the following event log message
>
> I can reboot the POS04 workstation(XP Pro) and it acts like it logs in
> fine and runs everythink ok, but the event log is and issue I'd like
> to fix.
>
> Any ideas?
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5722
> Date: 2/13/2007
> Time: 5:20:28 AM
> User: N/A
> Computer: SERVER3
> Description:
> The session setup from the computer POS04C failed to authenticate. The
> name(s) of the account(s) referenced in the security database is POS04C
> $. The following error occurred:
> Access is denied.
>
> For more information, see and Support Center at http://
> go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 22 00 00 c0 "..À

Good morning!

The error, and subsequent 'bad behavior' are because the domain has a
new sid for the workstation, while the worstation is utilizing the old
sid. The fix is easy, however.

First, log on locally to the workstation, with the local admin
account. Then, remove the workstation from the domain by joining it
to a workgroup. The name of the workgroup doesn't matter, so long as
it removes itself from the domain. You should get a window saying
"Welcome to the xxxx workgroup!". You'll have to reboot the
workstation for the changes to take effect.

To ensure that the machine is removed from the domain, go to a
workstation or server that has the AD User and Computers snap-in.
Ensure that POS04 is not present. If it is, delete it. wait 12
minutes to ensure replication to all GC's, if you are in a large
environment.

Now, go back to the workstation, logging on as local administrator.
Join the machine back to the domain, utilizing an account that has
sufficient privileges.

Hope this s,
Derek

http://www.fortypoundhead.com

Good Morning,

I have the same error, but I can´t login in the object machine, I think the
problem was generated by a backup when my user wasn´t yet created... I'm not
sure, but after that was when the problems started!
There are some resistences to solving the problem :
-first I can´t login to the machine, and so I can´t rename the machine;
-I have reset the the machine, deleted and created a new one(with the same
name)
-I don´t have admin login,l already tried netdom reset <computername>
but I received rpc unavailable, and then I tested the rpc service,
everything alright,
I really don´t know if it is because of my priveliges???
-I have tested the DNS,ok!
....

Please give me some feedback!
Thanks in advance for your support

"Derek" wrote:

> On Feb 13, 7:43 am, lope...@gmail.com wrote:
> > On my Win2003 server I accidently removed a workstation(POS04) in AD
> > users and computers. I recreated the machine at the server now we get
> > the following event log message
> >
> > I can reboot the POS04 workstation(XP Pro) and it acts like it logs in
> > fine and runs everythink ok, but the event log is and issue I'd like
> > to fix.
> >
> > Any ideas?
> >
> > Event Type: Error
> > Event Source: NETLOGON
> > Event Category: None
> > Event ID: 5722
> > Date: 2/13/2007
> > Time: 5:20:28 AM
> > User: N/A
> > Computer: SERVER3
> > Description:
> > The session setup from the computer POS04C failed to authenticate. The
> > name(s) of the account(s) referenced in the security database is POS04C
> > $. The following error occurred:
> > Access is denied.
> >
> > For more information, see and Support Center at http://
> > go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 22 00 00 c0 "..À
>
> Good morning!
>
> The error, and subsequent 'bad behavior' are because the domain has a
> new sid for the workstation, while the worstation is utilizing the old
> sid. The fix is easy, however.
>
> First, log on locally to the workstation, with the local admin
> account. Then, remove the workstation from the domain by joining it
> to a workgroup. The name of the workgroup doesn't matter, so long as
> it removes itself from the domain. You should get a window saying
> "Welcome to the xxxx workgroup!". You'll have to reboot the
> workstation for the changes to take effect.
>
> To ensure that the machine is removed from the domain, go to a
> workstation or server that has the AD User and Computers snap-in.
> Ensure that POS04 is not present. If it is, delete it. wait 12
> minutes to ensure replication to all GC's, if you are in a large
> environment.
>
> Now, go back to the workstation, logging on as local administrator.
> Join the machine back to the domain, utilizing an account that has
> sufficient privileges.
>
> Hope this s,
> Derek
>
> http://www.fortypoundhead.com
>
>

On Feb 14, 1:57 am, Hugo Vaz Sousa <Hugo Vaz
S...@discussions.microsoft.com> wrote:
> Good Morning,
>
> I have the same error, but I can´t login in the object machine, I thinkthe
> problem was generated by a backup when my user wasn´t yet created... I'm not
> sure, but after that was when the problems started!
> There are some resistences to solving the problem :
> -first I can´t login to the machine, and so I can´t rename the machine;
> -I have reset the the machine, deleted and created a new one(with the same
> name)
> -I don´t have admin login,l already tried netdom reset <computername>
> but I received rpc unavailable, and then I tested the rpc service,
> everything alright,
> I really don´t know if it is because of my priveliges???
> -I have tested the DNS,ok!
> ...
>
> Please give me some feedback!
> Thanks in advance for your support
>
> "Derek" wrote:
> > On Feb 13, 7:43 am, lope...@gmail.com wrote:
> > > On my Win2003 server I accidently removed a workstation(POS04) in AD
> > > users and computers. I recreated the machine at the server now we get
> > > the following event log message
>
> > > I can reboot the POS04 workstation(XP Pro) and it acts like it logs in
> > > fine and runs everythink ok, but the event log is and issue I'd like
> > > to fix.
>
> > > Any ideas?
>
> > > Event Type: Error
> > > Event Source: NETLOGON
> > > Event Category: None
> > > Event ID: 5722
> > > Date: 2/13/2007
> > > Time: 5:20:28 AM
> > > User: N/A
> > > Computer: SERVER3
> > > Description:
> > > The session setup from the computer POS04C failed to authenticate. The
> > > name(s) of the account(s) referenced in the security database is POS04C
> > > $. The following error occurred:
> > > Access is denied.
>
> > > For more information, see and Support Center at http://
> > > go.microsoft.com/fwlink/events.asp.
> > > Data:
> > > 0000: 22 00 00 c0 "..À
>
> > Good morning!
>
> > The error, and subsequent 'bad behavior' are because the domain has a
> > new sid for the workstation, while the worstation is utilizing the old
> > sid. The fix is easy, however.
>
> > First, log on locally to the workstation, with the local admin
> > account. Then, remove the workstation from the domain by joining it
> > to a workgroup. The name of the workgroup doesn't matter, so long as
> > it removes itself from the domain. You should get a window saying
> > "Welcome to the xxxx workgroup!". You'll have to reboot the
> > workstation for the changes to take effect.
>
> > To ensure that the machine is removed from the domain, go to a
> > workstation or server that has the AD User and Computers snap-in.
> > Ensure that POS04 is not present. If it is, delete it. wait 12
> > minutes to ensure replication to all GC's, if you are in a large
> > environment.
>
> > Now, go back to the workstation, logging on as local administrator.
> > Join the machine back to the domain, utilizing an account that has
> > sufficient privileges.
>
> > Hope this s,
> > Derek
>
> >http://www.fortypoundhead.com


Have you tried using a password recovery boot disk to recover the
login information for the local machine?