- I have two Windows 10 Pro computers A and B on the same domain.
- I am logged on to Computer A using a domain account and I'd like to access share 'files' on computer B.
- Before I start
net usereturns zero results and there's nothing in the Windows Credentials manager.
The sysadmin of Computer B has limited access to the 'files' share - only the local administrator (B\Administrator) has access.
Folder security on 'files' is: full control for users SYSTEM and
B\Administrator, and members of the local B\Administrators group. The in-built Everyone group isn't listed.
\\b\filesinto the explorer address bar and I immediately get an error dialog: "Windows cannot access \\B\files. You do not have permission to access \\B\files. Contact your network administrator to request access.". Why don't I get prompted for credentials here once the authentication fails?
- When I access
\\b\C$, I get a prompt to "Enter Network credentials" with red text "Access is denied" at the bottom. Providing local administrator credentials works.
- The audit log on B shows that when accessing both shares, the attempt is made using my domain account, but in the case of the C$ share it is subsequently giving me the opportunity to enter alternative credentials. Why doesn't this happen for the regular 'files' share? Is there something to do with how the sysadmin has configured permissions of the 'files' folder or share?
- I am aware I can use
net use \\B\files * /user:B\usernameor map a drive using the Explorer GUI and supply alternative credentials.
- I am aware I can cache credentials (using cmdkey)
While I'm aware of the workarounds, I'm trying to understand the difference in behaviour and whether I can get the 'files' network share to prompt after the automatically supplied credentials fail.