- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- 802.1X authentification with dynamic VLANs breaks ...
-
- Forums
-
Blogs
- Hybrid Cloud
- Edge
- Data & AI
- Working in Tech
- AI Insights
- Alliances
- Around the Storage Block
- Behind the scenes at Labs
- Careers in Tech
- HPE Storage Tech Insiders
- Inspiring Progress
- IoT at the Edge
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Russia
- HPE Blog, UK & Ireland
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-09-2012 01:33 AM
07-09-2012 01:33 AM
802.1X authentification with dynamic VLANs breaks Windows 7 DHCP
Hello everybody,
we use the 5400 series and have 802.1X authentification enabled. We use FreeRADIUS 2.10 with PEAP and MsCHAPv2. The VLAN is dynamically assigned by the RADIUS Access-Accept reply depending on the given user.
Most of the time this works fine, but sometimes Windows 7 clients complain about "limited connectivity". The reason is that Windows 7 does not correctly obtain an IP through DHCP, but chooses an APIPA adress.
A wireshark trace reveals that Windows 7 sends the DHCP discover before the authentication completes. Most of the time the authentication process is successful and VLAN assignment is done before the third DHCP discover times out. But in rare occasions, Windows 7 sends all three DHCP discover messages / request messages, before the VLAN assignment is established and then tries an APIPA address.
Of course, this is mainly a Windows 7 bug, because Windows 7 should first authenticate and then try to obtain an IP address, not the other way around. But I did not find anything in the web on that topic, but a sole CISCO help board entry, that essentially states "yes, we know this issue".
- Tags:
- VLAN
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP