File and Printer Sharing for Microsoft Networks Failing
 

I am running into an issue that the File and Printer Sharing for Microsoft Networks fails when my DELL 5580 is connected to a DELL D6000 Docking Station over USB-C with the current DisplayLink drivers (8.5.3595.0).

This issue does not occur when connected over WiFi or via the Network Adapter in the Laptop.

I've updated all drivers to the latest version and also the systems Firmware (BIOS).

The problem is resolved (work-around) by toggling the File and Printer Sharing for Microsoft Networks binding on the Network Adapter after every dock action or reboot.
I’ve found other people reporting this issue also, with the above work-around only and no actual solution.

https://social.technet.microsoft.com...tpronetworking

It is unclear what the root cause is and if the root cause is inside the DisplayLink driver, however it only happens in combination with the DisplayLink driver. Any support for diagnosing this?

Is there anyone who can test if this issue also exists at his/her system by connecting to \\computername\admin$

Hello Floris,

Interesting link. Neither of the products mentioned there use DisplayLink Ethernet.
Therefore this is unlikely to be a driver or device issue, but rather an OS one.

I'll ask Microsoft during my call next week how best to progress that.
Do you have a reliable reproduction? We are likely to be needing to gather/create logs of some sorts. I don't yet know which!

Kind regards,
Alban

You are right, I overlooked the Driver details for the Ethernet Adapter. It is a DELL driver.
Well looking again it does mention DisplayLink Corp. as provider.

https://www.displaylink.org/forum/at...1&d=1535955131

Reproducing is easy, every time the dock is plugged in the issue occurs. If you could get some movement at Microsoft that would be great, not much traction on the issue so far.

I’m more than willing to help gather logs for debugging purposes.

Afternoon,

I know (hopefully!) that the Dell D6000 uses DisplayLink Ethernet, I even have one on my desk.

The poster on the thread you linked on the Microsoft community are about Dell WD15, Dell DA200 and DA300. None of these products use DisplayLink technology and therefore not our driver.

I will ask what we need to get the bug rolling, it's good you have a reliable reproduction.

Kind regards,
Alban

DL Ref: 28632 - File and printer sharing for Microsoft networks failing on USB Ethernet adapters

Hello Floris,

Here are traces that might be helpful to find the root-cause the problem. Could you attach these ETLs to the thread or, if too big, send a link to the cloud storage of your choice so this can be downloaded and handed over to Microsoft? The email address is technical_enquiries@displaylink.com.
Please mention context and reference 28632 so the person picking up your ticket knows what to do with it straight away as I'm on holidays for a few days.

Turn on tracing on the “server”
- Open Admin command prompt and enter this:
Netsh trace start filesharing tracefile=c:\filesharing.etl

Turn on tracing on the “client”
- Open Admin command prompt and enter this:
Netsh trace start netconnection tracefile=c:\netconnection.etl
- Repro issue: Try connecting to the server
- Stop tracing:
Netsh trace stop

- Stop tracing on Server:
Netsh trace stop

Kind regards,
Alban

I'm really interested in this topic, since we have he same problem in our company.
The only difference is that we can not reproduce it reliable.

We are using an universal docking station from Targus (https://www.targus.com/uk/universal-...power-acp77euz), which are utilizing a DisplayLink ethernet chip, for our Dell and HP laptops.

Once the error occurs, it can be reliable linked to the docking station.
Unplugging ethernet from the docking station and connecting it directly to the laptop eliminates the problem with available shares. Reconnecting to the docking station results in shares not found.
This can be repeated over and over again with the same results.

Unfortunately, since this problem is rather infrequent (and regarding to company compliances), i can not provide (publicly) network traces to help further investigating into this problem.

Kind regards,
Stephan

Hello Stephan,

I've received traces from Floris through a ticket. We used them to create a bug report to Microsoft.
We only managed to reproduce the opposite in our labs. Also, as the issue is reported on other technologies, it seems Microsoft is the best placed to advise us on the next step.

Kind regards,
Alban

Hello Stephan and Floris,

We have received the feedback to check if this could be caused by SMBv1 being unavailable.
http://aka.ms/smb1rs3
http://aka.ms/stopusingsmb1

I understand that you have a different behaviour on Wi-Fi than USB, so I am not sure of the relevance. Would you be able to check nonetheless as we don't have internal reproduction of this issue?

Kind regards,
Alban

I am still running Windows 10 version 1703, so that can't be the issue. Also I am reproducing the issue by just doing a loopback on my system by going to \\hostname\admin$ or \\hostname\c$.

SMBv1 is installed as a Windows Feature. However, if I query it's status with PowerShell I get the following output:

Hello.

Sorry forgot the late reply.

I found a workstation, which had this problem at the time, and had a look on these settings.
I did the same test like Floris did, but for me both protocols shown up as True.

So i think this problem can be excluded on my side.

Kind regards,
Stephan