Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.

techcoor 1,251 Reputation points
2021-11-05T00:05:49.477+00:00

Windows appears with "\ipaddress\shared is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Multiple connections to a server or shard resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."

Apparently, first message has nothing to do with the problem.

I would want to disconnect all previous connections.

Tried the basics
DISM .exe /Online /Cleanup-image /Restorehealth
sfc /scanow
net use * /d

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,266 questions
0 comments No comments
{count} votes

Accepted answer
  1. MotoX80 31,566 Reputation points
    2021-11-05T13:31:09.843+00:00

    DISM .exe /Online /Cleanup-image /Restorehealth
    sfc /scanow
    net use * /d

    If you're running dism and sfc, you would have needed to launch cmd.exe with "run as administrator". That elevated cmd.exe will not see drives mapped from non-elevated processes unless you added the registry key for EnableLinkedConnections.

    http://woshub.com/how-to-access-mapped-network-drives-from-the-elevated-apps/

    Try running cmd.exe without "run as administrator" and then try "net use * /delete".

    When you access the server, do you always initiate the session the same way? That is, do you always map a drive letter, either from a "net use" command or the Explorer? Does "net use" show that drive before you try to map a drive with the second account?

    What about granting access to your desktop login account to access all file shares so that you don't need to use a second account?

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. techcoor 1,251 Reputation points
    2021-11-07T22:01:20.807+00:00

    “If you're running dism and sfc, you would have needed to launch cmd.exe with "run as administrator". That elevated cmd.exe will not see drives mapped from non-elevated processes unless you added the registry key for EnableLinkedConnections.
    http://woshub.com/how-to-access-mapped-network-drives-from-the-elevated-apps/
    Try running cmd.exe without "run as administrator" and then try "net use * /delete".”

    Ran net use * /delete. Found the first mapped drive and wanted to remove that. (Continuing will cancel the connections. Do you want to continue this operation? (Y/N) Y). Selected enter to delete the first mapped drive and not the one this post is about.

    “When you access the server, do you always initiate the session the same way? That is, do you always map a drive letter, either from a "net use" command or the Explorer? Does "net use" show that drive before you try to map a drive with the second account?”

    Have tried both “net use” and Explorer. Net use now shows no connections. (There are no entries in the list.)

    “What about granting access to your desktop login account to access all file shares so that you don't need to use a second account?”

    Because this is a shared drive for multiple users.

    I will next go in using the mapping that gave me the message using Explorer and then the original mapped drive and no errors on computer 1. On computer 2 reversed mapping and there was no problem .
    Looks like running command prompt without the administrator with command "net use * /delete" worked even though there was no evidence the problem mapping was present.


  2. Limitless Technology 39,336 Reputation points
    2021-11-08T12:20:47.83+00:00

    In DNS check that the (A) record name correlates to the IP and check that the PTR record IP match the host name

    From a machine that can map the drive perform an NSLOOKUP on the IP and hostname then perform the same action on the one that does not work. If you have more than one DNS server look at the DNS server that is being used in the NSLOOKUP command. Check your network adapter settings where DNS Server is configured to make sure it is the same between both machines.

    You can also follow the methods in this thread and see if it is helpful https://learn.microsoft.com/en-us/answers/questions/76836/cannot-access-computer-shared-drive-using-ip-by-ca.html

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer--