SecureW2 F.A.Q.

This applies to the SecureW2 EAP Suite 1.0.0, for older version see the following: http://www.securew2.org/wiki/FrequentlyAskedQuestions33x

1. I cannot connect and I am using the DEFAULT profile.

The DEFAULT profile does not allow you to connect to a your server without changing the configuration.

2. I cannot connect using my Windows Mobile device.

The current releases of smartphones very often don't have the correct Windows Mobile versions running to allow you to use SecureW2 succesfully.

The following devices have been tested with success:

NOTE: there are problems with device with WPA/WPA2 connectivity, please see for http://www.securew2.org/forum/viewtopic.php?t=661 more info

NOTE: Section 3 of this FAQ applies to all Windows CE Devices. Windows CE will not work with the current DEFAULT anonymous options

3. I cannot connect using the new 3.2.0 release, but previous versions work fine.

The new version of SecureW2 uses a different approach to the outer identity (Support for username privacy as specified in RFC 4282). Some RADIUS servers cannot handle this. To fix this problem use one of the two configurations:

(PREFERED) configuration 1:

(NOT PREFERED) configuration 2:

4. How do I enable the SecureW2 tracing functionality?

The SecureW2 tracing functionality is available for the following features:

To enable these trace features you need to make sure any of the following entries to are set to "1"

To increase the amount of logging, you can set the LOG level, for more information see the AdminGuide (Section 1: FileTracingMask)

The trace files can be found in the following folder:

%windir%\tracing (c:\WINDOWS\tracing).

SecureWiki: FrequentlyAskedQuestions (last edited 2009-09-03 07:45:35 by TomRixom)