![]() ![]() Since its only one user among others that are also using Windows 10, I don't think that problem is SMB1 related. So don't believe that your client side reports you the full picture. I didn't finish analyzing Windows firewall and other aspects at client device. I'm currently analyzing a similar issue on my site where the NAS reports user for network share successfully accepted and authenticated while the client side reports the opposite. You may look if the credentials went through to the NAS and got confirmed and accepted on the NAS. I guess it a configuration and permissions issue probably at the client side. Have a look into the events and logs on NAS side and on client side. the situation of that user on that device. You may try to further analyze your situation resp. NetDoge wrote:or how could I tackle this issue? It does understand not only web URLs but also file URLs in various notations. Or you could use Windows Internet Explorer. You could try the Windows console with the net command for mapping network drives. NetDoge wrote:A solution in my mind is to use an alternative client to access the file server, but couldn`t find one.
0 Comments
Leave a Reply. |