similar to: My 'net ads keytab' can't write to keytab in samba 3.0.6

Hello. I recompiled from the samba.org 3.0.7 SRPMs and it worked like a charm. I think the problem may have been that I was using RHEL3's 3.0.6 samba RPMs which depended on their own krb5-libs, and I used kerberos rpms that don't use e2fsprogs's libcom_err. Anyone privilaged enough to be using RHEL3 to integrate their linux machines into ADS may want to rebuild anything depending on

I have samba+ads working fine *HOWEVER* when I run net ads keytab create it fails. Using -d 10 the debug output says it cannot write to the file. This is truly bizarre as I am running this as root! e.g. # /usr/local/opt/samba/samba-3.0.24/bin/net ads keytab create ; echo $? 183 And /usr/local/opt/samba/samba-3.0.24/bin/net -d 10 ads keytab create ; echo $? Gives [..snip..] ads_get_kvno:

The net ads joins the host to the AD, but cant get the proper kerberos tix. Manually generating the kerberos keytab from AD dont work. Any suggestions? root@host /#head -1 /etc/release Solaris 10 10/08 s10s_u6wos_07b SPARC root@host /usr/sfw/sbin#./smbd -V Version 3.0.28 root@host /#for PKG in `pkginfo -x | grep -i samba | awk '{print $1}'`; do VER=`pkginfo -l ${PKG} | grep PSTAMP`;

I am trying to join a samba server and have the keytab file set. After joining there was no keytab file so I ran the command: /usr/sfw/sbin/net ads keytab add host -d 10 This was the result: [2007/12/04 21:40:09, 5] lib/debug.c:(391) INFO: Current debug levels: all: True/10 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0 rpc_parse: False/0

Hello. I'm having difficulty running kerberized samba on my Linux box in my Windows ADS domain. Specifically, smbclient -k //server/share fails with a "session setup failed: NT_STATUS_LOGON_FAILURE" error message. I ran smbd with -d 3 debugging verbosity, and the following came out on stdout/stderr. I marked the interesting lines with ***'s: # smbd -i -d 3

When "use kerberos keytab = yes" in smb.conf is set with samba-3.2.8 and the environment variable KRB5_KTNAME is not set with the value using prefix "FILE:" or the default_keytab in /etc/krb5.conf is set without the prefix i.e. default_keytab_name = /etc/v5srvtab then the function smb_krb5_open_keytab() returns KRB5_KT_UNKNOWN_TYPE. If smb_krb5_open_keytab with a

Of course i can! Hereby the backtrace with symbols: Program received signal SIGSEGV, Segmentation fault. free_PrincipalName (data=data at entry=0x45) at default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c:961 961 default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c: No such file or directory. (gdb) bt #0 free_PrincipalName (data=data at entry=0x45) at

Hi Jeremy, Jerry and samba experts, This is Suresh from EMC . I am having difficulty in creating and adding a Kerberos principal using samba's net utility. This server is configured as a Winbind client to a Windows 2003 Active Directory. I've successfully bound it to AD and I am able to authenticate. If I log into this host I am properly issued a Kerberos ticket from AD so it would

On Tue, Jun 07, 2016 at 06:59:56AM +0000, Lars Maes wrote: > Of course i can! > > Hereby the backtrace with symbols: > > Program received signal SIGSEGV, Segmentation fault. > free_PrincipalName (data=data at entry=0x45) at default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c:961 > 961 default/source4/heimdal/lib/asn1/asn1_krb5_asn1.c: No such file or directory. > (gdb)

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

Hi All, I am getting Kerberos "enc type" problem that I can't explain: [2005/06/11 11:41:29, 1, pid=29355] libads/kerberos_verify.c:ads_keytab_verify_ticket(61) ads_keytab_verify_ticket: krb5_kt_start_seq_get failed (No such file or directory) [2005/06/11 11:41:29, 3, pid=29355] libads/kerberos_verify.c:ads_secrets_verify_ticket(193) ads_secrets_verify_ticket: enc type [16]

On Thu, 14 Jun 2018, Patrick Begou wrote: > Hi, > > I'm facing a problem with setting up LDAP+TLS client authentication in a > kickstart script on CentOS7 for several days. > > Setting up manualy the config with system-config-authentication works but I > need to automate this in kickstart for deploying cluster nodes. > This show that the server side is running fine.

hello all, i am trying to rpmbuild samba source 3.0.11-1 and ran into this error and can not figure out what is wrong. the follow error as follows libads/kerberos_keytab.c: In function `ads_keytab_flush'': libads/kerberos_keytab.c:429: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See

Hello everybody, I have run into a problem which I am not able to resolve by myself :-( Yesterday I have added a new printer (cups) to a Samba 3.0.28a server. The new printer showed up in the network neighborhood (Windows XP) and I was able to print to the new print queue. Then I tried to publish the new printer to the AD ( we use a windows 2000 server for user administration and GPOs) with the

Hi, Using samba 3.0.25b, testing to join to a Windows 2008 domain using ADS security with kerberos and it doesn't seem to work. Anybody else tried this combination? Same configuration worked joining to a Windows 2003 R2 domain. I'm not a samba expert but looking at the log it looks like the not_defined_in_RFC4178@please_ignore have something to do with it? Output from "net

Hi, we've got a samba-3.0.21a-1 systems that's set up w/ winbind to query AD to authenticate users w/out Unix accts. The system is also set up to support our LDAP'd UNIX accts. After setting the [global] section like this: [global] realm = WIN.OURDOMAIN.COM security = ads password server = thebes balsam encrypt passwords = yes log file = /var/log/samba/log.%m

Hi Guys- We are a group involved in a project to move an application from Windows to AIX, and part of the application involves reading OSF DFS shares, and making the filesystem available to Windows machines through SAMBA. The conversion of the application has gone well, but it is our first time using SAMBA and I have some questions that hopefully are not too dumb, and if they are, we would gladly

I updated my PDC and BDC to Samba 4.4.7. Compiled from source into /usr/local/samba. On the samba domain controllers "/usr/local/samba/bin/wbinfo -u" shows the local domain users but not the trusted one. Everything indicates trusts are ok # /usr/local/samba/bin/net rpc trustdom list -U Administrator Enter Administrator's password: Trusted domains

We have Samba 3.2.4 on two SLES 10 (one is SP1, the other SP2 64bit) machines. Both are member servers in our ADS, which was over the past month given some additional DCs, new IPs for all DCs, and upgraded to Windows 2008 (from win2003). The krb5.conf and nsswitch.conf files on the two machines are identical; the smb.conf files are *nearly* identical in their common section; the filewall rules

Hi all, I'm not having any success adding samba (3.0.28 on Solaris 10) to a Windows AD server (2003 R2) per the instructions here: (In addition to much googling) http://us3.samba.org/samba/docs/man/Samba-Guide/unixclients.html#adssdm The error is: bash-3.00# /usr/sfw/sbin/net ads join -U Administrator Administrator's password: Using short domain name -- BETA Failed to set