RE: The SMBMOUNT plot thickens



Couple other things to consider:

Try specifying a domain with the username.

<domain>\\username or in fstab domain=<domain>

domain = domain name or computer name if you are not part of a domain

Unless you need some specific "cifs" functionality you could try using
"smbfs". I am using smbfs, but, there are some limitations, i.e., cannot
transfer a file larger than 2GB, etc...

Can you try setting permissions to 777 just to see if it would work? All
of our mounts are set to 777 and permissions to the files are managed
via windows acls.

BTW - I *think* the differences between the terms "(always), (if
possible), (if server agrees)" are probably due to different windows
versions/service packs.

-Steve

-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx
[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Darrel Barton
Sent: Wednesday, July 25, 2007 2:56 PM
To: redhat-list@xxxxxxxxxx
Subject: The SMBMOUNT plot thickens

OK - all suggestions taken and implemented.
Keep in mind (this is for Steve) I don't even HAVE the exact same
prompts
that you have.
Where YOU have
Microsoft network client - digitally sign communications (always) & (if
server agrees)
I have
network client - digitally sign communications (always) & (if possible)

=-=-=-=
Not that big a deal ... but the fact that differences like that exist
-for
no real reason- just frosts my windshield
=-=-=-=
Anyway .....

Double verified permissions and enabled all the logging and here's what
I get:

Event viewer shows a successful logon by my mount.cifs client
Event viewer shows a successful open of the target directory

Event viewer shows a successful READ of the target file ..... EVEN
THOUGH
LINUX gives me a "permission denied" error.
Samba logs on Linux show successful mount. Nothing else.





At 09:00 AM 7/25/2007, you wrote:

Message: 7
Date: Wed, 25 Jul 2007 09:20:41 -0400
From: "Kozakoff,Stephen J" <kozaksj@xxxxxxx>
Subject: RE: SMBmount conspiracy
To: "General Red Hat Linux discussion list" <redhat-list@xxxxxxxxxx>
Message-ID:

<D874258078AB854EAAD78C0F2196B9381A7EB4@xxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="US-ASCII"

I have the same setup - win2k3/RHEL ES4
My local security policy settings are like this:
In Local Security Settings navigate to:
Local Policies >> Local Policies >> Security Options

Microsoft network client - digitally sign communications (always) -
DISABLED
Microsoft network client - digitally sign communications (if server
agrees) - ENABLED
Microsoft network server - digitally sign communications (always) -
DISABLED
Microsoft network server - digitally sign communications (if server
agrees) - DISABLED

Turn on Auditing:
In Local Security Settings navigate to:
Local Policies >> Audit Policy
Set Audit Object Access == Failure

Next turn on auditing of Read events on the folder you are accessing.

Now you can check the Security event log to see if you can gleen why
access is being denied.

HTH.

-Steve


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.19/917 - Release Date:
7/25/2007 1:16 AM


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • The SMBMOUNT plot thickens
    ... Event viewer shows a successful logon by my mount.cifs client ... Microsoft network client - digitally sign communications - ... Microsoft network server - digitally sign communications - ...
    (RedHat)
  • Re: 2003 Server Unable to Map UNC Path
    ... How can I get server 1 to use a unc path to server 2? ... respond with that security level. ... Microsoft network client: Digitally sign communications ...
    (microsoft.public.windows.server.networking)
  • Re: USERENV error - Group Policy
    ... Microsoft network server: Digitally sign communications ... Microsoft network server: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clients not able to login to Domain
    ... Microsoft network client: Digitally sign communications - Disable ... Digitally sign communications (if server ...
    (microsoft.public.windows.server.sbs)
  • Re: nt4 domains (over vpn) cannot see windows 2003 domain in nethood
    ... Microsoft network server: Digitally sign communications ... computer in my 2003 domain EXCEPT the new Win2003 Server itself!! ... settings that are blocking access to the users from the other NT4 ...
    (microsoft.public.windows.server.migration)