Networking-Forums.com

Professional Discussions => Security => Topic started by: jinxer on January 10, 2015, 03:28:47 AM

Title: 802.1x supplicant
Post by: jinxer on January 10, 2015, 03:28:47 AM
Do you use the native OS supplicant or a 3rd party one like Anyconnect?

Please share your experience..
Title: Re: 802.1x supplicant
Post by: killabee on January 10, 2015, 03:33:44 AM
We use native.  It works pretty well on our client OSes (Win 7/8, Mac, etc).
Title: Re: 802.1x supplicant
Post by: jinxer on January 10, 2015, 06:05:31 AM
Ok, sweet. Were about to implement ISE so im curious about it for the wired part.. Been hearing mixed reviews esp about windows.


Sent from my iPhone using Tapatalk
Title: Re: 802.1x supplicant
Post by: srg on January 10, 2015, 06:39:30 AM
Did a deployment a couple of years ago in a  mixed WinXP/7 environment and choose Ciscos supplicant to get the same behavior independent of OS.
Title: Re: 802.1x supplicant
Post by: deanwebb on January 10, 2015, 07:55:04 AM
The Cisco client makes the ISE client side much, much, much easier. I would consider it indispensable to a rollout.

The Windows supplicant behavior can be erratic.

Also, be sure to set up the ISE as a trust point for CA in your PKI system. If you use Windows Server as a CA, this can be done in AD.
Title: Re: 802.1x supplicant
Post by: jinxer on January 10, 2015, 04:02:26 PM
Yea, will probably end up using Anyconnect..


Sent from my iPhone using Tapatalk
Title: Re: 802.1x supplicant
Post by: Reggle on January 11, 2015, 05:14:38 AM
I used the native client so far.
Currently it's stable. Currently... Because we've twice had a wave of "no connection" issues after Windows updates, that disappeared after a new update.
Title: Re: 802.1x supplicant
Post by: deanwebb on January 11, 2015, 11:47:50 AM
Windows updates can really ruin a guy's day when they crash the app he's in charge of.