| Jeremy 2007-02-07, 1:17 pm |
| I've tried that. Originally I put both the domain users and domain computers
groups into the access policy, but also tried making a special group just for
wireless access, still no go. My test PC is in the same domain as the IAS
server, so that should make it simple.
On a similar note, in my testing I could remove the domain users group from
the access policy, and would get an access denied error for user
authentication. However when I remove the domain computers group from the
access policy I did not receive an access denied message for the machine
authentication, just the same error as before, about invalid account. So I
assume from that that the error is generated before an access decision is
made.
"Lee" wrote:
> On Feb 2, 4:36 pm, Jeremy <Jer...@discussions.microsoft.com> wrote:
>
> What I would do is create a group of wireless enabled computers. Add
> the computer objects to that group, then you add that group to the
> access policy and this should fix that problem. If the computers
> don't belong to the domain, then you will want to prompt for the
> username and password, and turn off machine authentication on the
> computer. I had this same problem. With Domain computers, I'm not
> sure why the computers need to auth, but they do for a first time
> login to work on that laptop.
>
>
|