Hi

I have configured 802.1x and Machine authentication for my windows domain.
The authentication works fine. However, some machines later fail to
authenticate with Active Directory. The radius logs show that the machine
supplied a wrong password. The solution is to re-add the machine to the
network.

What causes the machine to fail authentication with AD yet it is part of the
domain.

Is there a way this can be avoided?

Hubdocs

You need to ask your question in a newsgroup devoted to you version of
Windows; this one is about security in Access, the database product.

--
Joan Wild
Microsoft Access MVP
"hubdocs" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> I have configured 802.1x and Machine authentication for my windows domain.
> The authentication works fine. However, some machines later fail to
> authenticate with Active Directory. The radius logs show that the machine
> supplied a wrong password. The solution is to re-add the machine to the
> network.
>
> What causes the machine to fail authentication with AD yet it is part of
> the domain.
>
> Is there a way this can be avoided?
>
> Hubdocs
>

Hi, did you posted your question in other newsgroup? I have the same problem
- did you solved it?

"hubdocs" wrote:

> Hi
>
> I have configured 802.1x and Machine authentication for my windows domain.
> The authentication works fine. However, some machines later fail to
> authenticate with Active Directory. The radius logs show that the machine
> supplied a wrong password. The solution is to re-add the machine to the
> network.
>
> What causes the machine to fail authentication with AD yet it is part of the
> domain.
>
> Is there a way this can be avoided?
>
> Hubdocs
>
>
>