[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1121
  • Last Modified:

802.1x wierd security (btw Huawei S3900 switch, MS IAS 2006 (RADIUS) and Windows 2k3 AD) doesn't work

Hi,

We use HuaWei equipment in our network: S8500 for our core routers, S3900 for the edge switches.
We tried to implement wired 802.1x security in schools network via the S3900 edge switches, and followed the instructions from HuaWei documents, and it doesnt work.

Please see the following testing results:

1.)Enable CHAP only on RADIUS and on S3900, it doesnt work, please see the attached debug file ( also I cannot see any event regarding my logon (mbus\j.wan) via Event Viewer on RADIUS);
2.)Enable MS-CHAPv2 on RADIUS and enable EAP on Switch, it doesnt work, please see the attached debug file ( but I can see some events regarding my logon (mbus\j.wan) via Event Viewer on RADIUS, it said:----Access request for user MBUS\j.wan was discarded, Reason-Code = 23 and Unexpected error. Possible error in server or client).

We actually have another part of 802.1x in our network--- network points in public areas, which are working well (via a login portal from an Aruba controller), please see the following diagram:

Client machine---------> S3900 switch -----------> Aruba controller (Use CHAP)  ------------> IAS (RADIUS)-------------->Windows AD----------> a successful authentication.
                                                                                                   
I would like to share some my experience with you, I had a similar issue with ChiliSpots (an open source software for HOT SPOT ---wireless and RADIUS authentication) three years ago, I successfully rectified the issue via CHAP whilst whole ChiliSpots community reckoned there was no way to make  ChilliSpots&RADIUS&Windows AD  work as their different ways of authentication.  

I think there might be an issue with S3900 regarding authentication method with Windows Active Directory via IAS (RADIUS), the switch S3900 really should use CHAP to initiate an authentication request to Windows AD via IAS (RADIUS) as CHAP would be a common language between S3900, RADIUS and Windows AD regarding authentication process.

Please also see two attached debug files for above two scenarios.

If someone out there experienced similar issues and know how to fix them, please help us, any information and help would be much appreciated.

Many thanks in advance.

Regards

John Wan

debugging-8021x-with-only-CHAP-e.txt
debugging-8021x-with-only-MS-CHA.txt
0
mbsadmin1
Asked:
mbsadmin1
1 Solution
 
Rich RumbleSecurity SamuraiCommented:
There is quite a bit of planning and testing you need to do to enable 802.1x on a wired lan, the wifi networks have it all rolled up into a nice neat packages so it is much easier on wifi than wired. Are you going to use certificates or active directory as the authentication mechanism? Have considered trying a solution like PacketFence, FreeNac or safe access lite from still secure. These are NAC solutions that don't require 802.1x, but can use it as well.
Also for 802.1x to work you have to have the supplicant installed/enabled. With XP I think it's enabled by default on wireless nic's but not always on wired nic's, and 802.1x depends on the "Wired AutoConfig" service to be started this is especially true for vista and 2008.. XP SP3 moves the service to wired autoconfig, and it's set to manual.
XP SP2 you had to have the Wireless Zero Configuration service started...
http://technet.microsoft.com/en-us/magazine/cc194418.aspx
http://support.microsoft.com/kb/953650
-rich
0
 
mbsadmin1Author Commented:
Hi Rich,

Thanks for your info, we are going to upgrade firmware soon, and will let you know the outcomes.

Cheers

John
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now