A shared folder keeps requesting a username and password even though the password is correct: why is access still denied?
Repeated credential prompts commonly result from an existing session under another identity, an incorrect account format, cached credentials, clock skew, or mismatched share and NTFS permissions.

Establish a factual baseline with “existing net use connections” and “multiple-account conflicts on the same server”, then move to “DOMAIN\user and UPN formats”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking existing net use connections, multiple-account conflicts on the same server and DOMAIN\user and UPN formats independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · existing net use connections | Checking existing net use connections helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of existing net use connections. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 02 · multiple-account conflicts on the same server | Checking multiple-account conflicts on the same server helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of multiple-account conflicts on the same server. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 03 · DOMAIN\user and UPN formats | Checking DOMAIN\user and UPN formats helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of DOMAIN\user and UPN formats. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 04 · Windows Credential Manager | Checking Windows Credential Manager helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of Windows Credential Manager. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 05 · time synchronization and domain authentication | Checking time synchronization and domain authentication helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of time synchronization and domain authentication. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
| 06 · share and NTFS permissions | Checking share and NTFS permissions helps establish whether the effective identity, share and file permissions match the intended access; compare it with a known-good baseline and the incident timeline. | Record the actual state of share and NTFS permissions. Preserve ACL, group and share configuration and use representative users to test read, write, change and delete operations. |
net use
cmdkey /listInvestigation and change sequence
- Capture a baseline for existing net use connections and multiple-account conflicts on the same server and compare it with a known-good system.
- Correlate evidence from DOMAIN\user and UPN formats and Windows Credential Manager to distinguish the direct fault from dependent symptoms.
- Only if evidence points to time synchronization and domain authentication, plan a controlled change with backups, a change window and rollback triggers.
- Finally check share and NTFS permissions and the real business workflow. Confirm the final effective access and application behavior for real file, print or share workflows.
Validation and rollback evidence
- Confirm the final effective access and application behavior for real file, print or share workflows.
- Recheck time synchronization and domain authentication and share and NTFS permissions against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming existing net use connections is sufficient while overlooking multiple-account conflicts on the same server and dependent checks.
- Changing several settings before preserving the original evidence for DOMAIN\user and UPN formats.
- An administrator being able to access a file does not prove normal users have the intended rights.
Common questions and acceptance criteria
What should be checked first?
Begin with existing net use connections and multiple-account conflicts on the same server. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Confirm the final effective access and application behavior for real file, print or share workflows.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
