I'm using SBS 2003. I've had tow users in two days with login problems.
They get an error indicating that the domain controller may not be available
or that their computer account can't be found. I have fixed the problem by
removing the computer from the domain and rejoining, but why is this
happening? This is an error in the System log that I think pertains to the
problem:

The session setup from the computer WKSTN513 failed to authenticate. The
name(s) of the account(s) referenced in the security database is WKSTN513$.
The following error occurred:
Access is denied.



Thanks!

Please have a look:

http://support.microsoft.com/kb/216393/en-us

With kind regards
Krystian Zieja
http://www.projectenvision.com

"Just Guessing" wrote:

> I'm using SBS 2003. I've had tow users in two days with login problems.
> They get an error indicating that the domain controller may not be available
> or that their computer account can't be found. I have fixed the problem by
> removing the computer from the domain and rejoining, but why is this
> happening? This is an error in the System log that I think pertains to the
> problem:
>
> The session setup from the computer WKSTN513 failed to authenticate. The
> name(s) of the account(s) referenced in the security database is WKSTN513$.
> The following error occurred:
> Access is denied.
>
> Thanks!

The article describes the computer account mechanism, but why does it break?
I also noticed licensing errors in the event logs. I'm over by about 5
client access licenses. Is it possible the server is disconnecting computer
accounts because of too few licenses?

"Krystian Zieja" wrote:

> Please have a look:
>
> http://support.microsoft.com/kb/216393/en-us
>
> With kind regards
> Krystian Zieja
> http://www.projectenvision.com
>
> "Just Guessing" wrote:
>

> > I'm using SBS 2003. I've had tow users in two days with login problems.
> > They get an error indicating that the domain controller may not be available
> > or that their computer account can't be found. I have fixed the problem by
> > removing the computer from the domain and rejoining, but why is this
> > happening? This is an error in the System log that I think pertains to the
> > problem:
> >
> > The session setup from the computer WKSTN513 failed to authenticate. The
> > name(s) of the account(s) referenced in the security database is WKSTN513$.
> > The following error occurred:
> > Access is denied.
> >
> > Thanks!

If you got too few cals installed in SBS 2003 there will be an EventLog entry
for that. The other possibility is that users which exceeds your CALS, won't
be able to login, but the computers will not be "disconnected"

With kind regards
Krystian Zieja
http://www.projectenvision.com

"Just Guessing" wrote:

> The article describes the computer account mechanism, but why does it break?
> I also noticed licensing errors in the event logs. I'm over by about 5
> client access licenses. Is it possible the server is disconnecting computer
> accounts because of too few licenses?
>
> "Krystian Zieja" wrote:
>

> > Please have a look:
> >
> > http://support.microsoft.com/kb/216393/en-us
> >
> > With kind regards
> > Krystian Zieja
> > http://www.projectenvision.com
> >
> > "Just Guessing" wrote:
> >

> > > I'm using SBS 2003. I've had tow users in two days with login problems.
> > > They get an error indicating that the domain controller may not be available
> > > or that their computer account can't be found. I have fixed the problem by
> > > removing the computer from the domain and rejoining, but why is this
> > > happening? This is an error in the System log that I think pertains to the
> > > problem:
> > >
> > > The session setup from the computer WKSTN513 failed to authenticate. The
> > > name(s) of the account(s) referenced in the security database is WKSTN513$.
> > > The following error occurred:
> > > Access is denied.
> > >
> > > Thanks!

Since you've run into this twice, I would troubleshoot it rather than just
disjoining and rejoining the PCs. If there's a configuration or other issue
behind this, you're just putting a band aid on it until it happens again.

I'd start by checking the event logs on the workstation (system and
application). Troubleshoot or post back on any errors. Then when this
happens, check all your network connectivity - can you ping server to
workstation and workstation to server, using both name and IP address. If
you run an ipconfig /all on the workstation, is everything correct (post it
or compare to a properly working PC). Are group policies applying properly
on the client PCs (application log or open a cmd prompt and type "gpupdate
/force," watch for errors, then when it completes check system and
application logs).

In what context are you getting the error you posted? At startup, login,
randomly? Are these XP or Vista? Are these PCs that have been functioning
normally for a while and are now doing this? If so, what changed?


"Just Guessing" <JustGuessing@newsgroup> wrote in message
news:FAF6932B-EA02-4C2D-871A-D11ECF5974D6@newsgroup

> I'm using SBS 2003. I've had tow users in two days with login problems.
> They get an error indicating that the domain controller may not be
> available
> or that their computer account can't be found. I have fixed the problem
> by
> removing the computer from the domain and rejoining, but why is this
> happening? This is an error in the System log that I think pertains to
> the
> problem:
>
> The session setup from the computer WKSTN513 failed to authenticate. The
> name(s) of the account(s) referenced in the security database is
> WKSTN513$.
> The following error occurred:
> Access is denied.
>
> Thanks!

In article <FAF6932B-EA02-4C2D-871A-D11ECF5974D6@newsgroup>,
JustGuessing@newsgroup says...

>
> I'm using SBS 2003. I've had tow users in two days with login problems.
> They get an error indicating that the domain controller may not be available
> or that their computer account can't be found. I have fixed the problem by
> removing the computer from the domain and rejoining, but why is this
> happening? This is an error in the System log that I think pertains to the
> problem:
>
> The session setup from the computer WKSTN513 failed to authenticate. The
> name(s) of the account(s) referenced in the security database is WKSTN513$.
> The following error occurred:
> Access is denied.
>
> Thanks!

One common issue that causes this is a Bug in Antivirus software running
on the server and/or workstations. I've seen this many times....

What Antivirus solution are you using, specific version numbers are
needed.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free@newsgroup (remove 999 for proper email address)