I recently posted a question ( http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3381231&SiteID=17) asking how to make two simultaneous connections with different users to different shares on the same server. I was told that the inability to do so was security related. Can someone explain exactly howthis lack of functionality is in fact a 'security feature' as opposed to a 'bug'? Especiallygiven that theability to 'trick' the system into thinking it's making two connections to two different servers using the HOSTS file is so simple? Or is this just another case of Microsoft deciding the end user is too stupid to know what he or she is doing?

Hi, Please refer to the following KB article. Error message when you use user credentials to connect to a network share from a computer that is running Windows XP: "The network folder specified is currently mapped using a different user name and password" http://support.microsoft.com/kb/938120 This applies to Windows Vista as well. This behavior is by design as one server (uniquely identified by the given name) can only have one user authenticated to it at a given time. Thank you for your understanding.

This article does not answer the question. The article states that this is by design, but it does not say WHY it was designed this way. In a previous post, you said it is a security feature. However, nowhere has Microsoft or its representatives explained in what way it is a security feature. "It is for security." "Why" "It is designed this way." "Why?" "It is for security." So let me make this question much more clear: 1.) What attack would be possible if a given client could access two shares using two different credentials on a server, that is not possible by the virtue of this "feature"? 2.) Why does this flaw not exist if I connect using two different IPs or DNS aliases to the same server? If there is no such attack possible, or no explanation for the flaw not existing in the alias scenario, then this is NOT a security feature.