Hello,
I am having a problem with getting a wireless laptop to stay connected when using two factor authentication. I am in the process of testing this before putting it in production. When I have the laptop using two factor authentication, the connection gets dropped after about 1 hour. I have to do a repair on the laptop wireless adapter to be able to reconnect to the wireless network again. I changed the configurations on my AP's (2 of them) to use WPA2 personal mixed and used a shared secret key, the laptop stays connected. I ran a constant ping for almost 24 hours and it never lost the connection.
I suspect it is a configuration setting on the IAS server but I don't know what I am missing.
My IAS settings are as follows:
The default ports are used
Radius Clients are set to the correct APs with the keys
I set full logging in the log file. (although I do not understand how to read the log file)
I used the wizard for the remote access policy. It is set to NAS port type matches "Wireless - others" OR "Wireless IEEE 802.11 AND windows groups matches Domain Computers and a group I made for wireless users. The account I am testing with is a member of that group. The settings in this profile for the access policy was left at the default settings except for the encryption (only 128 bit). Authentication is set to PEAP. I created a self signed certificate for this server and placed it in the trusted root certificate authority. I also installed that certificate to the laptop I am testing with.
For the connection request policies, I left the use windows authentication for all users as is.
I checked the event viewer system log on the IAS server and I see it gets granted access. When the connection gets dropped I do not see any other connection messages about being denied. The last entry of the connection shows it as successful.
I am using two Linksys WAP4400N access points. One is on channel 1 and the other is on channel 11. They are both using the same SSID to enable roaming.
If anyone has any suggestions, I would appreciate it.
Brian
I am having a problem with getting a wireless laptop to stay connected when using two factor authentication. I am in the process of testing this before putting it in production. When I have the laptop using two factor authentication, the connection gets dropped after about 1 hour. I have to do a repair on the laptop wireless adapter to be able to reconnect to the wireless network again. I changed the configurations on my AP's (2 of them) to use WPA2 personal mixed and used a shared secret key, the laptop stays connected. I ran a constant ping for almost 24 hours and it never lost the connection.
I suspect it is a configuration setting on the IAS server but I don't know what I am missing.
My IAS settings are as follows:
The default ports are used
Radius Clients are set to the correct APs with the keys
I set full logging in the log file. (although I do not understand how to read the log file)
I used the wizard for the remote access policy. It is set to NAS port type matches "Wireless - others" OR "Wireless IEEE 802.11 AND windows groups matches Domain Computers and a group I made for wireless users. The account I am testing with is a member of that group. The settings in this profile for the access policy was left at the default settings except for the encryption (only 128 bit). Authentication is set to PEAP. I created a self signed certificate for this server and placed it in the trusted root certificate authority. I also installed that certificate to the laptop I am testing with.
For the connection request policies, I left the use windows authentication for all users as is.
I checked the event viewer system log on the IAS server and I see it gets granted access. When the connection gets dropped I do not see any other connection messages about being denied. The last entry of the connection shows it as successful.
I am using two Linksys WAP4400N access points. One is on channel 1 and the other is on channel 11. They are both using the same SSID to enable roaming.
If anyone has any suggestions, I would appreciate it.
Brian