I already posted this in smb-clients, but seeing the load difference
I repost in the samba list.

I am currently using samba 3.0.10 with kernel 2.6.9.

In the doc one is encouraged to use 'security = user' level.
If I then connect with 'smbclient //machine/share -U myname%mypass' all works
well. But when I try to mount the share localy with

smbmount //machine/share mountpoint -o "username=myname,password=mypass"


smbmount => not made here, please go talk to the kernel boys
mount -t cifs often works better than mount -t smbfs. Give that a try and then go talk to the kernel boys if it's still broken.



The result is that the connection is refused, allthough mount shows the share
mounted. In the logfiles it seems that in the first logon the right username password combination is used and accepted by samba, but when the mount should happen I see BAD SIG in the logfile and the connection is broken by samba.


Is this a known problem? And if so, what is the solution?

Greetings, Peter.



-- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: [EMAIL PROTECTED]



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

Reply via email to