[Samba] Samba 3 + Win2k = Headache
sjohnson at engr.psu.edu
Fri May 21 15:00:59 GMT 2004
Well, the ldap/AD part may be moot now... I got the cifs module inserted
into the kernel, but now I can't get anything to mount with it. I issue
mount -t smbfs //192.168.0.2/home /home/test -o username=test
It asks me for a password, I enter it, and it mounts... everything's
good. However, when I try:
mount -t cifs //192.168.0.2/home /home/test -o user=test (I've
also tried username=test)
It asks for a password, then gives me an error:
mount error 22 = Invalid argument
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
In the /var/log/messages (syslog), it says:
CIFS VFS: Error -32 sending data on socket to server.
CIFS VFS: cifs_mount failed w/return code = -5
I've also tried enabling the debug mode:
echo 1 > /proc/fs/cifs/cifsFYI
It doesn't give any more information. The server (again, Samba 3.0.5svn)
doesn't record anything in any logs, from what I can tell.
Does anybody have any idea what's going on and how to fix it?
Network Support Specialist / Systems Administrator
Dept. of Mechanical and Nuclear Engineering
224 Reber Building
University Park, PA 16802
Phone: (814) 865-8267
> -----Original Message-----
> From: tms3 [mailto:tms3 at fsklaw.net]
> Sent: Thursday, May 20, 2004 5:30 PM
> To: Paul Gienger
> Cc: Shannon Johnson; samba at lists.samba.org
> Subject: Re: [Samba] Samba 3 + Win2k = Headache
> Yep. And you can populate ADS with the ldap stuff, automatically, but
> only one way. From ldap to W2k. I've got an overview on this form
> University of Michigain, but at the office. On vacation till tuesday.
> Paul Gienger wrote:
> > Shannon Johnson wrote:
> >>> From what I can gather, you've got
> >>> 2003 AD doing user management
> >>> RHEL for a (home) fileserver
> >>> Clients of all flavors
> >>> Have you thoroughly investigated just using nfs and autofs to do
> >>> directory mounting and decided you can't use it for one reason or
> >>> another? What are those reasons? You'd probably have less
> >>> using nfs in a unix client - unix server environment, after all,
> >> that's
> >>> what NFS is good for.
> >> Win2000 server, not 2k3... but essentially correct. NFS won't work
> >> because since we're doing authentication through winbind, all of
> >> uid's are different on each linux client. We've tried loading the
> >> Services for Unix on the server, and assigning UID's, then using
> >> idmap_ad as the idmap backend, but I'm actually not sure how it
> >> so I can't thoroughly explore it (the documentation apparently
> >> exist?). The only thing I can check is "getent passwd" which
> >> UID winbind came up with on its own (through its own methods... not
> >> AD).
> > For that I would suggest using a central LDAP repository for your
> > idmap backend on all machines. If that's all you need to do to get
> > going with nfs, that's a not-too-tough situation to solve. You
> > have to go through the (somtimes painful) samba/ldap setup, you just
> > need a basic ldap server with one idmap tree in it. What are you
> > using for your unix auth now? since it sounds like you've got a few
> > unix machines, ldap is a good fit there too, unless you've got
> > something else that's tied in to your organization that you'd have
> > rebuild...
> >> Also, we are sharing files in a cross-platform environment... We
> >> to have the same file space, using the same quota for all of the
> >> in the department.
> > What is enforcing your quotas? 2K or unix machine?
> >> That's why Samba seemed like such a perfect fit.
> >> Windows maps the user's home directory from the Samba server via
> >> and the Linux users do the same. That's when the symbolic and hard
> >> problems come into play...
More information about the samba