Re: Configurijng IAS on W2K3
- From: "Carl Hilton" <someone@xxxxxxxxxxxxx>
- Date: Thu, 19 Jan 2006 09:04:30 -0500
Got this one figured out... Had to set DefaultDomain so that passwords were
checked against the local users group.
<carlvh@xxxxxxxxx> wrote in message
news:1137591418.553020.122840@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Ok, I have a W2K3 IAS running and it is supposed to authenticate users
> against the LOCAL users on the IAS machine. However folks are NOT
> getting authenticated...
>
> EVENT log:
> Event Type: Warning
> Event Source: IAS
> Event Category: None
> Event ID: 2
> Date: 1/18/2006
> Time: 7:50:26 AM
> User: N/A
> Computer: MYRADIUS
> Description:
> User user223 was denied access.
> Fully-Qualified-User-Name = CORP\user223
> NAS-IP-Address = 192.168.53.10
> NAS-Identifier = <not present>
> Called-Station-Identifier = 5558005
> Calling-Station-Identifier = 4015558000
> Client-Friendly-Name = CISCO3640
> Client-IP-Address = 192.168.53.10
> NAS-Port-Type = Async
> NAS-Port = 2
> Proxy-Policy-Name = Use Windows authentication for all users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Policy-Name = <undetermined>
> Authentication-Type = MS-CHAPv1
> EAP-Type = <undetermined>
> Reason-Code = 16
> Reason = Authentication was not successful because an unknown user
> name or incorrect password was used.
>
.
- References:
- Configurijng IAS on W2K3
- From: carlvh
- Configurijng IAS on W2K3
- Prev by Date: Re: Multiple AP problem
- Next by Date: Pattern Matching
- Previous by thread: Configurijng IAS on W2K3
- Next by thread: IAS and EAP-MD5
- Index(es):
Relevant Pages
|
