Re: [Samba] Mapped drive behaviour after Windows reboot

2010-05-24 Thread Graham Keeling
On Fri, May 21, 2010 at 03:16:00PM +0100, Graham Keeling wrote:
 Hello,
 
 I was previously using samba-3.3.3 on my linux machine.
 
 I could 'map a drive' from a Windows XP machine to access files on the linux
 machine.
 
 If I rebooted the Windows machine, and tried to access the share again by
 clicking on the mapped drive icon, I would be denied, but I would be given a
 prompt in which to type in a username and password.
 
 The samba log.clients on the linux machine would say this when I tried to
 access the mapped drive:
 smbd/service.c:make_connection_snum(740)
   create_connection_server_info failed: NT_STATUS_WRONG_PASSWORD
 
 
 
 I've updated to samba-3.4.8. On a reboot now, I am also denied, but I am not
 given username/password prompt.
 Instead I get a box that says this:
 
 An error occurred while reconnecting Z: to \\192.168.100.121\admin
 Microsoft Windows Network : More data is available
 The connection has not been restored
 OK
 
 The samba log.clients on the linux machine says this for each time I try to
 access the mapped drive:
 smbd/service.c:646(make_connection_snum)
   create_connection_server_info failed: NT_STATUS_WRONG_PASSWORD
 
 
 So, it looks like I am getting blocked for the same reason in both cases, but
 subsequently, the old behaviour of letting me type a username/password in
 made life a lot easier.
 
 Can anybody advise on how to get the old behaviour back with the new samba,
 or is this a bug for which I need to file a bug report somewhere?


Hmm.
I've just tried samba-3.5.3, and it is has reverted to the 3.3.3 behaviour
of allowing me the chance to type in a username and password.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba


[Samba] Mapped drive behaviour after Windows reboot

2010-05-21 Thread Graham Keeling
Hello,

I was previously using samba-3.3.3 on my linux machine.

I could 'map a drive' from a Windows XP machine to access files on the linux
machine.

If I rebooted the Windows machine, and tried to access the share again by
clicking on the mapped drive icon, I would be denied, but I would be given a
prompt in which to type in a username and password.

The samba log.clients on the linux machine would say this when I tried to
access the mapped drive:
smbd/service.c:make_connection_snum(740)
  create_connection_server_info failed: NT_STATUS_WRONG_PASSWORD



I've updated to samba-3.4.8. On a reboot now, I am also denied, but I am not
given username/password prompt.
Instead I get a box that says this:

An error occurred while reconnecting Z: to \\192.168.100.121\admin
Microsoft Windows Network : More data is available
The connection has not been restored
OK

The samba log.clients on the linux machine says this for each time I try to
access the mapped drive:
smbd/service.c:646(make_connection_snum)
  create_connection_server_info failed: NT_STATUS_WRONG_PASSWORD


So, it looks like I am getting blocked for the same reason in both cases, but
subsequently, the old behaviour of letting me type a username/password in
made life a lot easier.

Can anybody advise on how to get the old behaviour back with the new samba,
or is this a bug for which I need to file a bug report somewhere?

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba