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

[Neil Aggarwal]

Hello:

I have a Windows 2003 Small Business Server acting as the
primary domain controller in a network for a client.

In addition, I have a Windows 2000
server acting as a fileserver and as a backup domain
controller.

I just did a fresh install of Fedora Core 2 for a firewall
and routing machine.

I would like to mount one of the shares from the fileserver
to the Linux box, so I logged in as root and typed:
mount.cifs //192.168.1.2/GDrive /mnt/GDrive
-o user=[user],password=[pass],domain=[domain],ro
This is all on one line and the items in brackets []
are replaced with the appropriate values.

When I try this, I get:
mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

And these messages appear on the /var/log/messages file:
Oct 10 00:19:03 www kernel: CIFS VFS: Send error in SessSetup = -13
Oct 10 00:19:03 www kernel: CIFS VFS: cifs_mount failed w/return code = -13

I can mount this share on a windows machine with no problem.

I even tried it with the administrator account to no avail.

I checked the web and docs and I cant find anything to help.

I am pretty sure this is not a firewall problem.

Any ideas?

Thanks,
Neil

--
Neil Aggarwal, JAMM Consulting, [phone], 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

[Neil Aggarwal]

Hello:

Some follow-up information. I am able to communicate with the
file server using smbclient.

I tried this command:

smbclient -L 192.168.1.2 -U administrator
Password:

and entered the administrator password.

It gave me this output:

Domain=[HOMEXCORP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
GDrive Disk
NETLOGON Disk Logon server share
G$ Disk Default share
ADMIN$ Disk Remote Admin
SYSVOL Disk Logon server share
VPLOGON Disk Symantec AntiVirus
C$ Disk Default share
VPHOME Disk Symantec AntiVirus
session request to 192.168.1.2 failed (Called name not present)
session request to 192 failed (Called name not present)
Domain=[HOMEXCORP] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]

Server Comment
--------- -------
APOLLO
FILESERVER
STATIOND
STATIONF STATIONF
STATIONH
STATIONJ
STATIONL

Workgroup Master
--------- -------
HOMEXCORP APOLLO

But, if I try this command:
mount -t smbfs //192.168.1.2/Gdrive /mnt/GDrive -o user=administrator

I get this output:
cli_negprot: SMB signing is mandatory and we have disabled it.
5002: protocol negotiation failed
SMB connection failed

Any ideas?

Thanks,
Neil


--
Neil Aggarwal, JAMM Consulting, [phone], 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-----
org
s.samba.org] On Behalf Of Neil Aggarwal
Sent: Sunday, October 10, 2004 12:23 AM
Subject: [linux-cifs-client] Mounting CIFS gives me permission denied
I have a Windows 2003 Small Business Server acting as the
primary domain controller in a network for a client.
In addition, I have a Windows 2000
server acting as a fileserver and as a backup domain
controller.
I just did a fresh install of Fedora Core 2 for a firewall
and routing machine.
I would like to mount one of the shares from the fileserver
mount.cifs //192.168.1.2/GDrive /mnt/GDrive
-o user=[user],password=[pass],domain=[domain],ro
This is all on one line and the items in brackets []
are replaced with the appropriate values.
mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
Oct 10 00:19:03 www kernel: CIFS VFS: Send error in SessSetup = -13
Oct 10 00:19:03 www kernel: CIFS VFS: cifs_mount failed
w/return code = -13
I can mount this share on a windows machine with no problem.
I even tried it with the administrator account to no avail.
I checked the web and docs and I cant find anything to help.
I am pretty sure this is not a firewall problem.
Any ideas?
Thanks,
Neil
--
Neil Aggarwal, JAMM Consulting, [phone], 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
_______________________________________________
linux-cifs-client mailing list
http://lists.samba.org/mailman/listinfo/linux-cifs-client

[Steven French]

Post by Neil Aggarwal
mount error 13 = Permission denied

A few possbile causes come to mind
1) Obviously a bad user or password (from a windows box you can override
the user and password explicitly on NET USE or use smbclient as an
alternative to try a different client)
2) specifying a user who is configured to not allow authentication across
the network
3) specifying a domain (or using the default domain) which does not match
the servers domain
4) restricted host (windows allows you to configure workstations that are
not allowed to mount to a share)
5) windows is configured for mandatory use of ntlmv2 or kerberos security
(cifs support for ntlmv2 is not enabled in /proc/fs/cifs by default and
cifs kerberos support is not complete)



Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
-------------- next part --------------
HTML attachment scrubbed and removed

[Neil Aggarwal]

Steve:

Here is something strange:

When I do this command:
smbclient -L 192.168.1.2 -U na
It asks me for the password and then it gives
me a list of the shares on the machine.

But, when I do this command:
smbclient -L 192.168.1.2 -U na/HOMEXCORP
It asks for a password and then it gives me this
message:
session setup failed: NT_STATUS_LOGON_FAILURE

When I try either of these:
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na/HOMEXCORP
I get these error messages:
cli_negprot: SMB signing is mandatory and we have disabled it.
5889: protocol negotiation failed
SMB connection failed

When I try either of these:
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o user=na
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o user=na,domain=HOMEXCORP
It asks me for a password and I get these messages:
mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

Any ideas why the smbclient list works but smbmount and
mount.cifs do not?

Thanks,
Neil

--
Neil Aggarwal, JAMM Consulting, [phone], 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=***@lists.samba.org
[mailto:linux-cifs-client-bounces+neil=***@lists.samba.org]
On Behalf Of Steven French
Sent: Monday, October 11, 2004 1:30 PM
To: Neil Aggarwal; linux-cifs-***@lists.samba.org
Subject: Re: [linux-cifs-client] Mounting CIFS gives me permission denied

Post by Neil Aggarwal
mount error 13 = Permission denied

A few possbile causes come to mind
1) Obviously a bad user or password (from a windows box you can override the
user and password explicitly on NET USE or use smbclient as an alternative
to try a different client)
2) specifying a user who is configured to not allow authentication across
the network
3) specifying a domain (or using the default domain) which does not match
the servers domain
4) restricted host (windows allows you to configure workstations that are
not allowed to mount to a share)
5) windows is configured for mandatory use of ntlmv2 or kerberos security
(cifs support for ntlmv2 is not enabled in /proc/fs/cifs by default and cifs
kerberos support is not complete)



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

[James Philip Roper]

Maybe the user na doesn't have permission to mount GDrive? Also, if
your password is wrong, smbclient may fall back to anonymous, which may
have permission to list the shares, but not to mount GDrive. To find
out what is really happenning, an easy way is to fire up ethereal (or
tcpdump), and actually look at who smbclient is logging in as, and who
smbmount and mount.cifs are trying to log in as.

Have you checked that smb signing is turned on?
(/proc/fs/cifs/PacketSigningEnabled)

James

Post by Neil Aggarwal
smbclient -L 192.168.1.2 -U na
It asks me for the password and then it gives
me a list of the shares on the machine.
smbclient -L 192.168.1.2 -U na/HOMEXCORP
It asks for a password and then it gives me this
session setup failed: NT_STATUS_LOGON_FAILURE
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na/HOMEXCORP
cli_negprot: SMB signing is mandatory and we have disabled it.
5889: protocol negotiation failed
SMB connection failed
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o user=na
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o user=na,domain=HOMEXCORP
mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
Any ideas why the smbclient list works but smbmount and
mount.cifs do not?
Thanks,
Neil
--
Neil Aggarwal, JAMM Consulting, [phone], 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-----
On Behalf Of Steven French
Sent: Monday, October 11, 2004 1:30 PM
Subject: Re: [linux-cifs-client] Mounting CIFS gives me permission denied

Post by Neil Aggarwal
mount error 13 = Permission denied

A few possbile causes come to mind
1) Obviously a bad user or password (from a windows box you can override the
user and password explicitly on NET USE or use smbclient as an alternative
to try a different client)
2) specifying a user who is configured to not allow authentication across
the network
3) specifying a domain (or using the default domain) which does not match
the servers domain
4) restricted host (windows allows you to configure workstations that are
not allowed to mount to a share)
5) windows is configured for mandatory use of ntlmv2 or kerberos security
(cifs support for ntlmv2 is not enabled in /proc/fs/cifs by default and cifs
kerberos support is not complete)
Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
_______________________________________________
linux-cifs-client mailing list
http://lists.samba.org/mailman/listinfo/linux-cifs-client

[Neil Aggarwal]

James:

I tried it with administrator which does have permission to
mount the drive. I also tried the mount on a windows computer
and it worked fine. I don't think the user name and password
are the problem.

I tried tcpdump, but everything is happening on port 445, so
tcpdump is not decoding the packets. Is there a way to
use tcpdump for this?

/proc/fs/cifs/PacketSigningEnabled has a 1 in it already,
so that cant be the problem.

Thanks,
Neil


--
Neil Aggarwal, JAMM Consulting, [phone], 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-----
Sent: Monday, October 11, 2004 8:34 PM
Subject: Re: [linux-cifs-client] Mounting CIFS gives me
permission denied
Maybe the user na doesn't have permission to mount GDrive? Also, if
your password is wrong, smbclient may fall back to anonymous,
which may
have permission to list the shares, but not to mount GDrive. To find
out what is really happenning, an easy way is to fire up ethereal (or
tcpdump), and actually look at who smbclient is logging in
as, and who
smbmount and mount.cifs are trying to log in as.
Have you checked that smb signing is turned on?
(/proc/fs/cifs/PacketSigningEnabled)
James

Post by Neil Aggarwal
smbclient -L 192.168.1.2 -U na
It asks me for the password and then it gives
me a list of the shares on the machine.
smbclient -L 192.168.1.2 -U na/HOMEXCORP
It asks for a password and then it gives me this
session setup failed: NT_STATUS_LOGON_FAILURE
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na
smbmount //192.168.1.2/GDrive /mnt/GDrive -o user=na/HOMEXCORP
cli_negprot: SMB signing is mandatory and we have disabled it.
5889: protocol negotiation failed
SMB connection failed
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o user=na
mount.cifs //192.168.1.2/GDrive /mnt/GDrive -o

user=na,domain=HOMEXCORP

Post by Neil Aggarwal
mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
Any ideas why the smbclient list works but smbmount and
mount.cifs do not?
Thanks,
Neil
--
Neil Aggarwal, JAMM Consulting, [phone],

www.JAMMConsulting.com

Post by Neil Aggarwal
FREE! Valuable info on how your business can reduce

operating costs by

Post by Neil Aggarwal
17% or more in 6 months or less!

http://newsletter.JAMMConsulting.com

Post by Neil Aggarwal
-----Original Message-----

s.samba.org]

On Behalf Of Steven French
Sent: Monday, October 11, 2004 1:30 PM
Subject: Re: [linux-cifs-client] Mounting CIFS gives me permission denied

Post by Neil Aggarwal
mount error 13 = Permission denied

A few possbile causes come to mind
1) Obviously a bad user or password (from a windows box you can override

the

user and password explicitly on NET USE or use smbclient as an alternative
to try a different client)
2) specifying a user who is configured to not allow authentication across
the network
3) specifying a domain (or using the default domain) which does not match
the servers domain
4) restricted host (windows allows you to configure workstations that are
not allowed to mount to a share)
5) windows is configured for mandatory use of ntlmv2 or kerberos security
(cifs support for ntlmv2 is not enabled in /proc/fs/cifs by default and

cifs

kerberos support is not complete)
Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
_______________________________________________
linux-cifs-client mailing list
http://lists.samba.org/mailman/listinfo/linux-cifs-client

[Steven French]

Some explanations as to what is going on.

1) smbclient -L (without specifying the domain) works because smbclient
supports signing as well as both kerberos and ntlmv2 and the default
domain is good enough
2) "smbclient -L 192.168.1.2 -U na/HOMEXCORP" fails (probably) because
your domain name and user name are backwards in the -U
3) smbmount (smbfs) fails because it doesn't implement signing (which is
one of the reasons that I wrote cifs vfs in the first place, to add to the
kernel, enough code to do security functions such as signing, rather than
relying on userspace smb client libraries which are awkward to get at when
processing every frame)
4) mount -t cifs probably fails because the server is configured so that
either
a) Kerberos is required (CIFS SPNEGO implementation is not
complete so can not handle
kerberized session setup - yet)
or
b) NTLMv2 is required (CIFS support for NTLMv2 is turned off by
default in /proc/fs/cifs/
because AFAIK it is not well tested)
or
c) plaintext paswords or old lanman password hashes are required
(these are too insecure - and
the cifs vfs will refuse to negotiate them)
or
d) your client's hostname (but not the ip address) is explicitly
allowed in the workstations
allowed list on the server but the cifs vfs does not send the
client's netbios name unless
you connect via the older netbios-over-tcp port 139 (and
"netbiosname=workstation_name"
was not passed over -o on the client mount).
or
e) that share can only be mounted by administrators not by the
user that you tried

We might be able to rule out 4b (NTLMv2 required) if extended security
were enabled in /proc but this will only work to WindowsXP and 2000
clients - or servers not in a domain - since they will then negotiate "raw
ntlmssp" which cifs does support rather than spnego which it does not).

In any case tracing on port 445 and 139 is quite similar and it does not
much matter which end you trace on there are similar tools available on
each.

Also note that if this is a windows server they have an audit or security
event log (I forget what it is called) which may tell you what is going on
- see System Tools -> Event Viewer -> Security on the server if it is a
windows server - obviously with Samba you have more detailed info you can
get by looking at log.smbd

Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
-------------- next part --------------
HTML attachment scrubbed and removed

[Neil Aggarwal]

Steve:

Thank you for your help so far.

Regarding 2), I switched the -U to HOMEXCORP/na and it worked fine.

Regarding 4), I took a look at the event log on the windows server, and
here is what I am seeing when I get a login failure:
Logon Failure:
Reason: Unknown user name or bad password
User Name: na
Domain: HOMEXCORP
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: \\192.168.1.1

It looks like the windows server is getting the correct user
name and domain name, but the workstation name is the IP
address of the Linux box. I wonder if that is the problem.

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
not a computer in the active directory. I think this may be
the problem. How do I get the computer to use linux as the
workstation name?

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

Thanks,
Neil

--
Neil Aggarwal, JAMM Consulting, [phone], 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=***@lists.samba.org
[mailto:linux-cifs-client-bounces+neil=***@lists.samba.org]
On Behalf Of Steven French
Sent: Tuesday, October 12, 2004 5:09 PM
To: Neil Aggarwal
Cc: linux-cifs-***@lists.samba.org
Subject: RE: [linux-cifs-client] Mounting CIFS gives me permission denied



Some explanations as to what is going on.

1) smbclient -L (without specifying the domain) works because smbclient
supports signing as well as both kerberos and ntlmv2 and the default domain
is good enough
2) "smbclient -L 192.168.1.2 -U na/HOMEXCORP" fails (probably) because your
domain name and user name are backwards in the -U
3) smbmount (smbfs) fails because it doesn't implement signing (which is one
of the reasons that I wrote cifs vfs in the first place, to add to the
kernel, enough code to do security functions such as signing, rather than
relying on userspace smb client libraries which are awkward to get at when
processing every frame)
4) mount -t cifs probably fails because the server is configured so that
either
a) Kerberos is required (CIFS SPNEGO implementation is not complete
so can not handle
kerberized session setup - yet)
or
b) NTLMv2 is required (CIFS support for NTLMv2 is turned off by
default in /proc/fs/cifs/
because AFAIK it is not well tested)
or
c) plaintext paswords or old lanman password hashes are required
(these are too insecure - and
the cifs vfs will refuse to negotiate them)
or
d) your client's hostname (but not the ip address) is explicitly
allowed in the workstations
allowed list on the server but the cifs vfs does not send the
client's netbios name unless
you connect via the older netbios-over-tcp port 139 (and
"netbiosname=workstation_name"
was not passed over -o on the client mount).
or
e) that share can only be mounted by administrators not by the user
that you tried

We might be able to rule out 4b (NTLMv2 required) if extended security were
enabled in /proc but this will only work to WindowsXP and 2000 clients - or
servers not in a domain - since they will then negotiate "raw ntlmssp" which
cifs does support rather than spnego which it does not).

In any case tracing on port 445 and 139 is quite similar and it does not
much matter which end you trace on there are similar tools available on
each.

Also note that if this is a windows server they have an audit or security
event log (I forget what it is called) which may tell you what is going on -
see System Tools -> Event Viewer -> Security on the server if it is a
windows server - obviously with Samba you have more detailed info you can
get by looking at log.smbd

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

[Steven French]

Post by Neil Aggarwal
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

Post by Neil Aggarwal
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: [phone]
email: sfrench at-sign us dot ibm dot com
-------------- next part --------------
HTML attachment scrubbed and removed

[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, [phone], 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=***@lists.samba.org
[mailto:linux-cifs-client-bounces+neil=***@lists.samba.org]
On Behalf Of Steven French
Sent: Wednesday, October 13, 2004 6:00 PM
To: Neil Aggarwal
Cc: linux-cifs-***@lists.samba.org
Subject: RE: [linux-cifs-client] Mounting CIFS gives me permission denied

Post by Neil Aggarwal
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

Post by Neil Aggarwal
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: [phone]
email: sfrench at-sign us dot ibm dot com

[Steven French]

The host is down error would normally indicate that the server is not
listening on that port or that it is blocked.


Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
-------------- next part --------------
HTML attachment scrubbed and removed

[Neil Aggarwal]

Steve:

I think port 139 is up an operational on the fileserver.

When I do:
telnet 192.168.1.2 139

I get this response:
Trying 192.168.1.2...
Connected to 192.168.1.2.
Escape character is '^]'.

Why would mount.cifs think the server is down?

Thanks
Neil


--
Neil Aggarwal, JAMM Consulting, [phone], 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=***@lists.samba.org
[mailto:linux-cifs-client-bounces+neil=***@lists.samba.org]
On Behalf Of Steven French
Sent: Wednesday, October 13, 2004 7:58 PM
To: Neil Aggarwal
Cc: linux-cifs-***@lists.samba.org
Subject: RE: [linux-cifs-client] Mounting CIFS gives me permission denied



The host is down error would normally indicate that the server is not
listening on that port or that it is blocked.


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

[Steven French]

Can you get a tcpdump or ethereal trace of the mount and send the binary
trace file?


Steve French
Senior Software Engineer
Linux Technology Center - IBM Austin
phone: [phone]
email: sfrench at-sign us dot ibm dot com
-------------- next part --------------
HTML attachment scrubbed and removed

[Reinhold Jordan]

Hi,

Post by Steven French
Can you get a tcpdump or ethereal trace of the mount and send the binary
trace file?

I have the same problem and wait for the answer

so this is, what I do
mount.cifs //ASC-FS1/Vol1 /mnt/asc_R -o user=JordaRe1%xxxxx
and on other teminal
tcpdump -vv > tcpdump-vv.log
and hope, this is, what you ask for...

Regards, Reinhold
--
ASC telecom AG Research & Development
Seibelstr. 2 F: [phone]
D-63768 H?sbach E: ***@asc.de
Visit us on http://www.asctelecom.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tcpdump-vv.log
Type: text/x-log
Size: 4565 bytes
Desc: not available
Url : http://lists.samba.org/archive/linux-cifs-client/attachments/20041021/25d604c6/tcpdump-vv.bin

[Reinhold Jordan]

Hi,

why this mail didn't appear in the list?

Post by Steven French
Can you get a tcpdump or ethereal trace of the mount and send the binary
trace file?

I have the same problem and wait for the answer

so this is, what I do
mount.cifs //ASC-FS1/Vol1 /mnt/asc_R -o user=JordaRe1%xxxxx
and on other teminal
tcpdump -vv > tcpdump-vv.log
and hope, this is, what you ask for...

Regards, Reinhold
--
ASC telecom AG Research & Development
Seibelstr. 2 F: [phone]
D-63768 H?sbach E: ***@asc.de
Visit us on http://www.asctelecom.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tcpdump-vv.log
Type: text/x-log
Size: 4566 bytes
Desc: not available
Url : http://lists.samba.org/archive/linux-cifs-client/attachments/20041026/c598ce0b/tcpdump-vv.bin

[Neil Aggarwal]

Steve:

It has been a while since I sent you the tcpdump.
Any progress?

Is there anything that I can do to help you?
I would like to get this problem resolved.

Thanks,
Neil


--
Neil Aggarwal, JAMM Consulting, [phone], 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
<http://newsletter.jammconsulting.com/>


-----Original Message-----
From: linux-cifs-client-bounces+neil=***@lists.samba.org
[mailto:linux-cifs-client-bounces+neil=***@lists.samba.org]
On Behalf Of Steven French
Sent: Sunday, October 17, 2004 9:48 PM
To: Neil Aggarwal
Cc: linux-cifs-***@lists.samba.org
Subject: RE: [linux-cifs-client] Mounting CIFS gives me permission denied



Can you get a tcpdump or ethereal trace of the mount and send the binary
trace file?


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

-------------- next part --------------
HTML attachment scrubbed and removed