Bug 4576 - Samba 3 cannot join AD domain over IPv6
Samba 3 cannot join AD domain over IPv6
Status: NEW
Product: Samba 4.0
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB
4.0.0
Other All
: P3 normal
: ---
Assigned To: Andrew Bartlett
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-28 10:11 UTC by David Holder
Modified: 2013-07-18 08:43 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Holder 2007-04-28 10:11:10 UTC
Samba 3 should be able to join a Longhorn based AD domain over IPv6. It cannot at present.

Test by installing Longhorn server. Configure Longhorn with a global IPv6 address. Then add the AD domain controller and DNS roles. 
Configure the Samba client with  a global IPv6 address. Configure Samba3 as normal for an AD client.
Next attempt to join the Longhorn domain using the Samba3 net command as normal. Samba 3 should join the domain over IPv6 in preference to IPv4, if IPv6 DNS records (AAAA) exist for the domain controller and if IPv6 transport is available. If either of these are not true then Samba3 should fall back to joining the domain over IPv4. This process should be invisible to the user.

Let me know if you need help testing or any further information.
Comment 1 Björn Jacke 2013-07-17 21:17:23 UTC
once bug 10030 is being fixed can you try again with Samba 4 and see how that works for you?
Comment 2 David Holder 2013-07-18 08:43:07 UTC
(In reply to comment #1)
Will do. As it turns out we did get Samba 3 to join AD domains over IPv6. Thanks for chasing updating this bug.