Windows 10: After updating to WIndows 10 v2004, cannot map network drives

Hi,


How can I solve this problem after updating to windows 10 v2004 from v1909, i cannot map network drives/shares anymore, everything was working fine before the update, the shares are located in a windows server v1809.


When i try to connect the shares on map a network drive either using \\server_name\share_name or \\IP_of_the_Server\share_name using the correct domain\username and password i get a error code 0x80070043, the windows server is a domain controller and the windows 10 is a laptop that is not joined in the domain.


Thanks.

:)

 

Trouble Mapping Network Drive

I have a WD NAS drive connected to my router and have mapped it on three of my computers. I just setup another laptop with Windows 10 and have updated it to 1809 and when I tired Mapping a network drive nothing is displayed in the browse window except the
computer I am currently using. The drive is shown under network locations in File Explorer but not when you select map network drive and browse. I right clicked on the drive and selected properties and noted the IP address and went back into Map network drive
but instead of selecting browse I entered the IP address but it still does not map the drive. The strange part is if I go to any of the computers that already has the network drive mapped and select Map network drive and select browse none of those computers
show the drive either but you can select the mapped drive in the drive list in file explorer and it works just fine.

I have read several articles both here and elsewhere and tried the suggestions but nothing works. Network discovery is turned on as is file sharing and also checked if all three boxes under SMB file sharing support in Windows features were also checked and
they are. I have mapped several computers to several different drives over the years and anytime the drive was not listed it was always easy to go into Network Sharing Centre and find the problem but everything seems to be as it should so would appreciate
if someone can suggest something I may have overlooked.

Thank you

 

Create a shortcut to map a network drive windows 10

Hi,

Thank you for posting your query on Microsoft Community.

As per the issue description you are willing to create a shortcut to map a network drive. I would suggest you to refer the steps provided in the articles mentioned below and see if it helps.

Create a shortcut to (map) a network drive

Create a shortcut to (map) a network drive


Note: These articles are for Windows 7/8/8.1 but steps holds good for Windows 10 too.

Hope the information provided is helpful. Do let us know if you have any more concern related to Windows. We will be more than happy to assist you.



Regards,

 

Mapped network drives don't work in Windows 10 version 1809

Yep. *Wink

Mapped drives issue now resolved. See "Current Status" table on first post for more details.

*Arrow Windows 10 October 2018 Update version 1809 Now Re-Released - Windows 10 Forums

[table][tr][td]Date[/td] [td]Current Status[/td] [td]Affected Platforms[/td] [td]Details[/td] [/tr] [tr][td]December 5, 2018 3:00 PM PT[/td] [td]Resolved[/td] [td]

• Windows 10, version 1809
• Windows Server 2019
• Windows Server, version 1809

[/td] [td]Mapped drives may fail to reconnect after starting and logging onto a Windows device. Symptoms include:

• In File Explorer, a red "X" appears on the mapped network drives.
• Mapped network drives show as "Unavailable" when you run the net usecommand from a command prompt.
• In the notification area, a notification displays, "Could not reconnect all network drives."

Resolved: KB4469342 addresses the issue that may cause mapped drives to fail to reconnect after starting and logging onto a Windows device. This supersedes KB4471218 for workaround scripts to automatically reconnect a mapped network drive when you log on to the device.[/td] [/tr] [/table]