Can't authenticate to radius server, with Windows 7
Hello all! I think the posting title describes my dilemma well. Here are some of the specifics. At my institute of work, we all authenticate our wireless connections via a radius server, which is a Windows Server 2003 Enterprise R2 Virtual PC, on a physical host of the exact same OS persuasion. I'm testing the Windows 7 RTM (Enterprise) on our domain network (we're running Windows Server 2008 Enterprise controllers), and can never seem to get my work-laptop to authenticate for wireless. I have all Windows Firewalls shut off. I type in the proper SSID when prompted in the Wireless Network Connection... all to no avail. It sits there for awhile as if it's trying to connect, and then errors out with "Windows was unable to connect to the wireless network." Also, the name of my laptop is in the OU that we've set aside for wireless authentication--that doesn't seem to matter, though. It acts no differently than as if it were in the default "Computer" OU. Has anyone had issues similar to this? That, or with the above description of radius and domain controller, is there a configuration that I am missing somewhere, server side? I thank any and everybody in advance for any feedback they can provide me in this matter.
August 25th, 2009 6:00am

If you are running IAS server as RADIUS server, please check the RADIUS server's system event log. You may find the corresponding logs with source: IAS or RemoteAccess. Sometime, the information is helpful for troubleshooting.
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2009 3:56pm

Thank you for your reply, and advice; I thought nobody would answer! :) I'll look into those logs this Monday, and get back with what I find.
August 29th, 2009 1:15pm

Going into the logfiles (C:\Windows\System32\LogFiles), all I'm finding is directories in 2008, for Cluster, Firewall, Scm, Shutdown, WMI, and WUDF--where should I start looking here, for the IAS/RADIUS logs? Wireless still not working. Tried to click the "Connect, even when network is not broadcasting option," but it's grayed-out, saying I need admin privileges. I AM the admin on the machine. Encryption and authentication are set at TKIP and PEAP, which they should be (WPA-Enterprise is the network type). Looking forward to any and all feedback.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2009 12:14am

Is the wireless network profile pushed to yourmachine by group policy? If so, you cannot change the settings even if you are an admin on the machine.To troubleshoot the wireless issue, you can take a look at the event logs in the event viewer. The path is "Applications and Services Logs/Microsoft/Windows/WLAN-AutoConfig/Operational".
September 11th, 2009 1:52am

This is what I get in the logs: Log Name: Microsoft-Windows-WLAN-AutoConfig/Operational Source: Microsoft-Windows-WLAN-AutoConfig Date: 9/14/2009 9:04:59 AM Event ID: 11002 Task Category: MsmAssociation Level: Error Keywords: (512) User: SYSTEM Computer: NAME.123.abc.ab.local Description: Wireless network association failed. Network Adapter: Dell Wireless 1395 WLAN Mini-Card Interface GUID: {1c2bac05-d4d1-49de-aeb4-8d1c97554227} Local MAC Address: 00:16:44:DC:3F:A0 Network SSID: mti BSS Type: Infrastructure Failure Reason: The driver disconnected while associating. Dot11 Status Code: 2 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WLAN-AutoConfig" Guid="{9580D7DD-0379-4658-9870-D5BE7D52D6DE}" /> <EventID>11002</EventID> <Version>0</Version> <Level>2</Level> <Task>24011</Task> <Opcode>195</Opcode> <Keywords>0x8000000000000200</Keywords> <TimeCreated SystemTime="2009-09-14T14:04:59.082908200Z" /> <EventRecordID>112</EventRecordID> <Correlation /> <Execution ProcessID="904" ThreadID="1176" /> <Channel>Microsoft-Windows-WLAN-AutoConfig/Operational</Channel> <Computer>NAME.123.abc.ab.local</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="Adapter">Dell Wireless 1395 WLAN Mini-Card</Data> <Data Name="DeviceGuid">{1C2BAC05-D4D1-49DE-AEB4-8D1C97554227}</Data> <Data Name="LocalMac">00:16:44:DC:3F:A0</Data> <Data Name="SSID">mti</Data> <Data Name="BSSType">Infrastructure</Data> <Data Name="FailureReason">The driver disconnected while associating.</Data> <Data Name="ReasonCode">229378</Data> <Data Name="Dot11StatusCode">2</Data> <Data Name="ConnectionId">0x9</Data> </EventData> </Event> Also, I get this: Log Name: Microsoft-Windows-WLAN-AutoConfig/Operational Source: Microsoft-Windows-WLAN-AutoConfig Date: 9/14/2009 9:04:59 AM Event ID: 8002 Task Category: AcmConnection Level: Error Keywords: (512) User: SYSTEM Computer: NAME.123.abc.ab.local Description: WLAN AutoConfig service failed to connect to a wireless network. Network Adapter: Dell Wireless 1395 WLAN Mini-Card Interface GUID: {1c2bac05-d4d1-49de-aeb4-8d1c97554227} Connection Mode: Connection to a secure network without a profile Profile Name: mti SSID: mti BSS Type: Infrastructure Failure Reason:The specific network is not available. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WLAN-AutoConfig" Guid="{9580D7DD-0379-4658-9870-D5BE7D52D6DE}" /> <EventID>8002</EventID> <Version>0</Version> <Level>2</Level> <Task>24010</Task> <Opcode>191</Opcode> <Keywords>0x8000000000000200</Keywords> <TimeCreated SystemTime="2009-09-14T14:04:59.082908200Z" /> <EventRecordID>113</EventRecordID> <Correlation /> <Execution ProcessID="904" ThreadID="1176" /> <Channel>Microsoft-Windows-WLAN-AutoConfig/Operational</Channel> <Computer>NAME.123.abc.ab.local</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="InterfaceGuid">{1C2BAC05-D4D1-49DE-AEB4-8D1C97554227}</Data> <Data Name="InterfaceDescription">Dell Wireless 1395 WLAN Mini-Card</Data> <Data Name="ConnectionMode">Connection to a secure network without a profile</Data> <Data Name="ProfileName">mti</Data> <Data Name="SSID">mti</Data> <Data Name="BSSType">Infrastructure</Data> <Data Name="FailureReason">The specific network is not available.</Data> <Data Name="ReasonCode">163851</Data> <Data Name="ConnectionId">0x9</Data> </EventData> </Event> Mind you, this is now (as of today) after ca clean handload of Win 7 this weekend. I've tried the Dell Broadcom wireless driver supplied by Dell, and the "plug-and-play" version from the Windows 7 install ISO itself. Both to no avail. Firewalls are off, my NetBIOS name is still in the appropriate OU, etc., etc... Your thoughts? Thanks for all the suggestions you've given thus far.
Free Windows Admin Tool Kit Click here and download it now
September 14th, 2009 6:42pm

This is a layer-2 failure (i.e. the wireless card failed to associate with the access point). It has nothing to do with firewall etc.Unfortunately, the Dot11 status codereturned by the driver is a generic error.What is the version of the driver? Could you try Windows Update to see ifa newer driver is available?
September 16th, 2009 12:58am

I've tried both updating to the latest driver I could find (while making sure the Broadcom utility was not installed on the machine, as it has been know to cause issues with Vista), and even an HP version of the Broadcom driver, as many on the Technet forums have seemed to have had issues with the Bradcom Dell driver as of late--both on Win7 and Vista. No luck. I even uninstalled the wireless altogether, and went with the driver that comes installed with the Windows 7 installation, as many thought a rollback would even help the matter,since it worked for them. No go. Yet, when I take my laptop home to do work, it finds my home network no problem (which is WPA2 Personal, as opposed to my works WPA2 Enterprise). REALLY weird... Here is the 411 on my driver, as of today: Dell wireless 1395 WLAN Mini-Card (Broadcom) Driver Provider: Microsoft Driver Date: 10/1/2008 Driver Version: 4.176.75.23 Digital Signer: Microsoft Windows Hardware Compatability Publisher In event viewer, there is a log as of 5 minutes ago that reads of an Explicit Eap failure received, for my card. The entry is as follows: Log Name: Microsoft-Windows-WLAN-AutoConfig/Operational Source: Microsoft-Windows-WLAN-AutoConfig Date: 9/16/2009 11:55:39 AM Event ID: 8004 Task Category: None Level: Error Keywords: User: SYSTEM Computer: MOSSMAN.mti.tec.sd.local Description: Wireless network is blocked due to connection failure. Network Adapter: Dell Wireless 1395 WLAN Mini-Card Interface GUID: {1d5b6f9d-be0b-4613-8d2c-48534e71635b} Connection Mode: Automatic connection with a profile Profile Name: MTITC SSID(s): MTITC BSS Type: Infrastructure Failure Reason:Explicit Eap failure received Length of block timer (minutes): 20 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WLAN-AutoConfig" Guid="{9580D7DD-0379-4658-9870-D5BE7D52D6DE}" /> <EventID>8004</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2009-09-16T16:55:39.912476000Z" /> <EventRecordID>1213</EventRecordID> <Correlation /> <Execution ProcessID="876" ThreadID="2224" /> <Channel>Microsoft-Windows-WLAN-AutoConfig/Operational</Channel> <Computer>MOSSMAN.mti.tec.sd.local</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="InterfaceDescription">Dell Wireless 1395 WLAN Mini-Card</Data> <Data Name="InterfaceGuid">{1D5B6F9D-BE0B-4613-8D2C-48534E71635B}</Data> <Data Name="SSID(s)">MTITC</Data> <Data Name="ProfileName">MTITC</Data> <Data Name="ConnectionMode">Automatic connection with a profile</Data> <Data Name="BSSType">Infrastructure</Data> <Data Name="FailureReason">Explicit Eap failure received</Data> <Data Name="BlockTime">20</Data> <Data Name="ReasonCode">327685</Data> <Data Name="ConnectionId">0x9</Data> </EventData> </Event> Under change adapter settings, it shows that the WNIC is in a "loop" of trying to authenticate. It's show "Not COnnected" if I try to join the network by entering the SSID, and then go right back to attempting to authenticate. Again, thank you for your assistance in all this.
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2009 8:00pm

As no one was able to help me, and as others are having some of the same issues with their 7/Broadcom installs, I would like to just mark this thread close please. Ironically, I set my OS back to Vista, which can see the radius on the same WNIC. After getting it where I wanted it with apps, I ran an upgrade to 7, and all seems to be working so far. Not a very practical workaround for deployment... but I guess this just means that we'll order Intel wireless cards from now on. :) Thanks to all who helped; or tried.
October 13th, 2009 11:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics