Technical Anshu
Tutorials Blog
Share Password Loop

Network Shares Keep Asking for Password After NTLM Hardening

The share worked for years. Then an update or a security setting landed, and now Windows asks for the password every time - sometimes refusing the right one. Three causes explain almost every case, and none of them needs a reinstall.

By Technical AnshuWindows 10 / 11 / Server6 minute read
Watch the full video - the complete NTLM blocked fix, step by step

A password prompt that loops is not Windows being stubborn. It is a negotiation failing silently behind the prompt: your PC offers one authentication method, the other machine refuses it, and Windows politely asks you to try again - forever. The prompt is the symptom, not the disease. Here are the three real causes, in the order they actually occur, and the fix for each.

Windows Security - Enter network credentials
Enter network credentials
Enter your credentials to connect to: 192.168.1.50
User name:  ______________
Password:   ______________
The user name or password is incorrect.
Notice the address: an IP address, not a computer name. That is clue number one.

The looping credential prompt, shown as an example. Connecting by IP address is the most common trigger.

1

Cause 1 - You Are Connecting by IP Address

Kerberos tickets are issued for names, not numbers. The moment you open \\192.168.1.50\share instead of \\SERVER01\share, Windows falls back to NTLM - and if the server has been hardened against NTLM, or refuses NTLMv1, the logon fails no matter how correct the password is.

This single change settles a large share of these complaints, because nothing about the account or the password was ever wrong.

  1. Disconnect the mapped drive or close the window
  2. Reconnect using the computer name: \\SERVER01\share
  3. If the name does not resolve, fix DNS or use the fully qualified name - do not go back to the IP address as the permanent route
2

Cause 2 - LAN Manager Authentication Level Mismatch

The policy Network security: LAN Manager authentication level (under Security Options in Group Policy or Local Security Policy) decides which challenge-response flavours a machine will send and accept. At the strict end it sends NTLMv2 responses only and refuses LM and NTLM. If the other side is older - a NAS, a legacy server, a workgroup PC with a lower level - the two sides cannot agree, and the password prompt loops even though both passwords match.

  1. Check the setting on both machines - the mismatch is the problem, not either value alone
  2. Prefer raising the weaker side (a device or old PC) toward NTLMv2 rather than lowering the hardened side
  3. If one device genuinely cannot rise, scope the exception to that device instead of lowering the level domain-wide
3

Cause 3 - A Stale Saved Credential

Windows remembers. If the password on the server changed - or was once typed wrongly and saved - Windows keeps presenting the old credential first, and the server keeps refusing it. The prompt you see may not even be using what you just typed.

Also confirm the account form: on a workgroup, the server expects SERVER01\username with the account that exists on the server - not your local PC's account that happens to share the name.

  1. Open Credential Manager and go to Windows Credentials
  2. Find the entry for the server name or IP address and remove it
  3. Disconnect any mapped drive to that server, then reconnect and type the current password once, cleanly
4

How to Tell Which Cause You Have

Quick triage: if connecting by name works but by IP fails, it is Cause 1. If it fails from one PC but works from another with the same account, compare the LAN Manager level and clear saved credentials - Causes 2 and 3 live on the client. If it fails from everywhere for every account, the change is on the server side: check the Restrict NTLM policies and the audit log (event 8002 shows the refused incoming attempts with names and addresses).

🔴 The honesty line: the tempting fixes for a looping prompt - turning password-protected sharing off, enabling the guest account, or dropping the authentication level everywhere - all trade a small annoyance for a large hole. A share that accepts anyone is worse than a share that asks twice. Fix the negotiation, not the lock.

Watch the Complete Fix in the Video

The full process with live demonstration - every setting shown on screen, step by step.

Watch Full Video
Common Questions

Why does the share accept my password from one PC but not another?

Because the difference is on the client, not the account: the failing PC is usually connecting by IP address (forcing NTLM), has a lower LAN Manager authentication level, or is silently presenting an old saved credential from Credential Manager.

My password is definitely correct but Windows says it is not. Why?

When authentication negotiation fails, Windows reports it as a credential failure. If the server refuses the protocol your PC offered - NTLMv1 after hardening, for example - the correct password is refused with the same message as a wrong one.

Should I just save the credential so it stops asking?

Saving the correct, current credential is fine and normal on your own PC. But save it only after fixing the cause; saving on top of a negotiation failure just preserves the failure.

This guide is based on the Technical Anshu video on the NTLM authentication blocked error - if a step gets stuck, ask in the video comments and you will get help there.