Windows 10: Windows 10 V21H2 Drive mapping fails periodically to local NAS on home network.

I have a home network with a PC running Windows 10 Pro V 21H2 64bit O/S and X64 Processor. I have a local NAS Drive Seagate Personal Cloud. The NAS drive is preset to a fixed IP address in both the NAS drive and router.Whilst running an initial backup, the drive mapping fails every so often. I can't pin down how long it takes. Sometimes it's after a few hours. Other times it's after 14 hours. This seems to only be a problem when the initial backup is running, which takes many hours. Doesn't happen on a daily backup, which takes just a few minutes.I need help to sort this out, as it's

:)

 

Connecting NAS - mapping of drives

Ok,

If you want, we can do a step by step troubleshooting of your current situation:

If you are able to ping your Machine and it responds.
Code:

Try to view if your NAS appears on the Network List:
Code:

If Your NAS appears on the list, try to view it:
Code:

The available shares will be listed there.

Then Try to List the content of one of the directories:
Code:

This should list the content of the directory,

If all this works Try to map a drive on one share:
Code:

Pls reply with the "response" of the first "encounter" of a non positive output.

This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.

 

All scans of mapped drive fail (full, quick, custom)

Hi! I'm having a problem with the Custom Scan operation in Windows Defender. I use this frequently on my local machine, but when I try to scan my NAS (mapped as "H") it fails taking anywhere from several seconds to 13-minutes but always showing 0 files scanned. The topology is all gigabit ethernet: Desktop > LAN > switch > LAN > NAS. My computer is part of a small workgroup, DHCP is handled by LAN-wired router, and the NAS is a Drobo. I'm running Windows 10 Pro x64 v1909 build 18363.778

I have tried the following:

• Tut 70530 Local Group Policy Editor | Include Mapped Drive on Full Scan -- no joy
• Tut 70530 Registry hack | Include Mapped Drive on Full Scan -- no joy
• Tut 152869 Registry hack | Scan Network Files -- no joy

It seems no matter what I do I can't get WD-AV to scan my mapped NAS or any part thereof. I did just see that the latest definitions broke WD, so maybe that's it. Both registry hacks above are still in place, I put the policy setting back to default.

Any suggestions?

Thanks,
7

 

Mapping network devices such as NAS drives.

Dear Support,

I am having a massive problem with finding NAS devices on my network so I map them as network drives.

I had not changed any network configurations, but now I do not see my NAS drives in the list under "Network", nor can I map my NAS drives.

My previous mappings are fine and work OK. However, even the drives that were previously mapped that work OK do not appear in the list for the options of mapping network drives now.

I am running Win 10 latest version on an Intel 7th gen CPU, wired Ethernet.

I have checked to see that all my firmware is up to date, including router, NAS, network driver. I have checked that sharing is on, and turned off firewalls, made my network type private. I have searched every forum and technical note, and tried every video
out there, but I am at the end of my tether with this problem.

The problem seemed to occur after updating Windows. Everything was working fine before, completely flawlessly.

I am basically now completely fed up with the situation, and my only option left is to move all my computers to Linux. The problem has basically cut off access to data I need to work and is costing me money and time. I basically just want to cry as there
is no solution anywhere that I find. The Windows update has broken my network.

If anyone has any answers, please let me know.

Thanks for your time in advance.

Kind regards, Ben.