Sunday, February 10, 2013 1:25 PM
It is about Windows XP Pro SP3.
Some station in local network shares its own files via the SMB/CIFS.
Two users on the addressed machine (see above) want to have
one path on that share to have mapped as a network drive.
Both are going to use a single user account provided by the sharing station;
it should not arise to any issue cause they are connecting to the share
interchangeably - no time simultaneously.
User A was able to successfully carry out the network share to drive
letter mapping operation.
The another one needs to have the same local network path "\\CIFSserverstation\directoryX"
to have mapped under the same drive letter.
His attempt however ends with following error message
"The network folder specified is currently mapped using a different user name and password.
To connect using a different user name and password, first disconnect any existing mappings to this
Then second error pop-up "The mapped network drive could not be created because the following
error has occured: Multiple connections to a server or shared resources 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".
For these two users "net use" provides an empty list of connected shares if to invoke it
shortly after the user B mapping attempt.
What's the reason? How to achieve the aimed goal?
Monday, February 11, 2013 8:55 AM
Are both users logged into the same station at the same time? If not you could use logon and logoff scripts to connect and disconnect the drives as and when the login.
Also it is not possible to connect to the same share with a diffrent account using the same local account. e.g. 1 user on a computer can not connect to the same share with a diffrent username or password. As a work around you can create two shares with diffrent sharenames which would in effect be two diffrent connections to two diffrent shares which is messy but would work.
Share Name : ShareONE
Share Path : \\CIFSserverstation\directoryy\directoryX
Share Name : ShareTWO
Share Path : \\CIFSserverstation\directoryX
Net Use \\CIFSserverstation\ShareTWO
Both are the same location but by giving it a diffrent name when you share the folder you can access it by share name and therefore windows sees it as a diffrent connection.
Wednesday, February 13, 2013 9:56 PM
It is about two account existing on one and the same win XP based machine.
No other machines in local network use accounts with those names.
There is one station in lan which provides own files/directories as network shares.
Other machines exchange data via this point if they need to do exchange anything.
The machine providing network shares is an embedded device, some linux is operating on it.
I guess Samba runs on it. It provides the shares for an user account defined by its own.
Accounts on client machines do not collerate with share account. However this is no problem,
cause client machines asks user for access credentials every time they attempt to use the share
for the first time after new start of client machine.
As one can see, these two CIFS client accounts are never active in network in the same time.
For these two CIFS clients it is not acceptable to have no full-time access to directories on the share.
There are also some other machines in lan, against other Vista based.
On Vista clients there is no problem to map for two user accounts the same share under same driver letter.
Only on XP it does not work. Where to look for the reason?
Wednesday, February 20, 2013 10:28 PM
Registry clean-up was carried out, a clean-up in terms of mapped network drives entries
(obsolete entries and those currently in use). Additionally, in contrast to previous proceeding
during the drive mapping procedure the path of share was not open in windows file explorer,
also the user ensured that net use does not indicate any open connections to provided shares.
All that helped to achieve goal under seek. The network share is successfully mapped to a drive letter now.
I wonder, why the net use didn't indicate any open connection with the share during previous
attempts to map it.
- Marked As Answer by aapapapa Wednesday, February 20, 2013 10:29 PM