Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[skeleton]

I've looked through the history on here but didn't find any reference to the problem.  Had my DNS-343 for a couple months now, on my network router and using
Windows 10 patched to date.  Installed four 2TB drives.  Problem is that Windows 10 Explorer reports drives 'not available' on startup.  Found a feature in Win 10 to wait for network devices on bootup and set that option. I always shut down Win 10 machine at night but leave DNS-343 powered.    On boot of the Win 10 machine, mapped drives are most often showing red X and reported as 'not available.  I've had to resort to batch file to 'DISCONNECT' all mapped drives to erase the mapping and then remap drives with 'NET USE each one with the 'persistent:yes' option.  When Explorer shows the red X status, clicking the drive tries to connect but then reports not available.

I have 8 mapped drives, four on the DNS343 and four on a WDMyCloudEX4100.  WD drives map first S,T,U,V and then DNS343 drives should map W,X,Y,Z  I've used Windows versions for years and have never had problems mapping drives as long as the feature has been available and have mapped drives between Windows desktops and laptops for years with no problems. 

I also have another thing I can't figure out.  The display has been showing message 'Caution!  Disk is full!' message for days, but Windows Disk Properties show the following:

Vol 1          1.71tb free
Vol 2          1.78tb free
Vol 3          599mb free
Vol 4          1.61gb free

Nas has been rebooted but the message doesn't go away. 

[FurryNutz]

Is SMB v1 enabled in Windows 10?

[skeleton]

Yes, it is.