Computer Hope
Microsoft => Microsoft Windows => Windows Server => Topic started by: wbrost on December 14, 2009, 08:36:28 AM
-
I keep getting an annoying error message when connecting from a client pc to a admin share on a remote server.
"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."
Currently I am having to either (after getting error message) connect to the ip address or RDP to the server and stop the previous session. This is very annoying and time consuming to keep up. Is there any way to allow the previous connection to be replaced with the current requested connection?
-
Are you connecting to the server with the same account each time or a different account? Also, does each account have administrative rights on that computer? If the account has admin rights, it should be able to just kick off the previously signed in user.
Also, make sure you log out (not just close) of the session when you quit unless you know you are going to sign back in with the same account.
-
Are you connecting to the server with the same account each time or a different account? Also, does each account have administrative rights on that computer? If the account has admin rights, it should be able to just kick off the previously signed in user.
Also, make sure you log out (not just close) of the session when you quit unless you know you are going to sign back in with the same account.
I think you miss understood what I am doing. I am only using rdp as a last resort to stop the last session. first I try and do
start
run
\\Server\Drive$
That will connect me to the admin share on the server and prompt for credentials. At this point I enter my admin account information and receive the error message.
I am trying to connect to the admin share on an install server. I always connect with the same account (my admin account). I have full access to the system the users have read only to a specific folder on the server. To gain access to the software installs I need to connect with my admin account.
-
Are you logged in as domain admin or are you logged in as a user? If you're logged in as domain admin, you won't need to enter any credentials, since they're already there.
The only times I've seen the error you're talking about is when I'm logged in as a user and try entering admin credentials to gain access to a default share. Not sure why it does that, but you can work around it by creating a share for the drive and assigning permissions to the users that need it.
-
crap that is what I have done........... When I started at this office we were (around 25 cuts) running more software then we had licenses for. One of the first things I did was to take "Full control" ::) from everyone. That has limited the numbers back down to the appropriate levels. There has got to be a way around this. I will let you know if I find something.
-
It sounds like when you're connecting to the admin share, the PC you're using is trying to pass on the login credentials for the PC you are using, failing, then asking for the domain user name/password, then crapping out with the "Multiple connections..." error.
To work around this, you can either:
a) Log onto the PC you're using with the same domain user name/password you're using to connect to the admin share.
b) If the PC is not joined to the domain, then create a local user account with the name name/password, grant it local admin rights, reboot, and log in with that account. After logging in with that account, connect to the admin share. Enter credentials if asked.
-
I most of the time can not just log off the user because they are in the middle of processing or such. The systems are members of the domain so creating accounts is not a valid option for me.
I was just checking to see if there was an option / setting that would allow what I am trying to do by overtaking or stopping the previous session.
-
As far as I know, there isn't.
If I remember correctly, there's a Microsoft KB article describing this exact issue, which ends with "This behavior is by design."
-
yes they do not want to unintentionally grant elevated permissions to a user. But, I was hopeful that there was a way to override the default handling of the admin shares. so far I have just been doing the following :||x.
I know with a share you create there is the option to enable Access-based enumeration and by pass this issue. But, unfortunately I have not found a way to do this yet.