[linux-cifs-client] Mounting CIFS gives me permission denied

[Neil Aggarwal]

Steve:

I think we are getting somewhere.  I changed my command to
     mount.cifs //192.168.1.2/GDrive /mnt/GDrive 
        -o
user=na,password=[pass],domain=HOMEXCORP,netbiosname=linux,port=139

I now get this error:

mount error 112 = Host is down
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

Which is strange since I know the host is up.  I can ping it.

I don't see anyting in the event log on the windows machine.

Any ideas?

Thanks,
	Neil


--
Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com
FREE! Valuable info on how your business can reduce operating costs by
17% or more in 6 months or less! http://newsletter.JAMMConsulting.com

-----Original Message-----
From: linux-cifs-client-bounces+neil=jammconsulting.com at lists.samba.org
[mailto:linux-cifs-client-bounces+neil=jammconsulting.com at lists.samba.org]
On Behalf Of Steven French
Sent: Wednesday, October 13, 2004 6:00 PM
To: Neil Aggarwal
Cc: linux-cifs-client at lists.samba.org
Subject: RE: [linux-cifs-client] Mounting CIFS gives me permission denied



> When I tried the mount with this:
>         mount.cifs //192.168.1.2/GDrive /mnt/GDrive 
>                  -o "user=na,domain=HOMEXCORP,netbios name=linux"
>
> I still get the Workstation Name as \\192.168.1.1 which is
The parm netbiosname is one word, not two (no space) and the netbiosname
does not matter if netbios-over-tcp (RFC1001) is not being used.  To use
netbiosname you should force port 139 by adding 
        port=139 
in the options list (also you probably don't want to use quotes " after -o) 
                  -o user=na,domain=HOMEXCORP,netbiosname=linux,port=139 

>Also, when I did:
>                 echo 1 > ExtendedSecurity 
> in the /proc/fs/cifs directory, I get a segmentation fault when
> Is that a problem? 

Yes, although I am not sure which versions it is broken on because the code
is not complete - and we know it is broken if the server does not negotiate
"raw ntlmssp" (which are server in active directory will not negotiate).  So
it is good it ExtendedSecurity is forced off by default in proc until
someone has time to test/debug through it. 


Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: 512-838-2294
email: sfrench at-sign us dot ibm dot com