PEAP Authentication Fails

Hi,

We use a Cisco environment with Windows 2000 Clients (+ 802.1x supplicant).
The supplicant authenticates to our ACS radius server which ACS accepts.
We see that the client states to be "authenticated".
Now, 1-3 seconds later, the client starts reauthentication which our ACS
accepts again, but the client does not.

I've enabled "netsh ras set tracing * en" on the client which resulted in
the following output (see weblink)

Can anybody tell me what's going on and why we've got these failures?

Regards,

Erik Tamminga
etamminga@xxxxxxxxxxx

See http://www.etamminga.nl/8021x for the netsh generated log files.


.

Relevant Pages

  • Re: Any troubleshooting tips for remotesp.tsp?
    ... > what OS/SP is running on the TAPI Server? ... > Was the currently logged in user on the client the first user to login ... > netsh ras set tracing remotesp enable ...
    (microsoft.public.win32.programmer.tapi)
  • Re: TAPI and Win XP SP2
    ... > We made the check with netstat and the status on the client is WAITING. ... >> You may want to trace the TAPI components on client and server: ... >> netsh ras set tracing remotesp enable ...
    (microsoft.public.win32.programmer.tapi)
  • Re: PEAP with MS-CHAPv2 authentication on IAS
    ... both client and server machine: ... netsh ras set tra * en ... The IAS is running on a Windows 2000 Server with SP4 and my ...
    (microsoft.public.internet.radius)
  • Re: TAPI and Win XP SP2
    ... We made the check with netstat and the status on the client is WAITING. ... then telephony Server. ... > netsh ras set tracing remotesp enable ...
    (microsoft.public.win32.programmer.tapi)
  • Re: XP Clients cannot login VPN
    ... Client and the XP Client. ... netsh ras set tra * dis ... I am able to connect to it with a Windows ... > 2000 Pro client, but cannot connect to it with a Windows XP Pro or XP Home ...
    (microsoft.public.win2000.ras_routing)
Loading