Dear All Is it possible to mount a share hosted on a Windows 2003 box, that exists in an AD domain, on linux client. I can connect to the same share using SMBClient but cannot mount the share using mount -t smbfs. I have read on the forum that there are problems but couldn't determine if it was possible or not. If some one could clarify for me if this is possible or not I'd be grateful (I can then either stop wasting my time or figure out what the problem is). Thanks Paul ------------------------------------------------------------------- This email and any attachments transmitted with it are confidential (and potentially legally privileged) and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and do not store, copy or disclose the content to any other person. It is the responsibility of the recipient to ensure that opening this message and/or any of its attachments will not adversely affect its systems. No responsibility is accepted by the sender. -------------------------------------------------------------------
I have the same here. As I know it is a problem with digitally signed connections which isn't supported by samba. I don't know if it works with version up to 3.0.14a-r2, but with this version it won't do a smbmount of windows shares. Rogers, Paul schrieb:> Dear All > > Is it possible to mount a share hosted on a Windows 2003 box, that > exists in an AD domain, on linux client. I can connect to the same > share using SMBClient but cannot mount the share using mount -t smbfs. > I have read on the forum that there are problems but couldn't determine > if it was possible or not. > > If some one could clarify for me if this is possible or not I'd be > grateful (I can then either stop wasting my time or figure out what the > problem is). > > Thanks > > Paul > > ------------------------------------------------------------------- > This email and any attachments transmitted with it are confidential (and potentially legally privileged) and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and do not store, copy or disclose the content to any other person. > It is the responsibility of the recipient to ensure that opening this message and/or any of its attachments will not adversely affect its systems. No responsibility is accepted by the sender. > ------------------------------------------------------------------- > >
Markus/Filip Thanks for the responses. Markus Where did you find the info regarding "it is a problem with digitally signed connections which isn't supported by samba". It would be nice to know exactly what the problem was. Is it a problem with SAMBA or with W2k3, I wonder? Is it something that is fixable or will it always be broken? Does any one else know? Filip When you fixed it using CIFS was the client Linux and the host a W2k3 DC using AD/kerberos etc. Once agin thanks for the response. Paul Hi, I have posted the same question to the smb clients list but got no answer. Basically, smbfs is pretty much unsupported. I eventually upgraded to a 2.6 kernel and used cifs instead of smbfs. Worked without any problems. Here's a copy of my original mail & followup: http://archive.netbsd.se/?ml=smb-clients&a=2005-10&t=1348952 I would still be interested in knowing what exactly is causing the problem, since I have seen smbfs work with 2003 machines... Is it a domain controller vs. non-domain controller thing ? Regards, Filip -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba ------------------------------------------------------------------- This email and any attachments transmitted with it are confidential (and potentially legally privileged) and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and do not store, copy or disclose the content to any other person. It is the responsibility of the recipient to ensure that opening this message and/or any of its attachments will not adversely affect its systems. No responsibility is accepted by the sender. -------------------------------------------------------------------