Bug 238701 – mount.cifs fails with error message despite correct configuration.

Bug 238701 - mount.cifs fails with error message despite correct configuration.

Summary:	mount.cifs fails with error message despite correct configuration.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	samba (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Samba Maint Team
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-05-02 09:41 EDT by Carl Speare
Modified:	2007-11-16 20:14 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-09-12 10:21:44 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Carl Speare 2007-05-02 09:41:45 EDT

Description of problem:

Version-Release number of selected component (if applicable):
mount.cifs version: 1.5

How reproducible:
Always.

Steps to Reproduce:
1. mount.cifs //<cifs_server_name>/<cifs_share>
2. Verify mount failed with error message:

mount error 13 = Permission denied
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
12575: session setup failed: ERRSRV - 2242
SMB connection failed

3. Mount does not success, as verified from output of mount command.
  
Actual results:
Mount did not complete.


Expected results:
Mount should complete without error.

Additional info:

Please let us know what more is necessary to investigate this case. This mount 
works from an identically configured system without issue, which is also 
running RHEL 4.4.

Comment 1 Carl Speare 2007-05-02 10:24:15 EDT

Close this non-bug: the user account that was being used for the mount had an 
expired password. Once fixed, the mount succeeded without issue.

Thank you.

Note You need to log in before you can comment on or make changes to this bug.