Bug 436441

Summary:	Samba couldn't resolve alternativ DFS sources
Product:	Red Hat Enterprise Linux 5	Reporter:	Falko Pilz <falko.pilz>
Component:	samba	Assignee:	Simo Sorce <ssorce>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	5.0	CC:	gdeschner, jplans
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-12 15:15:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Falko Pilz 2008-03-07 07:43:59 UTC

Description of problem:
I use the following symbolic link:
data -> msdfs:server1\data,server2\data,server3\data
the samba couldn't split the DFS alternatives and it seems it sends
the whole target of the Link to the Clients

Version-Release number of selected component (if applicable):
3.0.23c-2

How reproducible:
use my link on a dfs-enabled Samba

Steps to Reproduce:
1.let XP show the DFS-Properties
  
Actual results:
with samba 3.0.23c this was send to XP as 3 alternatives:
1'st: \\server1\data\server2\data\server3\data
2'nd: \\server2\data\server3\data
3'rd: \\server3\data
and XP wasn't able to access the share.

Expected results:
with samba 3.0.26a-35 (sernet.de) this was send to XP as DFS alternatives:
1'st: \\server1\data
2'nd: \\server2\data
3'rd: \\server3\data
And XP can access the share.

Additional info:
I made every thing as shown in the howto for samba DFS.

Comment 1 Simo Sorce 2008-03-07 13:55:08 UTC

The latest package is 3.0.25b released with Upodate1, can you check with that first?

Comment 2 Simo Sorce 2008-07-12 15:15:41 UTC

No answer after many months I assume the problem is fixed in the current relase.
closing.