Tuesday, June 9, 2020

2004 Update breaks 802.1x DHCP IP address assignment

After the last major Windows 10 Pro update, our Ethernet connection doesn't work as before when obtaining a IPv4 address assignment from our Windows 2016 DHCP server. The issue affects all our pc from different vendors. When a domain user authenticates to start a new session, he doesn't receive the correct ip and gateway address, so he cannot have access to the network because the pc stays in a VLAN where that ip doesn't work. The problem needs to be fixed by disconnecting and reconnecting the ethernet cable, then it is stable for the time of the session. After a reboot or a logout, the problem starts again. We have this problem on all the pcs in the LAN after 2004 update.

We tried, with no success, to do the following:

- ethernet driver update (Intel);

- uninstall and reinstall ethernet interface;

- disable IPv6 from network properties;

- install a previous ethernet driver version (Intel);

- disable energy saving properties in ethernet interface;

- disable realtime antivirus functionalities;

- check correct operation at Radius and DHCP server level.

Any further idea about how to fix this issue?

Thank in advance for any help.



No comments:

Post a Comment