Question:
This New-PSDrive command
|
1 2 |
New-PSDrive -Name Z -PSProvider FileSystem -Root \\$j\share -Credential $credentials -ErrorAction Stop |
Causes the error
|
1 2 3 |
New-PSDrive : Multiple connections to a server or shared 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 |
I have tried disconnecting all drives first, then creating new drive,
|
1 2 3 |
net use * /delete /y New-PSDrive -Name Z -PSProvider FileSystem -Root \\$j\share -Credential $credentials -ErrorAction Stop |
I get the output
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
You have these remote connections: \\TSCLIENT\C \\TSCLIENT\D \\TSCLIENT\E \\TSCLIENT\I \\TSCLIENT\J \\TSCLIENT\K \\TSCLIENT\L \\TSCLIENT\R \\TSCLIENT\T Continuing will cancel the connections. The command completed successfully. New-PSDrive : Multiple connections to a server or shared 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 |
I also tried removing the Z drive first
|
1 2 3 |
Remove-PSDrive -name Z New-PSDrive -Name Z -PSProvider FileSystem -Root \\$j\share -Credential $credentials -ErrorAction Stop |
And get error
|
1 2 3 4 5 |
Remove-PSDrive : Cannot find drive. A drive with the name 'Z' does not exist. ... New-PSDrive : Multiple connections to a server or shared 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 |
How to fix?
UPDATE
I even rebooted the machine and changed the drive name, but I still get the same error of “New-PSDrive: Multiple connections ……”
UPDATE 2
I have also tried using IP address instead of computer name, but that doesn’t work either, http://support.microsoft.com/kb/938120
Answer:
I found workaround to this problem that seem to always work. You need to change the computer name, but since this will also stop working eventually just as with server name and IP, you need the option to specify arbitrary number of new computer names resolving to the same computer.
The obvious choice is hosts file. You can add any number of aliases to the IP to it. Afterwards, use the alias that isn’t already blocked.
==== EDIT ===
Here is the handy function:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
<# Use unique hostname for this script by altering hosts table to handle situation with multiple different scripts using this share with different creds which leads to following Windows error: Multiple connections to a server or shared 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 #require -RunAsAdministrator #require -module PsHosts https://stackoverflow.com/a/29059100/82660 #> function Set-UncHostnameAlias($UncPath) { $remote_hostname = $UncPath -split '\\' | ? {$_} | select -First 1 $remote_alias = (Split-Path -Leaf $MyInvocation.ScriptName) -replace '.ps1 Do this on the start of the script: |
and used aliased path afterwards with the New-PSDrive. This works always, even if some other scripts on the same system use different credentials for the same server.
Source:
net use * /delete /y doesn't resolve error "New-PSDrive : Multiple connections to a server ...." by stackoverflow.com licensed under CC BY-SA | With most appropriate answer!
$hostEntry = Get-HostEntry $remote_alias* -ea 0 | ? { $_.Comment -eq $remote_hostname } | select -First 1
if (!$hostEntry) {
$remote_alias += (Get-HostEntry $remote_alias*).Count + 1
Write-Verbose "Adding alias $remote_alias => $remote_hostname"
$remote_ip = Test-Connection -ComputerName $remote_hostname -Count 1 | % IPV4Address | % IPAddressToString
Add-HostEntry -Name $remote_alias -Address $remote_ip -Force -Comment $remote_hostname | Out-Null
} else {
$remote_alias = $hostEntry.Name
Write-Verbose "Using $remote_hostname alias: $remote_alias"
}
$UncPath.Replace("\\$remote_hostname", "\\$remote_alias")
}
Do this on the start of the script:
|
1 |
and used aliased path afterwards with the New-PSDrive. This works always, even if some other scripts on the same system use different credentials for the same server.