Windows 10: Win10/NAS (Freenas Box) Not Allowing Interaction

History: Before the Win10 Creators Update (or maybe just before it last summer, my Win10Pro PC was freely drag'n'dropping between my Freenas File Server as it should. I have read hundreds of posts about SMBv1 and other similar "solutions" and have attempted numerous "fixes" to no avail. I KNOW there are other people experiencing the same problem, so I'm trying to focus on this thread to possibly solve my problem and also help others.

A solution I did run across is the use of FileZilla FTP which SUCCESSFULLY allows me to communicate with Freenas and transfer files here on my local network from PC to FN and back again. I've tinkered with FN permissions, SMB, Windows/UNIX file types, etc. but direct communication from the Windows platform as I had over a year ago does not exist any more except with FileZilla, of course.

I get inspired then frustrated after a few weeks researching and trying solutions and give up. This is my third "phase" of re-trying again. Maybe someone has a fresh insight or has found a solution. I am an intermediate PC user with above average skills though no MS Networking certificate holder, no command-line junkie and most of what I've learned these past 20 years has been on the internet, YouTube, etc. I daily teach my fellow workers how to do basic to intermediate Windows tasks with their software, solve a glitch or two, hook up printers, maintain our video security system tasks, and so on but I am no expert when it comes to "cmd" or Power Shell to solve problems. But I can take instructions and fairly understand what I'm told to do.

I "graduated" from the Windows Home Server environment a little before last summer since support for that platform was dropped. That's when I decided to try the Freenas (9.2 if I remember correctly) as my file server instead. It was a little bit of a learning curve but after a couple of weeks of trial and error, I was up and running transferring my files back and forth. I was even at the point of getting OwnCloud/NextCloud working when the Creator's Update "seemed" to strand all my files useless on the FN box inaccessible to my Windows machine. I discovered FileZilla in the process which allowed me access to those files again and I've been on and off searching for the restoration of what I had when I first started the process: Windows communicating "natively" with Freenas. I use Plex, Roku and Nvidia Shield TV all of which communicate by web browser or device within the ASUS 1900RT router environment/network. The singular problem is that Windows 10 WILL NOT communicate across to FN on the file level as I've mentioned before.

I have attached a couple of screen shots to "prove" some things are working as they should. Any suggestions will be appreciated.

:)

 

No NAS Access after windows update

After update Windows machine does not see other computers on network.

Machine 1 - Windows 10 Desktop

Machine 2 - Windows 10 laptop - was working until I got the restart message as I was on the NAS

Machine 3 - Qnap NAS

Machine 4 - Freenas box

MAchine 5 - Linux Box - working fine, how I am access NAS Admin screens

When Windows desktop was only update that had been rebooted - it only saw itself. After update, the Laptop became visible but lap top lost access to NAS

I can ping both nas boxes - no issue

I can log into web interface of Freenas box from Desktop

I cannot log into web interface of QNAP box.

I have reset all routers and switches in the house as well as complete power cycle of Desktop and Laptop and QNAP Nas box (have not power cycled Freenas).

if I put \\IP Address - I can see directory structure of freenas box but nothing for QNAP

 

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?