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 running a proprietary operating system (based on Linux) 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 to each user for access.
We have 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 “name-of-NAS”, Error code 0x80004005″ dialog box.
The user can successfully ping the NAS, just not access anything on it. All other network functions appear to be normal, with the user able to access to all printers and to all file shares controlled by Windows servers.
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?