Hi there, i have problems connecting to network drives on Windows7 Professional. The Shares are Samba-shares from a DebianLinux. On this Server exist different Users which should get different network drives. To get these drives on the clients we use a VisualBasic tool which is on a guest share on the Server. The Client can also "logoff" wich is realised by a simple "net use /del" so somre users can acess their files on the same computer. This program sends username and password to the server and he then creates *.bat files (net use etc.) to connect the users drives. To do so the connection uses his ip adress e.g. "\\10.94.1.3\login$\xxx.exe" and user nobody as guest. The created *.bat file contains the net use commands as "\\servername\share" with the users anme and individual password. If it happens that different user Log on and off or the same user logs on and off windows brings up an error message: Error 1219. Multiple Connections to a Server or a shared Resource from the same user .... but at this point all shares are disconnected with net use /del. At the moment we have to restart those clients the log on again and get the same message after a few log on/off again. Anyone knows a solution to this? It only happens on Windows7 maschines (WinXP an Win2k without Problems), and the local users of the clients dont exist as any linux/samba users. Could it be using "net use /delete" that the shares and connections arent removed completely or some Security options i missed? Hope you can help us. Best Regards, JFuchs

Hi, Thanks for posting in Microsoft TechNet forums. Please use the command "net use" to view the connections and check if a mapping to the server with no drive connection. If so, used the "net use <mapping> /d" command then retry the connection. After that, net use * /d command again. You can also try to do the new mapping to \\server.domain\shared folder or \\10.94.1.3\shared folder This will simply open a new shared resource. Try it, then re-run the net use command to verify this. If the issue persists, click start, type services and press ENTER. Find the following two services and disable them. Server Workstation Their depending services need to be disabled alone.\ Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Thanks for posting in Microsoft TechNet forums. As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi there, it seems its adequate to just restart the workstation service. But this just works on the GUI tab of the services, not with a batch script. Is there a designated sequence for the dependent services to stop and start? This solution with the GUI tab of the Services isnt a functional solution for us. While thesting this, at some point there is a system error 85: "The local device name is already in use". These Network drives arent even deletable with net use * /d. They still remain in windows explorer. Just a reboot seems to do it. Any other solutions to our problem? Best Regards, JFuchs

Hi there, our problem still exists, anyone an idea? best regards