[Samba] Re: Access Denied

[Sten Sletbak]

In article <200407270929.i6R9TjGU047721 at robertsonmann.com>, Bill Mann wrote:
> I enabled wins32 and put the line server =2.0 and it works!  Try it!
> 
> Bill Mann
> The Benefits Office
> 
> CONFIDENTIALITY NOTICE: This e-mail (including attachments), is covered by
> the Electronic Communications Privacy Act, §§ 2510-2521 and is confidential.
> The information contained in this message and the accompanying documents is
> confidential information that is legally privileged and intended only for
> the use of the above-named recipient. If the reader of this message is not
> the named recipient or an employee or agent responsible for delivering the
> telecopy to the named recipient, please notify us immediately to arrange for
> the return of the original documents to us. You are hereby notified that any
> review, disclosure, copying, distribution, or the taking of any action in
> reliance on the contents of this information is strictly prohibited. 
> 
> -----Original Message-----
> From: samba-bounces+bill=robertsonmann.com at lists.samba.org
> [mailto:samba-bounces+bill=robertsonmann.com at lists.samba.org] On Behalf Of
> Vermyndax
> Sent: Monday, July 26, 2004 12:42 AM
> To: samba at lists.samba.org
> Subject: Re: [Samba] Access Denied
> 
> Bill Mann wrote:
> 
> >> Samba 3.0.5 on Unix. I can map to the share but Access is denied. 
> I've configured the share so this would not happen.  Any ideas?
> 
> 
> This started happening to me as of 3.0.4, and I never found a solution.
>    Now I'm trying to mount via cifs, but getting "missing or invalid
> username" even though I'm using the correct credentials file.   :(
> 
> The last good version of Samba that worked for me was 3.0.2a.

Let me see if I understand you correctly.
After upgrading to samba 3.0.5, you get "Access denied" errors on your clients (XP?) when 
for example saving documents to the mapped drive?

This started to happen randomly on our XP-clients after Redhat's up2date updated samba from 
3.0.2-6.3E to 3.0.4-6.3E. Rolling back to 3.0.2-6.3E solved the problem.
I am having a hard time reproducing this on our test-servers, and I really don't want to try
it out again on the production-servers...

Could you please be more specific on your solution. Is it something on the client? smb.conf?

Thanks,

Sten Sletbak
Oslo University College