Bug 533028 - Samba 3.4 ADS support broken on ipv6
Summary: Samba 3.4 ADS support broken on ipv6
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-04 18:12 UTC by Pim Zandbergen
Modified: 2010-11-04 14:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-04 14:21:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Samba Project 6870 0 None None None Never

Description Pim Zandbergen 2009-11-04 18:12:45 UTC
Description of problem:
On and ipv4/ipv6 network, where the DNS server resolves hostnames both
to ipv4 and ipv6 addresses, Samba does not fall back to ipv4 if an ipv6
LDAP connection to a Windows Active Directory server fails.

ipv6 LDAP connections to Windows 2003 Servers fail with "connection
refused", because Windows 2003 Server supports ipv6, but its Active
Directory LDAP service does not.

Samba should retry the connection using ipv4 but does not.

This results in Samba being unable to find the logon server in a domain.


Version-Release number of selected component (if applicable):
samba-3.4.2-0.42.fc11.i586


How reproducible:
always


Steps to Reproduce:
1. Join a Samba 3.4 client to a Windows 2003 AD domain using ipv4
2. Enable ipv6 on Windows 2003 DC and Samba 3.4 member server
3. configure both A and AAAA records for the DC's hostname
4. net ads testjoin -S dc-hostname
  
Actual results:
2009/11/04 14:29:47,  0] utils/net_ads.c:279(ads_startup_int)
  ads_connect: No logon servers
Join to domain is not valid: No logon servers

Expected results:
Join is OK


Additional info:

Side effect of this problem is that winbind fails too, as can
be expected. However, winbind, when not stopped, will consume
all open file resources, effectively bringing the server down.

Removing the AAAA records for the DC's DNS hostname fixes all
these problem, leaving the DC impossible to find using ipv6.

Comment 1 Bug Zapper 2010-04-28 11:05:28 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Pim Zandbergen 2010-05-03 08:45:16 UTC
According to upstream's bugzilla, this issue is fixed in samba 3.5

It therefore remains a problem in Fedora 12, and will be fixed in Fedora 13.

Comment 3 Fedora Admin XMLRPC Client 2010-10-08 14:43:57 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Bug Zapper 2010-11-04 06:48:11 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Pim Zandbergen 2010-11-04 09:59:34 UTC
This issue has been fixed in Samba 3.5, which started shipping in Fedora 13.

Comment 6 Guenther Deschner 2010-11-04 14:21:05 UTC
Ok, can you then please upgrade to Fedora 13 (or 14) ? Closing as wontfix in Fedora 12.


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