Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 47103 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 looks like it made the connection.  What do you see in the DHCP Server log at 16:37:03?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    That looks like it made the connection.  What do you see in the DHCP Server log at 16:37:03?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    That looks like it made the connection.  What do you see in the DHCP Server log at 16:37:03?

    Cheers - Bob


    Bob, Thanks for the reply, I just restarted the UTM so I don't have the log from 16:37, but here is the current log as I am still having the same issue... on the client computer it says I am connected to the SSID but I am getting the 169 auto config IP address

    DHCP Log:
    2013:10:11-18:20:21 gateway dhcpd: DHCPINFORM from 172.16.7.85 via eth2.7
    2013:10:11-18:20:21 gateway dhcpd: DHCPACK to 172.16.7.85 (80:ee:73:2e:e7:05) via eth2.7
    2013:10:11-18:20:33 gateway dhcpd: DHCPDISCOVER from c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:20:33 gateway dhcpd: DHCPOFFER on 172.16.7.105 to c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:20:44 gateway dhcpd: DHCPINFORM from 172.16.7.252 via eth2.7
    2013:10:11-18:20:44 gateway dhcpd: DHCPACK to 172.16.7.252 (00:0c:29:4a:7a:f1) via eth2.7
    2013:10:11-18:20:52 gateway dhcpd: DHCPINFORM from 172.16.7.107 via eth2.7
    2013:10:11-18:20:52 gateway dhcpd: DHCPACK to 172.16.7.107 (58:b0:35:b1:c5:04) via eth2.7
    2013:10:11-18:21:03 gateway dhcpd: DHCPDISCOVER from c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:21:03 gateway dhcpd: DHCPOFFER on 172.16.7.105 to c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:21:09 gateway dhcpd: DHCPDISCOVER from c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:21:09 gateway dhcpd: DHCPOFFER on 172.16.7.105 to c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:21:17 gateway dhcpd: DHCPDISCOVER from c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
    2013:10:11-18:21:17 gateway dhcpd: DHCPOFFER on 172.16.7.105 to c8:bc:c8:f4:83:1c (basement-PC) via eth2.7
Unfiltered HTML