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

Adnan adnano at charter.net
Tue Mar 23 00:05:41 GMT 2004


Steve, hopefully this was the answer you were looking from me.  If not,
please let me know what more information I can provide.

Again, thanks in advance

Adnan

"Adnan" <adnano at charter.net> wrote in message
news:000401c4103a$ca4a6fc0$f901a8c0 at AdnanLaptop...
>
> Thanks Steve for the response.....
>
> I am trying to Connect to Windows 2000 Server, XP (home and
> Professional) and Windows 2003 Server. I checked the Local Security
> Settings of Windows XP Professional and it is not restricting any
> Workstations.  Also to verify that I connect to this XP machine.  I
> mounted a share of this machine using
> Smbclient (samba 3.0.2rc2) to my Linux machine (Mandrake 9.0).
> Moreover, I can also connect to this share using other Windows Machines
> from My Network Places.
>
> I have also run,
>
> Smbclient -L "192.168.1.35" -N and I see the list of machines that are
> registered to that Workgroup/Domain.
>
> Hope this additional information helps.
>
> Thanks
> Adnan
>
> -----Original Message-----
> From: Steve French [mailto:smfltc at us.ibm.com]
> Sent: Monday, March 22, 2004 10:29 AM
> To: linux-cifs-client at lists.samba.org
> Cc: adnano at charter.net
> Subject: CIFS not mounting Windows Shares (Adnan)
>
> <<<<<<< Snip Original Message >>>>>>>
>
> 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.





More information about the linux-cifs-client mailing list