9/5/2023 0 Comments Mapped drives not showingSession 1 0:0x1add9 Window Manager\DWM-1 Negotiate:Interactive Session 1 0:0x1adf6 Window Manager\DWM-1 Negotiate:Interactive Session 1 0:0x161805 GARY\Gary NTLM:Interactive Session 1 0:0x161902 GARY\Gary NTLM:Interactive I would suggest exploring the Windows Object Namespace (using a tool of your choice ( would be one option)), especially the \Sessions\\DosDevices subtrees, looking for links to \Device\LanmanRedirector\ X: and perhaps correlating this information with the output of klist sessions.ĭirectory of: \Sessions\0\DosDevices\00000000-000003e4 The "linking" (or not) of connections between sessions does sound as though it might be playing a role, but you have already identified the key registry setting (EnableLinkedConnections). Was the error message in Windows File Explorer perhaps "Die Datei X:\ wurde nicht gefunden"? ![]() I guess that you are from a German speaking region and that the error message "Cannot access X:" is a translation while that translation might capture the essential nature of the problem, it would be useful to know the exact text (in German) so that one can accurately map the error text to an error code. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\SystemĪs described here in Solution 1 at this link mapped-network-drive-not-showing.html.ĭoes anyone have a similar problem or any tips on how to solve this? ![]() Somehow it does also not affect all Drives It seems that not all users are having this issue. The error can be resolved by restarting the explorer.exe process. When I enter the dive letter for example "X:" manual into the explorer the error "Cannot access X:" shows up. I can change to the drive using cd and can then list content but only in the cmd. ![]() When I open a CMD at the client having the problem and enter "net use" I see all drives connected. We map the dives via script at one and via GPO at the other. Only thing similar is that they both use a Windows Server 2016 as Data Server. One costumer is using Windows 10 Clients the other is using a Windows 2016 Terminal Server. I have the problem that at two of our costumers there is the problem that sometimes network drives do not show up in the Windows Explorer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |