Archived from groups: microsoft.public.windows.networking.wireless (More info?)
Is there a means to force the native W2K/XP 802.1.x supplicant to initiate a
re-authentication by sending an EAPOL-Start? Maybe netsh? WMI script?
Win32 API?
At this time, we can only get the supplicants to re-auth by
disabling/enabling the NIC (doesn't always work as some NICs don't drop link
on disable) or un-plugging the NIC. The later always works as the switch
will initiate a new authentication session by sending an
EAP-Request/Identity.
We like to find a means to force the client to initiate the re-auth. Any
ideas?
--
Tony (un-monitored email reply via post)
Is there a means to force the native W2K/XP 802.1.x supplicant to initiate a
re-authentication by sending an EAPOL-Start? Maybe netsh? WMI script?
Win32 API?
At this time, we can only get the supplicants to re-auth by
disabling/enabling the NIC (doesn't always work as some NICs don't drop link
on disable) or un-plugging the NIC. The later always works as the switch
will initiate a new authentication session by sending an
EAP-Request/Identity.
We like to find a means to force the client to initiate the re-auth. Any
ideas?
--
Tony (un-monitored email reply via post)