similar to: Followup to previous request

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just tried to join my SLES9 (Suese Linux Enterprise Server 9) to my ads. I follow a mixture of the howtos [1], [2], [3]. Everything works fine (kinit gives me a valid kerberos ticket), but the `net ads join -U $DOMAIN\\$USER` command segfaults. Software I have intalled: - - samba 3.0.23c (from ftp.samba.org) - - heimdal 0.6.1rc2 Here a debug 5

I'm setting up anew server with 3.3.0rc1 and cannot join my AD domain. It may not be a problem strictly linked to the samba versiom, for my Active Directory administrators have tightened and enforced security policies since last time I joined a linux server succefully. BTW, this is what I get with net join command: namenor:/usr/src/local/samba/samba-3.3.0rc1/source # net ads join -S

On a recommendation from this list I checked the junklog file, the output from which I attached below. It looks as if it does not even see the linux machine as it indicates not seeing "explorer" which is the local netbios name. The Win XP machine does not even show in the log. Here is the last entry for nmbd.log: ***** [2003/11/21 06:24:58, 0] nmbd/nmbd.c:terminate(54) Got SIGTERM:

I have the problem with smbclient -L ... This is a level 50 debug message [2004/02/23 10:45:00, 5] lib/debug.c:debug_dump_status(359) INFO: Current debug levels: all: True/50 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0 rpc_parse: False/0 rpc_srv: False/0 rpc_cli: False/0 passdb: False/0 sam: False/0 auth: False/0 winbind:

Have installed Redhat ES 3.1 and updated to samba-3.02-6.3E The PDC is solaris running PC netlink. Can join the domain if running samba 2.28. Have tried net oldjoin as well as net join but to no avail. Debug level 5 dump attached. Any help appreciated. [2004/03/16 11:56:53, 5] lib/debug.c:debug_dump_status(360) INFO: Current debug levels: all: True/5 tdb: False/0

Hi all I am having trouble joining a server to our new AD 2008 server with DOMAIN security mode. ADS Security mode works just fine ,but the server is going to be a Clearcase Vobserver and ADS is not supported. The AD server is also configured to only allow NTLMv2 and not older NTLM, the last 4 lines i global show this. Tried version 3.3.2 and 3.0.34. Same errors om both. Joining a older AD

Hello, Sorry for the long post but I've been working on this for over a day now and I haven't made any progress. I hope someone can help me with this. I have created a new ad domain on a win2k server. I am not user kerberos. I have the redhat enterprise linux 3 version of samba installed on my machine. I use: net rpc join member -Uadmin%password -S adserver to join the linux server

Sorry, I'll try this again. It appears the email got stripped out and left the attachment. ------------------------ I'm having an issue where any machine refuses to join the domain. It's a a Debian server(lenny) with an LDAP backend. I assume the issue is something obvious, but this is an "inherited" network and based on the state of the rest of it, the issue could be

Hi, We are testing the samba-3.0.23d in a samba server as role member in a domain with PDC (samba-3.0.20) and ldap as backend. The first tests don't left us join the machine in the domain, the following is showed: [root@machinetest bin]# ./net rpc testjoin -d 10 [2006/11/24 12:28:26, 5] lib/debug.c:debug_dump_status(391) INFO: Current debug levels: all: True/10 tdb: False/0

I have two networks: 192.168.1.0 with netmask 255.255.255.0 and 172.16.0.0 with netmask 255.255.254.0, when I join in domain in first network hostname registered successfully, but in second network: sudo net ads join -U admin Enter admin's password: Using short domain name -- BUTB Joined 'TH-2-011' to realm 'butb.by' DNS update failed! dpkg -l | grep samba ii samba

QUESTION: Does samba have client side TLS capabilities? BACKGROUND Samba ADS compliant distributions tried: RHEL samba 3.0.10 Blastware samba 3.0.22 (for Solaris 8 and above) Solaris 9 compilations 3.0.24, 25b, 25c, 26a My ADS is running in native 2003 mode. The only access I have to it is to set up Machine accounts. SMB.CONF For all versions I used the same smb.conf (see end of document) NET

I am trying to vampire the account database from my NT 4 DC (that has SP6A installed). The DC's name is nemesis. The samba computer's name is mjollnir. The directions seem trivial: 1.) Join the Domain as a BDC with: net rpc join -S nemesis -W WHSD -U Administrator this worked fine and I can see the computer listed in server manager with type "Windows NT Backup" 2.) Run

In my lab I successfully got everything working running our secured Active Directory and Fedora Core 3. In our AD we have secured settings like refusing NTLMv2, require LDAP signing, SMB signing and more. In the lab we have the following rpm's: krb5-workstation-1.3.4.7 samba-3.0.8.0.pre1.3 openldap-2.2.13-2 But now we're implementing this in production and there we're running Red Hat

Hey, I don't know if this is the right list to ask this question in, but I have tried on the IRC (irc.freenode.net #samba) and people on there advised me to try here instead. I have: Debian 4.0r4 Samba version 3.0.24 - mail.birke-gym.dk - 10.3.16.1 krb5 Version 1.4.4-7etch6 Kernel Version 2.6.18-6-amd64 A Windows Server 2003 SP2 with AD/DC - bgdc.birke-gym.dk - 10.3.17.1

On FreeBSD 6.0-RELEASE-p2 using samba-3.0.21a,1 the net command seg faults. Does anyone know what is going on? Thanks -rcollins ----- net ads join -Uadministrator -d 10 ----- [2006/01/23 12:36:59, 5] lib/debug.c:debug_dump_status(368) INFO: Current debug levels: all: True/10 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0 rpc_parse: False/0

Yes, this is in fact caused by LDAP server signing requirements set to "Require Siging". I put a bug in previously here: https://bugzilla.samba.org/show_bug.cgi?id=765 And Jeremy Naylor created a patch to add TLS support in libads. The TLS method is potentially more secure, but it requires a certificate be installed on the KDC. You could try applying the patch and setting up the

Hi List, I'm wondering if someone can help me get past these errors Joining an ADS Domain, using samba 3.0.14a & kerberos 1.3.5. When I look at the debug output from the join attempt, it almost seems as though The join is looking for an cn or something from the AD that doesn't exist. I'm not an Windows person and the AD admins are not around to help peep this out. Can anyone

Thanks for that interesting information. But how come it works in my lab (where I'm running Fedora Core 3)? Could it be because I'm running a newer version of LDAP? You think this will be fixed in future releases without the need to put certificated on the DC? Are there any detailinformation where to put the certificate on our DC:s? Unfourtunately we're not running any CA in our

Hiya, I compiled the RPMs of Samba 3.0.0 RC1 according to "../samba-3.0.0rc1/packaging/RedHat/samba.spec" and installed the binaries from the freshly compiled rpm on my up2date Redhat 9.0 Server. The command "net join -U Administrator%****** -d10" creates following error: ***** SNIP ***** [root@samba30srv RedHat]# net join -U Administrator%******** -d10 [2003/08/19

Hello : I tried to join to my active directory, i run the follow command, i read all hit into google about this and "all" howto on the google "how join a linux to a active directory"....and all possible combination of words about the last error, i found other people with the same error...but not solution. I tried into Debian (3.0.14a) and Centos(3.0.14a and 3.0.20 manual