[linux-cifs-client] Re: CIFS not mounting Windows Shares (Adnan)

[Adnan]

Would I need a special mount.cifs and cifs.o for mandrake or 1.02 should
work???


"Steve French" <smfltc at us.ibm.com> wrote in message
news:1079972944.10968.21.camel at stevef95.austin.ibm.com...
>
> > Subject: [linux-cifs-client] CIFS not mounting Windows Shares
> > To: linux-cifs-client at lists.samba.org
> > Message-ID: <c3frcj$8ut$1 at sea.gmane.org>
> >
> > Hi all,
> >
> > It is very important for me to get CIFS VFS running on my system. I have
> > compiled CFS version 1.02b in the kernel (not as a module) using the
> > direction in the README. I have also compiled mount.cifs from the Samba
vers
> > 3.0.2rc2 source (version 1.0) and using it. I have also tried it with
the
> > mount.cifs that is on the website (version 1.1) . All gives me the same
> > result.
> >
> > When I mount either a Windows 2000 or Windows XP (home or professional
> > server) using the following command my mount command is
> >
> > mount -t cifs //192.168.1.35/e$ /mnt -o
> > user=administrator,password=Passw0rd01
> >
> > I get the message that
> >
> > mount error 22 = Invalid argument
> >
> > my /var/log/syslog gave me this message
> >
> > Mar 18 15:57:36 rv2400 kernel: CIFS VFS: Error -32 sending data on
socket to
> > server.
> >
> > Mar 18 15:57:36 rv2400 kernel: CIFS VFS: cifs_mount failed w/return code
> > = -5
> >
> > So I looked more into the documentation and enabled debug (change the
> >
> > contents of /proc/fs/cifs/cifsFYI to 1).
> >
> > And I using the same mount command above, I get the same message but the
> > message in /var/log/syslog is
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: CIFS VFS: in cifs_mount as
Xid: 4
> > with uid: 0 Mar 18 16:47:28 rv2400 kernel: connect.c: Username:
> > administrator
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: UNC: \\192.168.1.35\c$
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: Socket created
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: Demultiplex PID: 1394
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: tcp session abended
prematurely
> > (after SMBnegprot)
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: About to exit from demultiplex
> > thread
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: Existing smb sess not found
> >
> > Mar 18 16:47:28 rv2400 kernel: connect.c: CIFS VFS: leaving cifs_mount
(xid
> > = 4) rc = -2
> >
> > Mar 18 16:47:28 rv2400 kernel: CIFS VFS: cifs_mount failed w/return code
> > = -2
> >
> > My environment:
> >
> > Mandrake Linux 9.0
> >
> > Kernel version: 2.4.19-16mdksmp
> >
> > Using 3-ware SATA card with 1.3TB on the SATA drives
> >
> > Oh, the smbfs mounts the drives without any problem. The reason I am
using
> > CIFS is because of speed and it doesn't have 2GB file limit (as I have
been
> > told).
> >
> > Thanks a lot in advance
> >
> > Adnan
>
> The symptoms shown by your debug log entries match what happens when the
> cifs client attempts to mount older servers to Windows9x or Windows NT
> (prior to Windows 2000). I have not seen this happen to Windows 2000 or
> later but perhaps the servers will do if the list of allowed
> workstations is restricted through the Windows admin gui since without
> the rfc1001 session initialize a clients can not identify their
> (netbios) workstation name.   Older operating systems (such as NT4)
> which do not support "native TCP" require that the first frame sent be
> RFC1001 ("Netbios over TCP") netbios session initialize (before the SMB
> negotiate protocol request) which the cifs client does not sent.  This
> would not be too hard to add though.
>
> Other possible less likely reasons could be hitting a tcp session.  Let
> me know if you are restricting the hostnames/workstation names that can
> connect to your system since the symptom indicates that the server is
> taking down the tcp session before responding even to the first SMB
> request.