similar to: ADS, W2K3, and various other broken things. (rc1)

Hi people, I have a Linux box running Samba 3.0.2a in ADS mode MIT Kerberos 1.3.3. My W2K e WXP users can't access the linux box by netbios name, the only access that works is by IP address, I know that's caused because access thought IP address don't make use of Kerberos. The most strange for me it's that the same environment works fine with a W2K Active Directory, I read in same

Hi Jim, I did what the doc says but the problem is the same. Does anybody saw this work ? I mean, is the Samba 3.0.2a+Kerberos MIT 1.3.3 able to be accessed by a WXP, W2K or W2K3 machine, using Kerberos tickets generated in a Windows 2003 KDC (W2K3 AD) ? Thanks -----Mensagem original----- De: Jim McDonough [mailto:jmcd@us.ibm.com] Enviada em: segunda-feira, 19 de abril de 2004 17:07 Para:

Hi, I've got th same problem than in this tread (no solution found) : http://lists.samba.org/archive/samba/2005-November/113914.html except I've got the problem on all stations. I am unable to connect to samba server using it's hostname, whereas it's work with IP address. When I use the hostname, Samba always request for login/password. [2006/09/21 12:59:04, 3]

| When a Windows client attempts to browse shares on a Samba 3.0 server | authenticating against a Windows 2003 Active Directory domain, it | requests credentials. Typing in user name and password fails I am having this exact same issue. Attached is a sample copy of my smb.conf and krb5.conf along with some errors I got from the smbd logs (max debug level). smb.conf ---- [global] server

here's the tail end of the -d 10 log.host. It seems to not like the encryption type. Which should I be using, and where should I change it? -dave [2003/08/22 09:45:29, 3] smbd/process.c:switch_message(685) switch message SMBsesssetupX (pid 6310) [2003/08/22 09:45:29, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2003/08/22 09:45:29, 5]

Hi I'm having major problems setting up Samba 3.0.9 with kerberos authentication. I have also tried with 3.0.8(from Debian SID) with same result. smb.conf[1] has 'security = ads' , and 'use kerberos keytab = yes'. I have set up pam_krb5 and I get TGTs that works with my ssh servers. But, when I try to authenticate using smbclient -k -L server I get: "session setup failed:

Since I haven't gotten any responses from the segfault log I posted earlier, I will try another approach. Below is what happens when a client tries to connect. Again, this all started after I changed a username mapping entry from root = DOMAIN\Administrator to root = @"DOMAIN\Domain Admins". This is in a security = ADS setup. wbinfo -u and -g return the correct information.

I tried to use the samba share that I was able to access this morning, but now I cannot get to it. The error in the client's log is: Doing spnego session setup [2006/02/09 13:14:02, 3] ../smbd/sesssetup.c:reply_sesssetup_and_X_spnego(664) NativeOS=[Windows 2002 Service Pack 1 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[] [2006/02/09 13:14:02, 10]

Can someone verify that I am having the same problem with Mac OS X Panther (10.3.3) using Samba 3.0.2 based on my log below? I get this trying to connect from my WinXP machine to my Mac which is configured with ADS. If so, can you point me to a set of instructions on upgrading from 3.0.2 to 3.0.4 with this patch? I don't have control over the server I authenticate with...it is about 300

Hints or check lists for that type or error ? [2004/05/27 14:11:06.627563, 10, pid=23616] libads/kerberos_verify.c:ads_verify_ticket(185) ads_verify_ticket: enc type [1] failed to decrypt with error Bad encryption type [2004/05/27 14:11:06.627589, 10, pid=23616] passdb/secrets.c:secrets_named_mutex_release(716) secrets_named_mutex: released mutex for replay cache mutex [2004/05/27

Hi, all! I have the following environment here: - A Windows 2000 domain, with one server running Windows 2003 Server - A kerberos realm, using MIT Kerberos - A samba server, with security=ads The Windows 2003 server have a trust relationship with the MIT kerberos realm. Users logs on that kerberos realm on their Windows workstations, and are supposed to have access to the shares at samba

Hi, I just installed 3.0.2rc1 for testing, and I came across a problem with cross-realm authentication. I joined samba to our active directory domain, and I can see that it has host and cifs principals in windows kerberos. Our organization's primary kerberos realm (CEDE.PSU.EDU) is an MIT kerb5 realm, and we have a one-way non-transitive trust such that windows (server 2003) kerberos

List- I have several samba 3.0.0 file/print servers running in a Windows 2000 AD domain. I do not use winbind; but have an LDAP database for Unix UID's with nss_ldap. I have MIT krb5-1.3.1. When I have tried to upgrade these machines to samba 3.0.1, clients get prompted for a user name and password when trying to connect. I have seen others with this problem, but none of their fixes have

Hi I'm having problems with samba-3.0.21b and Windows Server 2003 domain controllers. When I try to access the samba server from a client (\\sambasrv) I only get a login prompt, no username/password combination works. Accessing the samba server through its IP-number instead of using the netbios name works. This together with the log message "Failed to verify incoming ticket!"

Hello, I had a perfectly good setup with samba being a domain member, and domain users accessing their shares, since beta1. A month and several updates from M$ later, clients were no longer able to log on to the samba machine. I know this must be related to the updates, since there have been absolutely no configuration / application modifications on the linux box, and clients who forgot to

Hello. I set up a samba 3.0.0 with ADS support. Everything is fine but authentication of incomming connections. I joined the ADS of a W2k3: linux:/ # /usr/local/samba/bin/net ads join "Computers" Using short domain name -- DOMAIN Joined 'LINUX' to realm 'DOMAIN.LOCAL' linux:/ # getent passwd root:x:0:0:root:/root:/bin/bash ...

I'm having problems with ADS membership for samba. I had a "mostly" working version with RHES v2.1, krb5 v1.2, samba v3.0.5. I knew to get to a fully functioning version I would need krb5 v1.3 or later. So finally I had an opertunity to junk RH's crufty krb5 and build from scratch with: RHES v2.1 MIT krb5 v1.4 samba v3.0.13 This works fine on another server. Now to the

I'm having problems with ADS membership for samba. I had a "mostly" working version with RHES v2.1, krb5 v1.2, samba v3.0.5. I knew to get to a fully functioning version I would need krb5 v1.3 or later. So finally I had an opertunity to junk RH's crufty krb5 and build from scratch with: RHES v2.1 MIT krb5 v1.4 samba v3.0.13 This works fine on another server. Now to the

Hello I have two similar servers, both are Debian Etch (fully updated). Both work as PDC with samba 3.0.24-6etch9. Both have squid proxy working and I am using winbind to authenticate my proxy users. Couple of days ago I've encountered a problem with authorization on one of my servers. I realized that winbind stopped working properly. wbinfo -t now gives: checking the trust secret via RPC

=20 \\128.252.123.123\sharename <file:///\\128.252.123.123\sharename>=20 =20 And it works as expected - my clients are in the same domain, no password is asked for, etc. =20 Using any form of the hostname in the URI, either \\hostname\sharename <file:///\\hostname\sharename> or \\hostname.domain.name\sharename <file:///\\hostname.domain.name\sharename> in the URI will