Merge ~ahasenack/ubuntu/+source/samba:focal-samba-win-22h2-fixes into ubuntu/+source/samba:ubuntu/focal-devel
Status: | Merged |
---|---|
Approved by: | git-ubuntu bot |
Approved revision: | not available |
Merge reported by: | Andreas Hasenack |
Merged at revision: | ee10ad894df86d5cd2dd301c43f358d2f7c42903 |
Proposed branch: | ~ahasenack/ubuntu/+source/samba:focal-samba-win-22h2-fixes |
Merge into: | ubuntu/+source/samba:ubuntu/focal-devel |
Diff against target: |
324 lines (+302/-0) 3 files modified
debian/changelog (+7/-0) debian/patches/series (+1/-0) debian/patches/win-22H2-fix.patch (+294/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
git-ubuntu bot | Approve | ||
Lucas Kanashiro (community) | Approve | ||
Canonical Server Reporter | Pending | ||
Review via email: mp+432767@code.staging.launchpad.net |
Description of the change
Fix for Windows 11 22H2 failing to join a Samba AD DC domain. The linked SRU bug has a test plan and more details on the bug.
If you want to follow that test plan, we have the necessary VM created on diglett. You can point virt-manager at qemu+ssh:
- win11H22: the Windows 11 22H22 VM that shows the bug. Creds: ubuntu_
Note that after joining the domain, RDP access is cut off. You have to login as Administrator and allow the "Domain Users" group to use RDP. I didn't find a way to allow this from the samba AD DC, but didn't search really hard.
Ubuntu VMs, where you can (re)install samba packages at will. They are pointing at my PPA with the fix, so if you want to see the bug, you have to downgrade them to the non-ppa version. These all can be logged in via the virt-manager console, creds ubuntu/ubuntu, and from there you can ssh-import your key.
- ad: jammy AD. Fixed IP at 10.0.18.5
- b-ad: bionic AD. Fixed IP at 10.0.18.3
- f-ad: focal AD. Fixed IP at 10.0.18.2
Libvirt network: 10.0.18.0/24
If you want, we can have a hangout where I can show all of this.
PPA: https:/
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
I did not test the feature itself but I see you got some good feedback on the bug. The packaging changes LGTM.