When I enter my password I also check the box to remember my credentials. As soon as I map a drive to a NAS directory, MYSERVER no longer shows up under Network. An interesting thing is, when I have done this MYSERVER shows up under Network in Windows Explorer. If on the Surface I disconnect all the mapped drives, I can then type \\MYSERVER in Windows Explorer address bar, get a Windows Security dialog, enter my NAS password and have access to the NAS. All the mapped drives have the disconnected icon and if I click on a mapped drive, I get an error saying "An error occurred while reconnecting M: to \\MYSERVER\Mdirectory Microsoft Windows Network: The local device name is already in use." In response I get a dialog that says I might not have access (which I do) and then something about multiple connections by the same user. My NAS username is filled in so I enter my NAS password. When I try to access the NAS by typing \\MYSERVER in Windows Explorer address bar (which is what I did to setup the mapped drives in the first place) I get a Windows Security dialog asking me to 'Enter network credentials'. If I reboot the Surface, or even just sign out, when I sign back in I cannot access the NAS or mapped drives. That worked until I shutdown the Surface. I then setup my Surface to access the NAS, and mapped drives to some directories on it. I setup my Lenovo first to access the NAS, and mapped drives to some directories on it. I sign in to both computers using my Microsoft account. One computer is a Surface Pro 4 running Win 10 Pro. One computer is a Lenovo laptop running Win 10 Home. I access the network from 2 computers using WiFi. I have activated new protocols SMB in the NAS, not recognizable on Windows 10, Apple's Mac and Linux is recognized NAS, the Microsoft network is activated.I have a Synology DS220j NAS on my home network.Network service NFS on the Windows computer, check whether the NAS is listed in Windows Explorer under, the workgroup checked on NAS and client, may be missing to display the NAS in Windows Explorer?.Network service Windows client can not reach I have to make the network service for Synology specific setting for NAS, look for the reason why network storage is not listed in Windows Explorer?.Updated on: 23 September 2022 09:34 Windows ►► Identify network problems with the command prompt! ►► Show available WiFi networks on Windows 11 ►► No connection via WLAN / WiFi on my Windows 10/11 Surface, why? ►► The network drive folder keeps disappearing? Which can also indirectly affect the NAS access. However, other problems can also arise that are not so easy to fix, here are other helpful tips that can help you with any network problems you may have. You can easily apply this simple and fast SMB solution to other Microsoft Windows System configurations, whether it's a Windows desktop, tablet, Surface Pro / Go, or even a server operating system.ģ.) Further tips on possible problems with the network!Īs you can see, problems with NAS (Network Attached Storage) which are usually very rare can have a small root cause. As you can see at the top of the Windows 10 shot screenshot, it is quite easy to access NAS again. The elegant way to enable SMB 1.0 / CIFS file sharing support is not just for Windows 10 desktop computers. Yes, not only on Linux, Appel's Mac OS or Android you can easily use SMB or NAS. Making sure your Windows 10 has SMB support on your Windows 10 computer is no magic.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |