This is the scenario. I have a Ubuntu VPS which has two Samba shares on it used for remote back-up. One is mine and the other I setup for a friend.

So for the same of argument, let's say my VPS IP is 1.1.1.1 and the shares are called \Fred (me) and \Barney (friend)

So to access my share is simple, I just enter \\1.1.1.1\Fred and since my credentials are remembered I only had to login once, from that point it always just worked.

Now, after I created my friends share, I of course tested it to see if it was working. I accessed \\1.1.1.1\Barney and was presented with a login prompt (as the username and password is different for that share). After entering the user/pass I setup for my friend, his share appeared. Great, all working. But, now comes the nightmare.

I then tried to access my share again, and Windows throws a tantrum saying I do not have access. Huh? This can't be right, so I tried logging into it from another machine, just to check I hadn't messed up the smbd settings on the VPS. That worked fine, so I know the VPS's samba is not at fault.

It seems as though Windows doesn't like accessing the same SMB server using two user names. Many searches yielded the same answers. Clear the sessions and clear the credentials. So I opened Credentials manager and removed all traces of the server ip from there. I then started a command prompt as administrator and tried to delete the session that was open to the \Barney share with net. Nope, no such session exists. Well that's nonsense, because every time I try to access \Barney I'm NOT presented with a login prompt, so Windows is holding the session somewhere. So my questions are

1. Why doesn't Windows simply terminate the existing session if an attempt to login with another user is made?

2. How do I clear the existing sessions? Please don't tell me to use:
- Credentials Manager
- net session /delete
- net session \\1.1.1.1 /delete
NONE of those methods work.
net use - returns nothing.

Restarting the computer and/or logging out are not acceptable solutions.

Thanks for any help.

Dan

Well no thanks to anyone but myself for figuring out the answer. The solution was to restart the "Workstation" service.

Great support guys. Thanks.

• Marked as answer by Cordel Frankton 20 hours 11 minutes ago

Well no thanks to anyone but myself for figuring out the answer. The solution was to restart the "Workstation" service.

Great support guys. Thanks.

• Marked as answer by Cordel Frankton 20 hours 11 minutes ago

Well no thanks to anyone but myself for figuring out the answer. The solution was to restart the "Workstation" service.

Great support guys. Thanks.

• Marked as answer by Cordel Frankton Saturday, December 27, 2014 3:38 PM

Well no thanks to anyone but myself for figuring out the answer. The solution was to restart the "Workstation" service.

Great support guys. Thanks.

• Marked as answer by Cordel Frankton Saturday, December 27, 2014 3:38 PM