similar to: cannot compile 4-8-stable or 4-8-test

When Samba joins to AD, net creates 'Computer' object in target AD. Object 'Computer' has attributes operatingSystem and operatingSystemVersion, which automatically setup in properly value, when native Windows join to AD. I offer a patch to utils/net_ads.c to do similar way - set up operatingSystem to "Samba" and operatingSystemVersion to Samba version, when Samba

Hi List, We have a problem in connecting ADS server from SAMBA. Whenever we try to contact the ADS server from the Samba its giving error as LDAP_NO_RESULTS_RETURNED. We have varified the code also, in the code also its giving three possibilities to raise that error message, I am pasting the portion of code here, File name: libads/ldap.c Function name: ads_server_info Code snippet

Ok, I've analyzed this and found that the cause is a call to getpwuid(uid) with the uid being that of the domain controller. "wbinfo --uid-info=3000074" works and returns information, but this library function fails. This is then propagated upwards as a memory error, because it is being called from getpwuid_alloc() which is a talloc variant. the api doesn't allow us to

Well, I had a look at the python bindings and the error handling was in shambles. I fixed libgpo/pygpo.c and I now get: gpos = ads.get_gpo_list(creds.get_username()) SystemError: Failed to get machine token for 'DC01$' (CN=DC01,OU=Domain Controllers,DC=rvx,DC=is) (the failing call is status = gp_get_machine_token(self->ads_ptr, frame, dn,

On 13/03/2023 17:05, David Mulder via samba wrote: > > On 3/13/23 10:54 AM, Rowland Penny via samba wrote: >> Glad it isn't just myself having problems understanding that code, it >> is horrible :-D >> >> If it is a machine, why is it trying to look up a uid ? I traced where >> the error message is coming from, but couldn't understand what was

Hello, there is an error when building samba with current "samba-4.0.0alpha17" shipped with the sogo/openchange source. The error message is shown below. "‘struct registry_value’ has no member named ‘type’" is caused by gpo_reg.c in "samba4/source3/libgpo/gpo_reg.c" ??? line: 174: ??????? reg_val.type = REG_SZ;...

I've run into an error when trying to compile libnet/libnet_join.c: cc: "libnet/libnet_join.c", line 111: error 1588: "LDAP_NO_MEMORY" undefined. cc: "libnet/libnet_join.c", line 111: warning 563: Argument #2 is not the correct type. The source below is what triggers it (line 111 is marked): static ADS_STATUS libnet_connect_ads(const char *dns_domain_name,

On 1/6/23 8:11 AM, Dawson Greeley via samba wrote: > Hi, Im attempting to apply a few group policy settings but they dont seem to be applying on the machine in question, or some settings I cannot see in the GPME. > > > 1. Settings applied to openssh dont seem to create the required config files in /etc/ssh/sshd_config.d/ for ssh to actually pick up on these changes. Is there a

First thing - I'd like to say a big "THANK YOU" to the developers. I just upgraded to samba-3.0.23 and I've noticed an alarming issue with respect to my configuration. I've been using the built-in keytab management and it looks like the updated code no longer creates the userPrincipal in Active Directory. Whether this is an issue for others or not, it would be nice to have

Turns out that I was at least half-right, after all. I just opened the files contained in the last Samba release (contained in samba-4.6.5.tar.gz) and although the typos have been corrected in "./python/samba/provision/__init__.py", *they are still there* in "./examples/misc/adssearch.pl" and "./libgpo/gpo_util.c". It happened that, before my first post, I had

Hi I have a little problem to get Samba 3.0.26a to work with a w2k3 ad. If I try to connect to it I get an "Failed to join domain: Operations error". With debug I can see that samba tries to connect to the ldap server. But instead using the IP address it's using the name. Could not open LDAP connection to win1.test.ads.local:389: Connection refused In my enviroment, this

Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Changes since 4.11.5: --------------------- o Douglas Bagnall <douglas.bagnall at catalyst.net.nz> * BUG 14209: pygpo: Use correct method flags. o David Disseldorp <ddiss at samba.org> * BUG 14216: vfs_ceph_snapshots: Fix root relative path handling. o Torsten

On Tue, 26 Feb 2019 13:34:32 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Ok, I've analyzed this and found that the cause is a call to > getpwuid(uid) with the uid being that of the domain controller. > "wbinfo --uid-info=3000074" works and returns information, but this > library function fails. > This is then propagated upwards as a memory error,

======================================================== "It's better to be a lion for a day than a sheep all your life." Elizabeth Kenny ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.10 release series. Changes since 4.10.12 ---------------------- o Jeremy

Hi, I just upgraded to 4.8.9 and decided to give the samba_gpoupdate feature a whirl. However, it fails. The line that's failing is "gpos = ads.get_gpo_list(creds.get_username())" returning None. This is probably a failure, since it should otherwise return an empty list (if there were no gpos to return). But there is no output to indicate what may be failing. I have setup of three

Release Announcements ===================== This is the first release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.19.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.19 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

In April 2016 I reported the following typos in three source files related to sysvol and GPOs. ./examples/misc/adssearch.pl:357:"Default Domain Controllers Policy" => "6AC1786C-016F-11D2-945F-00C04fB984F9" ./libgpo/gpo_util.c:46: "6AC1786C-016F-11D2-945F-00C04fB984F9" } ./python/samba/provision/__init__.py:123:DEFAULT_DC_POLICY_GUID =