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.

Hi,

Can you try the latest USB 3.0 Host Controller Driver from here?
https://downloadcenter.intel.com/Det...&DwnldID=22824

Thanks,
James

Attached with the latest Host Controller driver installed - still experiencing same issues

Hi,

OK thanks, I've raised the internally for investigation.

Thanks,
James

Is there any ETA on it?

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

Hi Wim,

My office has just installed a whole bunch (~ 100 for hotdesking) of Targus USB3 docks (ACP71) and we're having a similar problem with 802.1x authentication.

When the new network adaptor is created by Windows for the dock's ethernet (new MAC address) port, how does Windows know what the default authentication settings are? Eg, Does it simply copy the built-in adaptors' properties or create new settings (like which certificate can be used to authenticate) from scratch?

The user experience is quite poor in that manual intervention is required to get staff online. It should be simple plug and plug, but many users are deciding to use their laptop's built in ethernet adaptor as that's already configured correctly for 802.1x

Will

The settings will probably not be copied across as each network connection will have its own settings.

However you can set these remotely, as they are just set in the Windows registry. I'm not that familiar with setting up 802.1x authentication (as I'm not an IT manager) but we have details on how our Ethernet settings can be set remotely and it is probably similar of 802.1x. Details on how to set up the Ethernet settings remotely is covered in section 5.7 of the User Guide:

http://downloads.displaylink.com/man...rManual7.6.pdf

Wim

Thanks for the quick reply, Wim.
Unfortunately remote config won't work as the computer can't get on the network without manual intervention in the first place.
So I need to see if the settings for a newly created network adapter can be copied from somewhere or set as a specific default..

Any other ideas?

Any news on this one.
 

Did anyone get a fix for this. Hi we have recently deployed hundreds of USB 3,0 docking stations in an 802.1x environment and are getting reports of people being placed in the Guest VLAN when they dock fist thing in the morning (failed auth). A wifi enable and disable seems to sort the wired authentication out. This does not happen all the time.

802.1x issues with display link and Lenovo usb
 

Hi

We are having the same problems when using these Lenovo port replicators. I can see in the wireshark that the port comes up but the 802.1x fails as we have configured it to MAB after 3 failed attempts (15 sec). Is there any way to speed up the driver load time from the time the user boots up the machine. It looks like the windows supplicant is initialized but since the Displaylink driver sits between the 2 layers there's quite a long delay for the EAPOL packets to start being sent to the authenticator.

Please let me know if there is a fix for this.

Thanks.

MC

Hi

The behaviour of the Ethernet driver with VLAN configuration was updated in v7.7 M4 to fix problems like this.

Previously VLANs were disabled and the VLAN ID was set to be 0. If VLANs were enabled the packets would have been priority tagged (VLAN set to zero). This was quite legal but different behaviour to other Ethernet adapters.

This Intel behaviour is to have Priority and VLAN enabled, and the VLAN field set to zero, but still sent untagged traffic. When we changed our driver to have the same behaviour in 7.7 M4, it fixed these problems with 802.1x failures, as they could probably now enable VLANs and set the VLAN field in the same way is they did on an Intel adapter.

Are you still seeing problems with 7.7 M4?

Wim

Similar issue
 

Hello There,
We have a similar issue with our corporate deployment of MAC based authentication system and DisplayLink network cards on Toshiba Dynadock model.

We've been trying to follow instructions from this support KB to pass-through laptop's MAC to dhcp but the settings do not stick, it reverts back to displaylink MAC when we move to different Dock.

Laptop's LAN and Wireless MAC addresses are registered but Dock's not. we need to get it to ALWAYS pass-through laptops mac no matter which Dynadock dock its connected to.

Here are some details from testing we carried out using one laptop on 4 docks.

Laptop A - Dock A ,
Tried changing MAC address through GUI under network card, this works. DHCP server sees lease against LAN card's MAC.

Dock B

• Changed the docking station , Laptop changed the network card from #2 to #3 and wiped MAC override settings.
• The settings under reg key HKEY_LOCAL_MACHINE\System\CurrentControlSet\servic es\dlcdcncm\Parameters\* are still the same but they do not show Laptops MAC when tested under the network card > advance > mac or ipconfig /all
• Under reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E972-E325-11CE-BFC1-08002bE10318} it now has new numeric key 0017
  
• We changed the settings through GUI under NIC and it works.
  
• Moved laptop back to Dock A and it still remembers settings but under 0016 driver key.

Dock C

• Changed the docking station to Dock C, it now has another driver key 0018 and no MAC override under NIC card anymore.
  
• Updated to Displaylink driver 8.3 from 31st Aug and rebooted.
• Changed NIC settings once more under NIC > advance tab , moved back to Dock B and it remembers settings Albeit under 0017 driver key.

Dock D,

Changed the dock again, settings gone away again. Driver key showing 0014


We tried to find DisplayLink support / customer service number but no joy so posting here on Forum. Quick reply will be much appreciated.

adding snippets

Eta ?
 

Hi,
Is there an ETA on this ?

We've tried all possible options mentioned on web page but can not get it stick to one "driver key" or make it override mac for every driver key.

A quick reply will be much appreciated.

Hi

Yes, this is possible, but you need to set the MAC address in a different place, rather than per adapter, otherwise it will need to be set for every new dock you connect to.

The information on how to do this is on or support site. See the section 8.1 MAC address configuration options.

Thanks

Wim

Hi Wim,
Thanks for getting back, we've been trying the same web page but it has not helped.

There are basically 2 ways mentioned on the web page to enable MAC pass-through,

Opion 1)
GUI and registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\XXXX Both essentially do the same thing but this setting reverts to default every time a new Dock is plugged.

Remote script push is not an option here as the laptop will keep creating new Driver keys for new docks and script is only one off.

Option 2)
Manual update of Registry key or Supplied script HKEY_LOCAL_MACHINE\System\CurrentControlSet\servic es\dlcdcncm\Parameters\

This option does nothing, we've tried on two laptops with latest Displaylink 8.3 driver and latest USB host driver with several docking stations and it made no difference.
we also updated registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\servic es\dlcdcncm_x64\Parameters\ but it did not help.


There is no displaylink customer service so We're trying to engage docking station vendor to get some support but it has not helped so far, issue is still open.

Thanks for your assistance here.

Waqas

Hi

You want to use Option 2 and add the entry MacAddressOverride under HKEY_LOCAL_MACHINE\System\CurrentControlSet\servic es\dlcdcncm\Parameters\

I've just tested this on the latest Ethernet driver and it works fine. I used the MAC address you were testing with (EC21E5660A20). Note that this only gets read by the Ethernet driver when the driver starts, so you will need to unplug and replug the dock to get it to use the registry MAC address after you've set it.

Wim

Hi Wim,
Thanks for testing but unfortunately it still does not work for us.

We've even tried switching USB ports on laptops and power cycling the dock but no joy.

Attaching snippet of our latest test. Is there anything related to hardware /reg key that we might be missing ?

Thanks ,
Waqqas

I've exported the registry and pasted the .reg file contents below. The characters in the MAC address are all 0-F? A zero is not actually a capital "O"?

How are you checking the MAC address? I'm using "ipconfig /all".

Wim

Hi,
Yes, the mac is all 0-F hex characters and we're checking by by ipconfig and getmac both.