|
05-29-2014, 02:19 PM | #1 |
Junior Member
Join Date: May 2014
Posts: 3
|
Authentication issues on ethernet port
I'm running the 7.6 M0 DisplayLink drivers on the Lenovo USB 3.0 port replicator (Part number: 0A33970).
When attempting to connect via ethernet, I receive an authentication failed error. We are using 802.1x in an enterprise environment. When I re-enable wireless, the LAN will connect shortly thereafter without authentication issues and work as intended. The port is fine, and about half the time, the dock will successfully authenticate on it's own without issue. Logs are attached to the post. Any assistance would be greatly appreciated. |
05-29-2014, 03:02 PM | #2 |
Senior Member
Join Date: Jan 2012
Posts: 1,523
|
Hi,
Can you try the latest USB 3.0 Host Controller Driver from here? https://downloadcenter.intel.com/Det...&DwnldID=22824 Thanks, James |
05-29-2014, 04:33 PM | #3 |
Junior Member
Join Date: May 2014
Posts: 3
|
Attached with the latest Host Controller driver installed - still experiencing same issues
|
05-30-2014, 11:00 AM | #4 |
Senior Member
Join Date: Jan 2012
Posts: 1,523
|
Hi,
OK thanks, I've raised the internally for investigation. Thanks, James |
06-03-2014, 12:33 PM | #5 |
Junior Member
Join Date: May 2014
Posts: 3
|
Is there any ETA on it?
|
06-04-2014, 03:37 PM | #6 |
Senior Member
Join Date: Feb 2009
Posts: 1,561
|
These issues tend to be above the DisplayLink driver layer, as all we do is pass layer 2 packets. The problem tends to be due to the internal network expecting certain MAC address (the dock has its own MAC address that will not be in a corporate whitelist) or we have seen the network requiring a different MTU to allow it to work in the network.
In the logs, I can't see the Wireless Network Connection (it is disabled) to see what settings you have on this interface. I think it is best to check the network settings and any error settings on the 802.1x authentication server, as the problem is probably above our USB driver and something to do with the network security. You could try using wireshark to see the packets in a working and a failed case and see what the difference is. It could give a clue as to where the problem is in the system. Wim |
|
|