Network Drive is not accessible: the user name or password is incorrect

• Rebooted both machines into oblivion
• Rebooted Modem & Router (UniFi Dream Machine SE)
• Verified Folder sharing settings (on server)
• Synced Windows time in Settings
• Cleared Windows Credential Logins (each time)
• Cleared MountPoints2 Registry Folder
• Mapping with IP address instead of Device Name
• Enabled File Sharing SMB settings in Windows Firewall
• Changed IP Address
• Reset Network Adapter
• Verified Advanced File Sharing Settings
• Created alternate User Account
• Local Security Policy > LAN Manager Authentication Level > Changed to: Send NTLMv2 response only. Refuse LM & NTLM
• IP Flush
• Windows 11 Repair (Under System > Restore)
• Typing credentials in all caps
• Switched from Ethernet connection to WiFi

gunrunnerjohn said:

Are these machines Win11 Home or Win11 Pro? If a mix, is the "server" a Home or Pro machine? Is the "client" a Home or Pro machine?

In Control Panel\All Control Panel Items\Programs and Features\Turn Windows Features on or off.
Check if there are No Ticks are on SMB 1.0/CIFS Client and SMB 1.0/CIFS Server Only a tick on SMB Direct

Make Sure you are on a Private Network NOT Public

Next go into Group Policy (Pro Version Only) gpedit.msc

Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

Reboot

Click to expand...

techmech said:

All machines, including the shared folder machine are Windows 11 Professional.

Changed settings as mentioned above, but still no luck I'm afraid.

Click to expand...

techmech said:

I have four Windows 11 computers networked together in a Private network, one of which acts as a server with a shared folder that all can access. As of recently and at random, 1 workstation absolutely refuses to successfully map the drive. Every time I try it comes up with the error:

Network Drive is not accessible: the user name or password is incorrect.

The credentials are accurate, it's even a local account with a password - not a PIN. I have tried everything I know to do to get this to work, but I can't figure it out! As I mentioned, all the other machines are connected and kosher. I've even re-mapped the drive successfully on a separate laptop just to see if I could.

I can successfully ping the server computer from this problematic machine. And I even see the server computer under Network Devices in File Explorer.

Things I've tried:

• Rebooted both machines into oblivion
• Rebooted Modem & Router (UniFi Dream Machine SE)
• Verified Folder sharing settings (on server)
• Synced Windows time in Settings
• Cleared Windows Credential Logins (each time)
• Cleared MountPoints2 Registry Folder
• Mapping with IP address instead of Device Name
• Enabled File Sharing SMB settings in Windows Firewall
• Changed IP Address
• Reset Network Adapter
• Verified Advanced File Sharing Settings
• Created alternate User Account
• Local Security Policy > LAN Manager Authentication Level > Changed to: Send NTLMv2 response only. Refuse LM & NTLM
• IP Flush
• Windows 11 Repair (Under System > Restore)
• Typing credentials in all caps
• Switched from Ethernet connection to WiFi

If anyone has suggestions, I'm all ears. But hurry, I'm fixing to pull them off in frustration!

Click to expand...

OAT said:

So to sum it up, you have a machine that can't access the share on the machine (used as a server) if manually mapped.

Is RDP'ing to that system where the share resides successful?
Are all Windows 11 the same version? I just don't mean Pro.
What does a ping from the system that fails connecting tell you?
What is the network mapping used and how are you attempting to map? Drive or a share$?

You say you have a local account but is it common to all machines in the network?
What I mean is each system user \\machine1\user1, \\machine2\user1 & \\machine3\user1 must be given rights to that share.
A local user is only local to that system and not common to all despite the username being the same.

Click to expand...

1. Remote Desktop Connection does not work to the server PC. Getting same credentials error.
2. All machines are the same versions and builds
3. Pinging the server from the problem-PC doesn't show any packet loss (Assuming that's what you're asking?)
4. I'm mapping from File Explorer using the server name and shared folder (\\SERVER\Shared Folder)
5. I have the folder sharing settings to Everyone, and they all have and had access for a long time until this issue popped up on this one machine.

OAT said:

What about scrolling up a bit?

Click to expand...

HTA said:

Are the machines clones?

Click to expand...

As of recently and at random, 1 workstation absolutely refuses..................

Click to expand...

Vimes said:

so, the other three work fine interacting as expected with each other..?

Click to expand...

Vimes said:

For me all of my Windows 11 PC's seemed to work fine over the LAN with build 24h2.26100.4946.
It was when they updated to build 6584 that things became a problem, on one in particular.
What build version is it for you..?

Click to expand...

Vimes said:

I resolved the access issues, for RDP and mapping etc, being denied, by creating another account on each machine. This one being a local account of the same name and password, just easy to remember, and used that to gain access and shares etc. That was following watching a video on YT that suggested doing that. That account has administer privileges

Click to expand...

tbmljk said:

Download and use the free Credential File View program by Nirsoft. It will read the encrypted credentials on your computer to see if they match the "correct" credentials you have been using

Click to expand...

techmech said:

That's correct. All are connected like they have been since I set them up. I even mapped said server/drive on a separate laptop.

Both the problem computer and server computer are on build: 26100.6584

Funny enough, the User and Password are the same as it is on the server machine already.

Click to expand...

Also it wasn't only necessary, for testing anyway, to set the sharing options for "everyone" but to now set the Security option, with full access ticked, for everyone also. This can be done on the same tabbed Window as setting the share options.

Click to expand...

Vimes said:

When I posted....





did you try that..?


All of my logins were the same, apparently that was no longer enough.

Click to expand...

techmech said:

I had already set it to Everyone with Full Control/Change/Read ticked for the shared folder in question.

Click to expand...

I have the folder sharing settings to Everyone, and they all have and had access for a long time until this issue popped up on this one machine.

Click to expand...

Vimes said:

Yup, noted in your first post.....



but I'm noting the security settings and not the sharing ones. For me they had to be created and set for each share.

Unless you mean that also..?

Click to expand...

techmech said:

So in my security tab I also added "Everyone" to the list with full control. Rebooted and still having the same issue.

Click to expand...

Vimes said:

On the workstation that is giving you issues with RDP, and mapping, have you tried to delete its Windows based credentials it uses to try and access other machines, through the Control Panel / Credential Manager...?

Then, as a test, create an admin level local account on another PC on the same network / workgroup, with user name and password. Then go to the problem PC and try and connect to the PC using the newly created credentials, username and password, that you just created on it as a local account..?

Click to expand...