Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 47112 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WLAN Radius (NPS) authentication fails (since upgrade to UTM 9)

fundinfo
Hi,

since the upgrade to UTM 9 (9.004-34) (HA Mode) we are experincing some problems with our WLAN authentication. 
There is a RADIUS server set up (Windows Server 2008R2, NPS Server, configured as described in the Sophos KB), which worked fine with our devices running V8.***. Since the upgrade to UTM none of the clients is able to connect to the wireless network using WPA2 Enterprise (WPA2 PSK works fine). Nothing was changed on the RADIUS server side and the configuration/shared key, etc was double checked. There are no errors in the NPS log, but the Sophos wireless log shows the authentication process.
 
The error showing up is the following:
802.1X: authentication failed - EAP type: 0 ((null))
802.1X: Supplicant used different EAP type: 1 (Identity)

The part of the logfile showing the error message is attached.


Any ideas?

Thanks.


This thread was automatically locked due to age.
Parents
  • 0
    That should work.  Now, I'm thinking we have to suspect that the switch isn't sending the response back to the AP 50 correctly.  What if you move the AP to a different switch port?  If that doesn't work, it's probably time to re-flash the AP 50.  Any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    That should work.  Now, I'm thinking we have to suspect that the switch isn't sending the response back to the AP 50 correctly.  What if you move the AP to a different switch port?  If that doesn't work, it's probably time to re-flash the AP 50.  Any luck?

    Cheers - Bob


    I've tried a different switch port and still no luck, I also have a Cisco Aironet 1140 that I was using, with the same setup, it works fine when I plug it in, how do I go about reflashing the AP 50?
Reply
  • 0 in reply to BAlfson
    That should work.  Now, I'm thinking we have to suspect that the switch isn't sending the response back to the AP 50 correctly.  What if you move the AP to a different switch port?  If that doesn't work, it's probably time to re-flash the AP 50.  Any luck?

    Cheers - Bob


    I've tried a different switch port and still no luck, I also have a Cisco Aironet 1140 that I was using, with the same setup, it works fine when I plug it in, how do I go about reflashing the AP 50?
Children
No Data
Unfiltered HTML