I ron s hield w hite p aper

W

HITE 

APER

ORT 

UTHENTICATION 

W

ITH 

ICROSOFT

S 

A

D

IRECTORY

If a non-802.1X client is connected to an 802.1X protected port, the Client will not recognize the EAPOL polling 

802.1X EAP-MD5 enabled client is connected to a non-802.1X port, it will attempt to send an EAP start frame to 

the Foundry device.  When the device doesn’t respond to the EAP packet, the Client considers the port to be 

authorized and starts sending normal traffic. 

By default, Foundry devices place all ports in the authorized state, allowing full network access.  When 802.1 Port 

prevent full network access.  Foundry devices support the EAP-MD5 standard between the client and itself. 

 

NOTE: For more information on Foundry’s implementation of 802.1X, please refer to the following resources: 

http://www.foundrynet.com/solutions/appNotes/PDFs/802.1XWhite_Paper.pdf