Suddenly can't map drives

Ok, this is an odd one. Starting last Thursday, I can't map drives between two Win11 Home machines I have in my house.
I'm using
net use t: \\PC1\SharedFolder Password123 /user:ShareUser
and I get the error:
System error 86 has occurred.
The specified network password is not correct.

The user ShareUser exists on PC1 and the password is correct (no, it's not the real password).

I also tried the same command using the IP address rather than the computer name with no change.

I read that KB5068861 can cause issues with sharing, so I uninstalled and hid that update. No change.
I created a new user, gave it access to the shared folder, and tried the command with the new username and password. No change.

running net view \\pc1 gives:
System error 5 has occurred.
Access is denied.

If I go to PC1 (the one with the folder that is shared) and run net view, I get:
System error 6118 has occurred.
The list of servers for this workgroup is not currently available

I'm assuming this is due to SMB 1.0 being turned off, so maybe that's not an issue.

Oddly, PC1 in File Explorer I can see PC2 (but no shares because there aren't any) but on PC2, I can't see PC (although I can see printers on the network).

I've tried resetting the network stack on both computers with:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns

I've updated the NIC drivers.

If I do net use \\pc1 in a normal admin prompt, it prompts for the username and password and then gives the same error as above.
If I use psexec to elevate to a system prompt, then net use \\pc1 - it works, but net use t: \\PC1\SharedFolder Password123 /user:ShareUser gives the same error as above.

I've turned off the firewall on both PCs just in case, no change.

What am I missing?

Try specifying the user name as "PC1\ShareUser" like this:

net use t: \\PC1\SharedFolder Password123 /user:PC1\ShareUser

In other words, replace the username with PC_Name\Username

Let me know if that helps.

tsherr said:

I'm assuming this is due to SMB 1.0 being turned off

Click to expand...

There are very few reasons to turn SMB1 on.


Denis

Try3 said:

There are very few reasons to turn SMB1 on.


Denis

Click to expand...

I agree, but is there an alternative to net view with SMB 1.0 turned off?

tsherr said:

... is there an alternative to net view with SMB 1.0 turned off?

Click to expand...

Net view does not depend on SMB1.
Enter this to see Net View Help
net view /?
or go to
net view - SS64


Denis

Try3 said:

Net view does not depend on SMB1.
Enter this to see Net View Help
net view /?
or go to
net view - SS64


Denis

Click to expand...

OK, thanks. I had read new view was deprecated and was reliant on SMB1. I appreciate the information.

hsehestedt said:

Try specifying the user name as "PC1\ShareUser" like this:

net use t: \\PC1\SharedFolder Password123 /user:PC1\ShareUser

In other words, replace the username with PC_Name\Username

Let me know if that helps.

Click to expand...

Unfortunately, that generates the same error that the password is wrong. I can log into PC1 with this username and password, so I know it's correct.

Understood.
So, back to the problems you are experiencing, can you connect using simple shortcuts?
e.g.
\\PC1\SharedFolder\
and manually entering the shared Admin account name & password to authorise the connection?

tsherr said:

I can log into PC1 with this username and password

Click to expand...

What I am referring to is an Admin account on every network computer that has the same username & the same password.


Denis

Try3 said:

Understood.
So, back to the problems you are experiencing, can you connect using simple shortcuts?
e.g.
\\PC1\SharedFolder\
and manually entering the shared Admin account name & password to authorise the connection?

What I am referring to is an Admin account on every network computer that has the same username & the same password.


Denis

Click to expand...

If I try opening file explorer and going to \\PC1\SharedFolder\ (by typing it in the address bar, since I can't see the PC1 in the Network list), it asks me for a username and password: I've tried the main username and password for PC1 (which happens to be PC1 and XXXX). That is rejected as incorrect. I have a second account on PC1 called ShareUser with the password Password123 (no, not really, but for our purposes), that is also rejected as incorrect.

I've cleared Windows credentials on both machines, I've created a new user and given it permissions to the shared folder, but the password is always rejected as incorrect.

At the command line, I've tried net use, with the same results (using either the name of the computer or the IP address).

tsherr said:

Starting last Thursday

Click to expand...

What happened last Thursday? The cumulative update KB5068861 that you mentioned?
And you have unloaded SMB1?
There seem to be lots of people reporting the same problem as you recently and several of them mentioned having SMB1 loaded.

tsherr said:

I've tried the main username and password for PC1

Click to expand...

I always create the same additional local, password-protected Admin user account on all network computers using both the same username & the same password.
I believe that your way should work aswell but I've never tried it.
Perhaps Brink can help you - check the tutorial advice then, if necessary, explain the problem in a post in the tutorial thread.
Share Files and Folders Over a Network - TenForumsTutorials [This tutorial also applies to Windows 11]


I'm afraid I won't be able to help you beyond the checks we've already discussed.
I've never developed network fault-fixing skills because I've been fortunate enough to have not experienced any network problems. This is how I set up my networks and I have never had it fail on me [even on WIndows 11 current builds].
A consolidated network setup checklist for Windows 10 and 11 - my post #4 - TenForums


Best of luck,
Denis

I'm having the same issue. anyone find a solution?

Even if you're using the same Microsoft account or the same local account/pw on all devices, Windows does not automatically treat it as the same user across machines for file sharing. Credentials still need to be authenticated per session.

Here's what I did to stop all the crazy credentials problems.
Create a Windows credential for an account & password on all computers on your network you are sharing files between. It must be a password, not a pin. While you can still use a pin to login, you must restart the device and log into it using a password at least once for this to work.
. (example I have 4 computers in my network. In each of them, I created a credential for the other 3.)

Even if you are using the same MS account, a credential should be created.

To create a credential:
Go to Control Panel>Credentials> Windows Credentials>add a windows credential

In the "Internet or network address" box, type the name of the computer on the network that you want to access.
In the User name and Password boxes, type the user name and password that you use for that computer, and then click OK.
Note: It must be a password, not a pin.

You indicated your systems did not show in the network map. Try this to see if it will make them appear.

Do this on all systems in network..

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:
sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation

Reboot each device after executing this command, and the devices should see each other more reliably in Network and File Manager.

glasskuter said:

Even if you're using the same Microsoft account or the same local account/pw on all devices, Windows does not automatically treat it as the same user across machines for file sharing. Credentials still need to be authenticated per session.

Here's what I did to stop all the crazy credentials problems.
Create a Windows credential for an account & password on all computers on your network you are sharing files between. It must be a password, not a pin. While you can still use a pin to login, you must restart the device and log into it using a password at least once for this to work.
. (example I have 4 computers in my network. In each of them, I created a credential for the other 3.)

Even if you are using the same MS account, a credential should be created.

To create a credential:
Go to Control Panel>Credentials> Windows Credentials>add a windows credential

In the "Internet or network address" box, type the name of the computer on the network that you want to access.
In the User name and Password boxes, type the user name and password that you use for that computer, and then click OK.
Note: It must be a password, not a pin.

You indicated your systems did not show in the network map. Try this to see if it will make them appear.

Do this on all systems in network..

add "LanmanWorkstation" as an additional startup dependency for the "Function Discovery Resource Publication" (FDResPub) service, which seems to do the trick. To do this, you simply open an elevated command prompt (i.e. use the "run as administrator" right-click context menu option to start cmd.exe), then execute the following command:
sc config fdrespub depend= RpcSs/http/fdphost/LanmanWorkstation

Reboot each device after executing this command, and the devices should see each other more reliably in Network and File Manager.

Click to expand...

I created the same userIds (for different users) across all systems in my network. Desktop doesn't have a password. The laptops do. Has worked flawlessly for years now.

glasskuter said:

Even if you're using the same Microsoft account or the same local account/pw on all devices, Windows does not automatically treat it as the same user across machines for file sharing. Credentials still need to be authenticated per session.

Click to expand...

Great info! Thanks for sharing this.

BTW, since you are adding the dependency using the command line, we could also just create the credential(s) in Credential Manager from the command line as well like this:

cmdkey /add:server01 /user:UserName /pass:MySecretPassword