- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We encounter an issue with the WOL fonctionnality and 802.1X using computer based authentication.( ) Message # 4
When Computer is waking up from sleep, the Windows Native supplicant is sending the wrong user (normally it's the computer name). The supplicant is sending mac adress (Network Card is doing mab insteed of 802.1X) :
Dec 3 14:20:16: RADIUS: authenticator 4C B5 F0 2E 73 78 D1 C0 - 9B 01 23 6F 02 14 59 49
Dec 3 14:20:16: RADIUS: User-Name [1] 14 "3417ebxxxxxx"
Dec 3 14:20:16: RADIUS: User-Password [2] 18 *
When I completly disable WOL on the network card, authentication is working perfectly when waking up from sleep :
Dec 3 14:22:49: RADIUS: User-Name [1] 30 "host/MASS1.xxx.xxx.xxx"
Dec 3 14:22:49: RADIUS: Service-Type [6] 6 Framed [2]
Dec 3 14:22:49: RADIUS: Vendor, Cisco [26] 27
We need to let the WOL fonctionnality activated, does anyone have an idea ?
- Tags:
- NFL
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The WOL can be done by Intel ME interface of chipset, not OS driver, so you probably need to setup a right hostname in ME BIOS (Ctrl+P at time of Intel Management Engine screen during POST), default password admin. If system do not support Intel AMT (so no ME BIOS), try to completely disable ME in MB BIOS, if possible.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi JFFulcrum,
If i understand well, i need to :
-Disable WOL in the OS driver
-Enable WOL in ME interface
Right ? But if the disable ME in MB BIOS because the system does not support Intel AMT we will have the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you disable ME, NIC will not send WOL signals to it and will use other methods, like global SMBus signals, and ME will not interfere into boot (probably overriding driver setting by settings from own firmware).
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page