Windows 10: Mapped Network Drive Isn't Available After Restart

How do I get the NAS Network Drive Created to reappear and require password entry next time I startup My Surface Pro 3 with Windows 10 version 1903?


I Mapped the NAS as a network drive with "Reconnect at sign-in" unchecked and "Connect using different credentials" checked. Then I entered credentials and created the drive. Here's a screenshot: https://1drv.ms/u/s!Ag9MrIdQMNIZoAPFrFX-qFVHGtd7?e=mepIS9


Next time I restart or start up the Surface Pro 3 the mapped drive does not appear. Here's a screenshot: https://1drv.ms/u/s!Ag9MrIdQMNIZoAQUxytMe1vyRB5s?e=OXhvtR


I have the same NAS mapped as a network drive on my PC before the version 1903 upgrade. It still works fine and is presented in File Explorer differently. Here's a screenshot: https://1drv.ms/u/s!Ag9MrIdQMNIZoAXnD_Git2_SYgOB?e=AQzVaj Notice that the network drive is disconnected because I haven't connected it using "different credentials."


I'm working on a home network without a domain. I originally had a workgroup but that's gone now that both computers are running Creators Update version: 1903. I haven't setup anything else to replace the workgroup.


Thanks.

Bill

:)

 

Map Network Drive in Windows 10


thank you for doing this tutorial.
An issue that plagued us in earlier Windows still remains in 10 and I do not yet understand some of the solutions given in the superuser forum thread pasted below.
The issue is simple:
- "drives" are mapped correctly, and work well WHEN they are manually accessed.
- Windows 10 automatically disconnects the resource when not used.
- Waking or restarting/booting the mapped drive remains disconnected: no request has been made, therefore the shared resource is offline [Red X]

the solution would be something to cause the mapping to be ready/available/connected at all times except for sleep [I guess... that would be permissible to most] or 'off'. In the thread below a couple of people propose 'solutions' [despite a couple of boneheaded ideas] but these either over-reach or are limited only to solving the 'connect at startup' need.

Not solving this defeats automated routine backups [pushed from the client station in question, in this example], which can be deadly. users should not be expected to have great memories or great technical skills

what is the RIGHT step to take to make the Mapped resource "always available", with exceptions noted above?

On login, how do I get Windows to mount/connect a mapped network drive automatically? - Super User

 

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

 

Printer isn´t working after latest update.

After the latest update from Windows, my Canon Pixma ip6600 printer isnt working. In Device Manager it shows up as working properly but when I go to print it isn´t listed as an option in any programs. Troubleshoot suggests it´s a USB 2 printer on a USB
3 port and that that´s the problem but that cant be since it worked fine before the update. I´ve tried to uninstall and plug it back in but that doesn´t work either.