802.1x or Aegis protocol

Question

I have a D620 with a TrueMobile 1490 with the driver that is,  currently in the 'Drivers' section on support.dell.com. I am trying to connect to a Foundry Networks Ironpoint 200. Every other machine connects just fine, except mine. We use certificate based authentication, and i have everthing needed on this machine to connect (i.e.- permissions, group membership, etc.) The only difference that i notice between my machine and a machine that will connect, is that i do not have a 802.1x protocol bound to my wireless NIC ('Aegis' or 'WPA Supplicant') . I noticed that drivers for the 13xx series TrueMobile NICs come with it and it is installed when the driver is installed. This is a new card and will not take that driver though. Where can i get this protocol as a download or how can i bind this protocol to the NIC. I know it is not part of windows, and i cant seem to find it anywhere to download. Thanks in advance for any help.

NemesisDB · Answer

aegis or any other WPA supplicant is just a 3rd party WPA supplicant that are usually bundled with network utility programs. they let the utility support WPA even if the OS does not support it natively.

WPA has been native to windows XP since SP2 and was available as a rollup patch to SP1. WPA2 support can be added on to the native windows environment as well:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=009d8425-ce2b-47a4-abec-274845dc9e91

tekno_guru · Answer

Thank you for the reply. I knew Windows supported it, but for whatever reason Windows is not passing the certificate. As a experiment, i had some one un check the binding on their wireless NIC and they could no longer connect. How can i bind the protocol to the NIC? If i am wrong i am wrong, but i need to try this. It is the only difference between connecting and not, that i can see.

NemesisDB · Answer

is the protocal currently installed on the system?

tekno_guru · Answer

no it is not installed on the system. And i can not add it through the protocol dialog in the properties for the NIC. It should be installed by the driver for the NIC, as it has in the  past. Dell released a updated management console that has 802.1x as a option, but my work network requires a certificate for the machine and for the user. The updated wireless management console does not address this issue. It only allows for one certificate. What i need is a protocol that i can BIND to the NIC, not some new feature in a console. I dont understand why this is such a problem, as it has come with the drivers for the the older 13xx series wireless NICs.   P.S.-Thank you for your response, i would have posted earlier but Dell fails to send the notification that there is a reply. another reason to go with a different computer manufacturer. THANKS Dell ! Message Edited by tekno_guru on 06-29-200610:30 AM

ItsJustAGuess · Answer

Did you see the trouble shooting section of the user manual that comes with the utility, it has a few things listed about certificates. I listed one of them below..

I am unable to connect to a network that uses a certificate.

The certificate may be invalid. To obtain a new certificate, see Obtaining Certificates.
If the network uses a TPM certificate, TPM must be enabled for you to connect. Refer to the TPM documentation that came with your computer for information about enabling TPM.
The purpose of the Logon or identity box on the Client Identity tab in Wireless Network Connection Settings (see Creating Network Connection Profiles) is to override the default behavior when users opt to use their user name and password to log on. This capability can be important with tunneling protocols such as TTLS and PEAP. Some AAA servers can be configured to require that the outer tunnel have a different identity than that of the inner tunnel. If this is the case, users must supply the information in the Logon or identity box. For TLS profiles that use machine certificates, Microsoft Internet Authentication Service (IAS) requires the client identity to be changed to the following:

tekno_guru · Answer

After many failed attempts with Dell technical support i finally figured out the problem by myself. it was the first option in the driver for 802.11h. after it was disabled everything was fine. we then upgraded our access point options and turned the option back on and has worked since.

Networking, Internet, & Bluetooth

802.1x or Aegis protocol

Was this post helpful?