[37875] in Resnet-Forum
Re: Windows 8 wireless problems
daemon@ATHENA.MIT.EDU (Cary Burnette)
Thu Jan 17 15:21:33 2013
X-Barracuda-Envelope-From: kerm@ncat.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 006FCB1B85257AF6_="
Message-ID: <OF1AC85848.9267D51C-ON85257AF6.006F8384-85257AF6.006FCB1D@ncat.edu>
Date: Thu, 17 Jan 2013 15:20:52 -0500
Reply-To: Resnet Forum <RESNET-L@LISTSERV.ND.EDU>
From: Cary Burnette <kerm@ncat.edu>
To: RESNET-L@LISTSERV.ND.EDU
In-Reply-To: <B3C0241889401F4AB97A55E980BABBA001591E350EC6@EXV01.wcu.edu>
This is a multipart message in MIME format.
--=_alternative 006FCB1B85257AF6_=
Content-Type: text/plain; charset="US-ASCII"
You did not say if you are using Cisco wireless or not. There is a bug in
certain versions of the Cisco wireless controller that effects Windows 8.
See link:
https://supportforums.cisco.com/docs/DOC-27213
------------------
Cary Burnette (kerm@ncat.edu)
Network Services, DoIT
NC A&T State University
038 IRC
Greensboro, NC 27411
336-285-2392 (Direct)
336-334-3833 (Fax)
From: Andy Voelker <avoelker@email.wcu.edu>
To: RESNET-L@LISTSERV.ND.EDU,
Date: 01/17/2013 03:15 PM
Subject: Windows 8 wireless problems
Sent by: Resnet Forum <RESNET-L@LISTSERV.ND.EDU>
Is anyone else having massive problems getting windows 8 an on 802.1x
WPA2-Enterprise wireless network? We are seeing the following issues:
1. Drivers shipped with budget computers lack the necessary components to
pass credentials. Many of these manufacturers are shipping drivers from
Feb. 2012, which means they were tested on consumer preview only. Of
course some manufacturers have updates and some don't. Some we have to go
to other sources to get drivers for. To remedy this, our only option is
to hook in a USB wireless adapter with good drivers until the proper
driver updates are cleared. At this point the blame appears on us because
those people can connect to home networks, Starbucks, etc. We are going
to purchase a few wireless cards to go in our multimedia checkout system
for desperate cases.
2. We call this one "sticky credentials". I, as a staff member, can log
in to the wireless network on a student computer and it will pass
credentials and work. If a student puts their credentials in, the process
fails before it hits Radius. I check all the logs and nothing has gone
through that username. I have cleared the wireless profile in netsh and
made sure it was forgotten in the GUI. I have also cleared off all
certificates. Does anyone know where Windows saves 802.1x credentials so
I can make sure to nuke it as well?
If you have any ideas, let me know. Thanks!
-- Andy Voelker
Manager of Student Computing in the Technology Commons
WCU Staff Senator (Professional Category), UNC Staff Assembly member
Western Carolina University
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--=_alternative 006FCB1B85257AF6_=
Content-Type: text/html; charset="US-ASCII"
<font size=2 face="sans-serif">You did not say if you are using Cisco
wireless or not. There is a bug in certain versions of the Cisco wireless
controller that effects Windows 8. See link:</font>
<br>
<br><a href="https://supportforums.cisco.com/docs/DOC-27213"><tt><font size=2>https://supportforums.cisco.com/docs/DOC-27213</font></tt></a>
<br><font size=2 face="sans-serif"> </font>
<br><font size=2 face="sans-serif">------------------<br>
Cary Burnette (kerm@ncat.edu)<br>
Network Services, DoIT<br>
NC A&T State University<br>
038 IRC<br>
Greensboro, NC 27411<br>
<br>
336-285-2392 (Direct)<br>
336-334-3833 (Fax)<br>
<br>
<br>
<br>
<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Andy Voelker <avoelker@email.wcu.edu></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">RESNET-L@LISTSERV.ND.EDU,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">01/17/2013 03:15 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Windows 8 wireless
problems</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">Resnet Forum
<RESNET-L@LISTSERV.ND.EDU></font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Is anyone else having massive problems getting windows
8 an on 802.1x WPA2-Enterprise wireless network? We are seeing the
following issues:<br>
<br>
1. Drivers shipped with budget computers lack the necessary components
to pass credentials. Many of these manufacturers are shipping drivers
from Feb. 2012, which means they were tested on consumer preview only.
Of course some manufacturers have updates and some don't. Some
we have to go to other sources to get drivers for. To remedy this,
our only option is to hook in a USB wireless adapter with good drivers
until the proper driver updates are cleared. At this point the blame
appears on us because those people can connect to home networks, Starbucks,
etc. We are going to purchase a few wireless cards to go in our multimedia
checkout system for desperate cases.<br>
<br>
2. We call this one "sticky credentials". I, as a
staff member, can log in to the wireless network on a student computer
and it will pass credentials and work. If a student puts their credentials
in, the process fails before it hits Radius. I check all the logs
and nothing has gone through that username. I have cleared the wireless
profile in netsh and made sure it was forgotten in the GUI. I have
also cleared off all certificates. Does anyone know where Windows
saves 802.1x credentials so I can make sure to nuke it as well?
<br>
<br>
If you have any ideas, let me know. Thanks!<br>
<br>
<br>
-- Andy Voelker<br>
Manager of Student Computing in the Technology Commons<br>
WCU Staff Senator (Professional Category), UNC Staff Assembly member<br>
Western Carolina University<br>
<br>
___________________________________________________<br>
You are subscribed to the ResNet-L mailing list.<br>
<br>
To subscribe, unsubscribe or search the archives,<br>
go to </font></tt><a href="http://listserv.nd.edu/archives/resnet-l.html"><tt><font size=2>http://LISTSERV.ND.EDU/archives/resnet-l.html</font></tt></a><tt><font size=2><br>
___________________________________________________<br>
</font></tt>
<br><br>NOTICE: This e-mail correspondence is subject to Public Records Law and may be disclosed to third parties.
­­
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to <a href="http://LISTSERV.ND.EDU/archives/resnet-l.html" target="_blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a>
___________________________________________________
--=_alternative 006FCB1B85257AF6_=--
