I have two Samba 4.1.0 Domain Controllers at two physical locations connected via vpn, with one controller at each site so to help clients use the correct controller, I started setting multiple sites. If I move one server from the default site into a new site though (via the Microsoft Sites and Services Windows Tool), Samba's LDAP malfunctions until Samba is restarted. This can be tested with the command: "samba-tool drs options". I get "Failed to bind - LDAP client internal error: NT_STATUS_UNEXPECTED_NETWORK_ERROR". I haven't enabled debug logs yet, but I can if needed.
It looks like moving a server to another site with ldbrename also freezes the ldap part of samba4: ldbrename -U Administrator -H ldap://<samba4_servername> "CN=<samba4_servername>,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=<mydomain>,DC=ad" "CN=<samba4_servername>,CN=Servers,CN=<newsite>,CN=Sites,CN=Configuration,DC=<mydomain>,DC=ad"
Also had this issue december 2013 with 4.1.3. It was not possible to move an server to another site. Also it did not work to rename an site. If however an site and assigned subnet was created before an join, the new server went into the proper site.
I have the same issue on Samba version 4.1.5.
We use ZENTyal which has Samba build in.
I tried to attach a subnet and then try to move ... AD Sites & Services hangs. ...
(In reply to comment #3)
> I have the same issue on Samba version 4.1.5.
> We use ZENTyal which has Samba build in.
> I tried to attach a subnet and then try to move ... AD Sites & Services hangs.
The same issue on Samba version 4.1.6.
Any update on this issue... this bug is already a long time open...
I experience same behavior using Samba 4.1.7 on Ubuntu 12.04. Moving domain controller to site using Microsoft Active Directory Sites And Services cause Samba to freeze.
*** This bug has been marked as a duplicate of bug 10419 ***