• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

smb being a jerk

Red Squirrel

No Lifer
I'm trying to map a second drive letter (Ive done this millions of times) but this time it wont let me. Why?

This is the error I get:

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.


Why?! I do it all the time. This is a samba server, if it matters.
 
open a folder > tools > disconnect network drive

if it prompts with no network drives to disconnect, try rebooting, if can't reboot try disabling then enabling the network interface.
 
I only had one network drive mapped, and I often have multiple drives mapped at once. But I ended up just doing the transfer through network places (without mapping it).
 
It's complaining because you're trying to map two drives to the same server under different usernames and that doesn't work.

Multiple connections to a server or shared resource by the same user, using more
than one user name, are not allowed.
 
possibly, however, I've sometimes disconnected all network drives and still gotten this error. rebooting fixed it.

bottom line: that error seems to be dodgy sometimes.
 
Yeah in my case it was strictly 1 user, the drive simply maps when it gets logged into. now that I think of it I might of had a background TS session still going, and that drive is set to map by default for everyone.
 
bottom line: that error seems to be dodgy sometimes.

No, most likely you're still connected to the machine. You don't have to have drives mapped to be logged into a SMB server. Type 'net use' and see if you're connected to the machine's IPC$ share or something.
 
spot on.

however, I can't remember if I killed all pertinent connections to the node, before trying to connect again -- indeed, perhaps I didn't.
 
Back
Top