>Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed

>I got this error when I tried to access a remote share from one of our DR servers. Well, apparently, the DR server configuration was not designed properly which is probably the reason why I am getting this error. The production and DR server both have the same configuration (or course, they are on a different network segment which is why this is possible) and I only get to access one or the other using a separate VPN profile. I was trying to copy a database backup from the production server and moving it to the DR server. The resolution: just run a net use * /delete command. It may sound simple but it works and that’s what is more important. Having the same configuration (hostname and IP address, in my case) is causing my Windows XP workstation to get confused so a simple purge of the cache of my shared folder information. I would have to do this quite often as I need to connect to both servers on a regular basis

Please note: I reserve the right to delete comments that are offensive or off-topic.

Leave a Reply

Your email address will not be published.

3 thoughts on “>Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed

  1. >Its not a configuration mistake, its an example of stupid Microsoft bad programming. According to whoever wrote this function, there is no appropriate reason for someone to try to access the same resource, at the same time, from two *OMFG* different terminals (oh, and by the way, it’s apparently worded like that because Microsoft knows that you don’t *ACTUALLY* have to be logged in at the same time — the session need only persist). I hate stupid programers!

  2. >Humm. Not eactly right. You can access the same resource at the same time from two different terminals. This error message happens when you try to connect to a resource with credentials that are different from the credentials that you are already connected to the resource with. Ideally, the newer credentials would just replace the older credentials, but in windows you’re in the same user space so you can’t connect to the same resource with *both* sets of credentials at the same time.If you start a new commend shell with runas and give that new shell process different (new) credentials, then you can can connect to the shared resource with those (new, different)credentials, but windows sandboxes that shell from your other shell(s).It’s not a “stupid Microsoft” programming error, it’s a security thing. And seriously, if you’re going to bash anything/anyone, have the guts to post with your name, Mr. Anonymouse.