[Samba] Problem with network drives
vlamsdoem at gmail.com
Tue Oct 16 07:07:15 GMT 2007
Thanks for the tip, it's working ;). The reason why I need to access to
another share is that when I go to the computer of some people from my work
for installing some software, I need to access a share that's not accessible
for the user. The user has the most of the time some network drives mapped
on his computer with his own login and password.
2007/10/15, Dennis McLeod <dmcleod at foranyauto.com>:
> -----Original Message-----
> From: samba-bounces+dmcleod=foranyauto.com at lists.samba.org
> [mailto:samba-bounces+dmcleod=foranyauto.com at lists.samba.org] On Behalf Of
> Vincent Zakofski
> Sent: Sunday, October 14, 2007 11:22 PM
> To: samba at lists.samba.org
> Subject: [Samba] Problem with network drives
> I have a Windows Xp station where a network drive is mapped. The username
> and password for this network drive are the same as those of my Windows
> I want to access to another share on this server with another name and
> than those of the mapped network drive. When I try to access to this share
> it tries with the username and password from my Windows session. I can see
> it in the samba log file ( NT_STATUS_NETWORK_ACCESS_DENIED).
> It doesn't work because this share is not accessible for my user. When I
> to log with a valid username and login for this share it doesn't work and
> have nothing in the samba log file.
> This share is accessible with another username and login when I dont have
> network drives mappped on the same samba server.
> Can somebody explain me why it doesn't work and why I don't see anything
> my log file.
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
> It's not a problem, and I don't think it's a Samba issue. It's a function
> XP/2000/2003. This would happen on a Windows Network too.
> "Multiple connections to a server or shared resource by the same user
> more than one user name are not allowed."
> That's the reason. I'm not enough of a Samba guru to tell you why it's not
> in your logs. It may show up in your XP event logs, depending on your XP
> Event log settings, though.
> You can make the second connection to the server using its IP address (I.E
> \\192.168.1.10\share) as a work around.
> Why would you want to connect as someone else, though, rather than give
> yourself (actually a group you belong to) access to the share?
> If it's just for testing, then the method above will be fine....
More information about the samba