Bug 235970 – Upgrade to samba-3.0.24-4.fc6 breaks Samba

Bug 235970 - Upgrade to samba-3.0.24-4.fc6 breaks Samba

Summary:	Upgrade to samba-3.0.24-4.fc6 breaks Samba

Status:	CLOSED DUPLICATE of bug 235821

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	samba (Show other bugs)
Sub Component:
Version:	6
Hardware:	x86_64 Linux

Priority	medium Severity urgent
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-04-11 01:50 EDT by Bill Woessner
Modified:	2007-11-30 17:12 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-04-11 09:13:15 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 Bill Woessner 2007-04-11 01:50:11 EDT

Description of problem:
After running 'yum update', I found that Samba no longer works.  Specifically, I
can no longer connect to my FC6 server from any of my Windows XP clients.  I am
still able to connect from other Linux clients.

Version-Release number of selected component (if applicable):
samba-3.0.24-4.fc6

How reproducible:
Simply upgrade to samba-3.0.24-4.fc6 and then try to connect from a Windows XP
machine.

I was able to fix the problem by reverting back to samba-3.0.24-3.fc6.

Comment 1 Paul Howarth 2007-04-11 02:53:42 EDT

Same symptoms here (connect OK from linux client using mount.cifs, can't connect
from VMWare guest running XP). When I say "can't connect", the samba log
indicates that a connection was created as the correct user and then closed, and
the XP client says that no connection could be made.

Comment 2 Paul Howarth 2007-04-11 03:45:19 EDT

OK, this seems to be a duplicate of Bug #235821 and rebooting the XP client
fixes the problem.

Given that this is a known issue, it would have been nice to have had some
mention of this is the package changelog and/or package announcement.

Comment 3 Simo Sorce 2007-04-11 09:13:15 EDT


*** This bug has been marked as a duplicate of 235821 ***

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