Windows 10: Accessing Windows FROM NAS servers -- Windows latest update

Hi there
can anybody suggest what needs to be done to access windows files FROM Nas servers (running SAMBA). The latest version of windows seems to have broken connections -- now just get message timeout on server when trying to access Windows shares FROM a NAS server.

No problem with windows accessing the NAS server shares (i.e FROM windows TO Nas problem is NAS TO WINDOWS). Computer name is seen in the network map and ping is OK.

people have suggested it's because Windows has depreciated the way it handles SMB connected files (or CIF).

Is there ANYWAY to make this working again.

The crazy thing is that ANDROID devices seem to have no problem -- for example I have some music files on Windows which I access from a Samsung S8 phone via a program called SambaPlayer (VLC for android also works) and play via blue tooth to a small Bose mini 10 speaker.

I need the server to be able to handle Windows files as I run the backups from the server . Even if I run the backups locally on Windows via macrium I'd like the server to automatically upload these files to the server.
Before the last update Windows had no problems -- seems every update or so breaks windows networking.

I don't use logon domains, profiles etc etc --simple HOME network with a few Windows laptops etc.

Cheers
jimbo

:)

 

Windows Credentialing

I work in an Architectural office, where we have a Windows domain-based network and 2 branch offices in addition to our main office.

We have a stand-alone NAS installed in one of our branch offices. The NAS is joined to the domain and looks to the domain controller in our main office for the domain users and what permissions to apply for access.

We have a mostly Windows 7 Pro computers, with 2 Windows 8.1 computers and now few "upgraded" Windows 10 computers. The domain controllers are Windows Server 2008 R2, and we have a few other Windows Server 2012 servers.

We're finding a user logged in to a Windows 7 machine, or a Windows Server 2008 server, can access the NAS device as he should be able to. If the same user logs in from a Win 8.1, Win 10 or WS 2012 computer, he will not be able to access the file structure
on the NAS at all- a Windows Security dialog box pops up and prompts for the username and password, and will fail after two attempts with a "Network Error; Windows cannot access
L: \\NASname, Error code 0x80004005" dialog box.

The user can successfully ping the NAS, just not access anything on it. All other network functions appear normal.

Please keep in mind the same user with the same credentials can then log in to a Win 7 machine and access the NAS normally.

Does anyone know what's going on, and how I can resolve this?

 

SQL Server 2012 Express can't read database files located on NAS after upgrade to windows 10

Hi,

I have SQL Server 2012 Express on a pc with windows 8.1. The data base files are located on a NAS. It works fine. After upgrade to windows 10, SQL Server can no longer access the files on the NAS. Access fails with 'operating system 58 error'. Downgraded
to windows 8.1 and SQL Server works again.

How do I fix the problem with windows 10?

 

Have you tried enabling this? The text says "allow insecure ie non Windows" connections is on by default but I have seen claims the default is now off ie text is out of date

 

You would not unless you are able to map those shares some way. On the Synology NAS DSM, the only way would be through a share sync. Anything you do on your Windows machine, would be synced to the NAS as a Cloud storage device. I do that with my Google Drive on my NAS.

 

You might want to check out Syncthing. Open Source, install on you Windows machines and sync with your server. There are server side versions as well. Works well on my LAN!

Oh, and I agree with bro67, this is the best solution to MS breaking networking every time you turn around!

 

I think you mis-understood the problem -- Windows TO NAS is fine it's NAS TO Windows that's the problem.

Cheers
jimbo

 

No, I did not misunderstand the problem. Syncthing works both ways. You install it on both sides and it works via authentication keys between devices over network connections. No SMB involved. There is a version for Synology too.

 

That is a Windows problem, not a NAS issue. I would use a third party program like Syncthing or depending on the NAS, use the manufacturer's program. I have yet to have Windows screw up any syncing with the Synology Cloud tool, same as being able to open up a shared or Network share from my NAS.

What you do with your system is far beyond what would happen in a Enterprise, let alone on a Home Network or SoHo.