Bug 15781 - RODC and remote Widows client behavior with RWDC initial replication partner offline
Summary: RODC and remote Widows client behavior with RWDC initial replication partner ...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: x64 Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-13 17:30 UTC by Enrico Manzini
Modified: 2025-01-13 17:30 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico Manzini 2025-01-13 17:30:44 UTC
samba-bugzilla support good evening,

We have a big customer, with a samba active directory infrastructure composed of an hub and spoke configuration with a central site and 80 remote sites
The main site contain 4 debian 10 and samba 4.18 rwdc
Each remote site contain 1 debian 10 and samba 4.18 rodc

We reproduce the customer main configuration, in laboratory, with the following configuration
The main site that contain 2 debian 12 and samba 4.21 rwdc
1 remote site that contain 1 debian 12 and samba 4.21 rodc
1 windows 10 client connected to the remote site and configured to use the rodc server as dns
Server’s DNS correcly configured
replica is working correctly
Sites and Services in Active Directory correctly configured, with 1 “main site” and 1 “remote site”, with correct subnet association
Windows 10 correcly bind the rodc as logon server through the command nltest /dsgetdc.domain_name

Expected (correct) behavior:
- we joined the rodc to the domain (both explicitly use one of the 2 rwdc in the central site, both leave the rodc find the rwdc themself)
                - replica from the rwdcs to the rodc correctly occurs
                - If we put offline the others rwdc, everything work
- we logon to the windows 10 remote client
                - client can browse the network in single sign on correctly

Actual (incorrect) behavior
- we put offline the rwdc used as intial replication partner during the rodc join
                - replica from the other’s rwdc to rodc does not works anymore
                - windows 10 client cannot browse the network (the system require the input of credential, that does not work)

I also contacted the samba mailing list, and they suggested me to open a bug report

ADDITIONAL INFORMATION:
- We build a specular windows based configuration, and the problem doesn't show up
- We configure a remote rwdc instead of an rodc, and the problem doesn't show up

Regards