smbmount //nt/e /mnt -o username=admin,password=secret
smbmount //nt/e /mnt -o username=admin,password=secret,ip=N.N.N.N
fails as described below.
Note! smbclient WORKS with these machine/username/pass!
I conclude it is a smbfs or smbmount problem, not a badly/unusually configured
NT or network problem. Also note that log messages are spewed by smbfs kernel
Tried to mount to locally running Samba:
smbmount //linuxbox/in /mnt -o username=guest,password=
How I can help to investigate this problem?
Please CC me. I'm not on the list.
JS> On Wednesday 15 August 2001 11:56 am, VDA wrote:
>> I'm having trouble mounting SMB shares residing on a WinNT machine.
>> smbclient works fine, but after mounting the same share with the
>> same username,passwd etc with smbmount and trying to enter
>> newly mounted dir I see repeating msgs in the logs:
>> smb_catch_keepalive: already done [<- this is KERN_ERR!]
>> smb_retry: successful, new pid=PID, generation=N [PID is the same, N grows
>> (N++)] smb_dont_catch_keepalive: server->data_ready == NULL
>> smb_trans2_request: result=-22, setting invalid
>> smb_close_socket: still catching keepalives!
>> smb_catch_keepalive: already done
>> smb_retry: successful, new pid=PID, generation=N+1
>> Since smbclient is working I presume it is a kernel smbfs bug or some
>> version mismatch between kernel and smbmount.
>> smbmount: 2.2.0a
>> kernel: 2.4.5
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/