<![CDATA[[SecurityRatty] tag: wzcsvc]]> http://securityratty.com/tag/wzcsvc Wed, 23 Jul 2008 09:59:30 +0000 iRatty Engine http://blogs.law.harvard.edu/tech/rss <![CDATA[Wired 802.1X and Windows XP SP3- Yes you can!]]> http://securityratty.com/article/0178304882a872ac541258a4d798bda7 http://securityratty.com/article/0178304882a872ac541258a4d798bda7 I’ve gotten a lot of questions recently about using 802.1X on the wired interface with Windows XP SP3. In the past few weeks I’ve also stumbled across a lot of forum posts, blogs and articles stating you ‘can’t do wired 802.1X with XP SP3.”

Well, sure you can! There is a little trick now, though.

As part of the move to the Microsoft NAP integration, they’ve broken out the wired and wireless supplicant management into two pieces. Until SP3, all 1X was handled in the Wireless Zero Configuration (WZCSVC) service. The wired 1X supplicant is handled now by a different service and must be manually started.

In Windows XP SP3, the supplicants are each handled separately by these services…
    •  Wireless 802.1X: WZCSVC service
    •  Wired 802.1X: Wired AutoConfig service (DOT3SVC)

How do you start the Wired AutoConfig service? Two ways, the end user (or admin) can do it manually on the endpoint, or you can push it out with group policies.

Instead of duplicating a lott’a text, you can find detailed instructions for manual and pushed wired 1X configurations on Microsoft KB article 953650.

You can also learn more about Microsoft NAP integration in the Network Access Protection Q&A site.

# # #

]]> Wed, 23 Jul 2008 09:59:30 +0000 wired wzcsvc service wzcsvc service wired autoconfig service wired interface sp3 microsoft microsoft nap integration Wired 802.1X and Windows XP SP3- Yes you can!