Ethernet problem with Windows 10 and Targus docking

[LuisNeves]

Hello.

I have been using for a few months a Targus USB 3 docking station with my notebook - a Toshiba Kira with Windows 8.1.

Everything running ok, video, ethernet, etc.

Last month I have made the upgrade to Windows 10 and since then I lost the ethernet. Already tried the updated software, unistall and clean, install again, always without success.

I enclose the log made with the utility tool. Any help is appreciated.

[JamesH]

Hi,

Can you try these steps?

1. Open Device Manager
2. Open Network adapters
3. Right click on Targus USB Ethernet
4. Select Update Driver Software
5. Select Browse My Computer For Driver Software
6. Browse to C:\Program Files\DisplayLink Core Software\
7. Select Include Subfolders
8. Select Next

Thanks,
James

[LuisNeves]

Hi,

Can you try these steps?

1. Open Device Manager
2. Open Network adapters
3. Right click on Targus USB Ethernet
4. Select Update Driver Software
5. Select Browse My Computer For Driver Software
6. Browse to C:\Program Files\DisplayLink Core Software\
7. Select Include Subfolders
8. Select Next

Thanks,
James

When I open the network adapters I found a "Displaylink network adapter NCM", is this right?

Doing these steps returns a message that the best controllers are already installed and up to date.

Thanks for your help.

[JamesH]

Hi,

It sounds like you may have already tried this but for completeness can you try the exact steps in this FAQ?

http://support.displaylink.com/knowledgebase/articles/678310-displaylink-ethernet-or-audio-drivers-are-not-load

Thanks,
James

[LuisNeves]

Hi,

It sounds like you may have already tried this but for completeness can you try the exact steps in this FAQ?

http://support.displaylink.com/knowledgebase/articles/678310-displaylink-ethernet-or-audio-drivers-are-not-load

Thanks,
James

I had already tried this steps, anyway I did again. The problem continues.

Then I noticed the referece to problems with Kaspersky and the need to update to version 2016. Indeed I use Kaspersky. I did the uninstall of version 2015, reboot, install version 2016 with windows defender off. Update of 2016 and reboot again. The problem continues.

I noticed one small difference. In the device manager, now the device is listed as "Targus Giga Ethernet", while before was described as "Displaylink network adapter".

Finally tried again the steps of your first post and again says that the drivers installed are up to date.

I run out of ideas...

[LuisNeves]

Problem solved...as usual I don´t know exactly what was the reason (my fault)...

Explaining.

Yesterday I bought an external usb/ethernet adapter. I have tested in another computer and worked perfectly, when attached to one USB port of my notebook again there was no network. This was in my opinion an indication that the problem was not related with the displaylink drivers but possibly with windows or other software component.

When I saw the reference to the update of Kaspersky to the 2016 version I realized that this was a very probable cause for the problem. So I got very disappointed when the update did not work.

After my last post I had one more idea: maybe the the problem could be Kaspersky itself. So I decided to unistall Kaspersky and try again without it.

I did the following sequence:

1 - Disconnect from docking
2 - Uninstall Kaspersky and reboot
3 - Unistall displaylink and reboot
4 - Use the cleaning app and reboot
5 - Stop Windows Defender
6 - Install again Displaylink and reboot
7 - Connect the docking station
8 - Confirm in device manager the presence of Targus ethernet and test updating from Displaylink folder (returns message that is already up to date).

Again no network. :confused:

It was at this stage that I realized that the ethernet cable was not connected to the docking since yesterday tests with the external adapter! :mad:

Well, I connected the cable to the docking and I got wired network imediatly. :D

After that I reinstalled Kaspersky 2016 and ethernet keeps working fine.

So, my conclusion is that the problem was likely caused by the Kaspersky issue described in the link provided by JamesH (http://forum.kaspersky.com/index.php?showtopic=328787):

Uff!