Windows 10: My two old NAS smb1 constantly asks password after upgrade to WIN10 20H2

Hi to all,
i'm struggling with two old Buffalo LS-WXL in my office network. At April upgraded from Win7 to Win10 and can't store password , even if stored in credential manager. It works when start WIndows... and works for some minutes.. but suddenly ask for password.
I tried every possible tips found in web but not solved.
yesterday.. finally formatted and reinstalled last Windows 10 Pro 20H2 19042.804 my PC retailer say me that this update fixed this problem. Enabled SMB1 in Control Panel.. but problem is still present!
I can power on PC and enter NAS folder.. without password already stored.. but after some minutes of inactivity or hours again ask me for password. Some for both my LS-WXL Nas

Now added in credential manager a second account so i have one with NASNAME/PASSWORD and other with IPNUMBER/PASSWORD but not solved.

Please... help me. i'm desperate! Can't work in this mode!


PS: Old PC with Windows7, in same network, have NO PROBLEM with this two NAS.





:)

 

need SMB1 protocol and drivers for obsolete NAS

I have an old Western Digital World Book Network Attached Storage that uses SMB1 protocol. I have new Windows 10 Home computer that is post SMB1. Is there a simple way for me to add the SMB1 drivers so I can use my NAS. The Knowledge Base articles seem
confusing and convoluted.

 

Windows 10 ADK no support for smb1?

Hello, everybody. Paragon Diskmanager uses Window PE for its rescue disk. I have an old but good NAS-Server (iomega) installed, which apparently uses smb1. There is no way to connect to the NAS Server with WIN10-PE. Does someone know whether there is a
way to configure Windows 10 ADK for smb1? Thank you!

 

Unable to do system image save to NAS

I have asked this question in several forums but am not getting any response.

Recently upgraded one of my boxes to win10 on a workgroup environment. I have a seagate central NAS that I saved system images to and it has been working fine until I upgraded to win 10. What I have discovered is that the win10 version of the backup engine
(wbengine.exe) is working differently than the win 7 version. The win 7 version does not do any byte range locking so I can save successfully to NAS and to win10. When win10 is the client I can save successfully to Win7 with SMB1 or SMB2.1 Protocol and the
win 7 box responds properly to the lock requests. The NAS only supports SMB1 which win10 understands but it still requests locks which apparently confuses the NAS and the process aborts. So the locking is the problem and it is new to win10 wbengine. As a result
my NAS is now an expensive paper weight. Is there anyway to prevent win10 from sending lock requests?