DisplayLink Forum - View Single Post - Network Connectivity issues after connecting to large number of Docks

wdeguara · 06-30-2016, 06:58 AM

Hello.

Our Support teams have detected a bug with the DisplayLink driver that is likely to impact enterprise customers with a large hotdesk environment.

In such an environment, as users visit different desks over a period of time, and thus connect to various Displaylink docks, the following registry key grows:

HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E 972-E325-11CE-BFC1-08002BE10318}

Once the size of this registry key reaches 64kb in size the Windows machine will start to experience problematic network connectivity (eg. the user will be unable to connect to network shares and mapped drives). In our experience, symptoms start appearing when the user caches the configuration information of approx. 140 Displaylink docks on their laptop). The only way to resolve the issue seems to be to manually delete older Displaylink entries from the above registry key.

Hopefully this is something that the folks at Displaylink can resolve in a future release.

06-30-2016, 06:58 AM	#1
wdeguara Junior Member Join Date: Jun 2016 Posts: 9	Network Connectivity issues after connecting to large number of Docks Hello. Our Support teams have detected a bug with the DisplayLink driver that is likely to impact enterprise customers with a large hotdesk environment. In such an environment, as users visit different desks over a period of time, and thus connect to various Displaylink docks, the following registry key grows: HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E 972-E325-11CE-BFC1-08002BE10318} Once the size of this registry key reaches 64kb in size the Windows machine will start to experience problematic network connectivity (eg. the user will be unable to connect to network shares and mapped drives). In our experience, symptoms start appearing when the user caches the configuration information of approx. 140 Displaylink docks on their laptop). The only way to resolve the issue seems to be to manually delete older Displaylink entries from the above registry key. Hopefully this is something that the folks at Displaylink can resolve in a future release.