Windows Explorer dead-locks when querying volume information with WNetGetConnection

[AliveDevil]

Hi,

I'm currently in the process of troubleshooting an application freeze, and a third-party application using Dokan results in our application freezing.

The third-party application includes a FUSE drive in the Local-drives section, and we are using WNetGetConnection to check whether a drive letter is a network drive letter.
This however results in NpGetConnection to return Win32 Error 6ba

RPC_S_SERVER_UNAVAILABLE
1722 (0x6BA)
The RPC server is unavailable.

and MprGetConnection looping forever.

Faulty stack trace:

rpcrt4.dll!RpcpRaiseException()
rpcrt4.dll!RpcRaiseException()
rpcrt4.dll!NdrpClientCall3()
rpcrt4.dll!NdrClientCall3()
davclnt.dll!DavWorkstationStarted()
davclnt.dll!NPGetConnection()
mpr.dll!MprGetConnection(unsigned short const *,unsigned short *,unsigned long *,unsigned long *)
mpr.dll!WNetGetConnectionW()

With MprGetConnection looping forever, WNetGetConnection never returns until the drive is disconnected.

Is this an oversight in the third-party application, or can be alleviated in Dokany?
I'm aware that the third-party application uses version 2.0.3 of Dokany, before I try to reproduce this with current 2.3 dokan-mirror, is there anything known?

[Liryna]

Hi @AliveDevil ,

I am not sure how this can happen but I can say that testing a new version might be worth it to know the current state. The network provider code had a change which might not help here but is worth pointing out
#1284