similar to: Windows 2000 and krb5 tickets.

Hello, I'm trying to access a samba share using an ADS user credentials. I always get an error, and the debug traces (log level = 5) are giving me the output in the follow. I have searched the samba ML archives, and I have found the thread http://lists.samba.org/archive/samba/2004-April/084545.html but, before asking the system admin to apply the eventual KB fixes, I would like to know if the

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 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

I'm beating my head up against the wall here.. Need some extra eyes!!! Setup -- Samba4 Domain Controller and samba3 print server.. DNS FlatFile,, All dns works.. Issue, When I browse to the print Server vi \\IP-Address I am able to connect just fine.. When I browse using \\netbios-name I connect to the server but it opens up a username/pass dialog box and no name or passwords will work..

We upgraded our Solaris 9 samba server to version 3.0.2a and configured Kerberos MIT 1.3.2. I was able to run kinit and join samba to our windows 2003 domain as a domain member, but when I am trying to browse the samba shares from a windows XP machine it is failing. When I am looking at the samba logs this is what I am getting: [2004/03/30 11:15:26, 3]

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]

Hello list. I've got a problem using samba-3.0.4 (RedHat AS 3.0) the server is member of a Win2003 Active directory domain All stuff about krb5 seems to work correctly kinit user@REALM klist etc... net ads join -U administrator has worked well too But when any Windows client member of the domain try to connect to the server it asks me for a user/pass. here is the log. [2004/08/10

Hello samba experts ! I have a big problem with my samba 3.0.2a on debian. I use winbindd, which seems to work (getent passwd/group and wbinfo -u works), and the net ads join worked too, but the authentication with the AD controler, hosted on Win2003 Server, fails. Sample of the level 3 log file : ... [2004/05/04 08:47:20, 3] smbd/process.c:switch_message(685) switch message SMBsesssetupX

Fantastic! On Monday I'll give it a try! -----Original Message----- From: Tim Jordan [mailto:timothy_jordan@labor.state.ak.us] Sent: Fri 12/12/2003 20:56 To: Tom Dickson; m.c.hudson@open.ac.uk; admina@labor.ak.us Cc: fernandor@sescam.jccm.es; jerry@samba.org; samba@samba.org Subject: Re: [Samba] Windows 2000 and krb5 tickets...SOLVED Browsing is working from my W2K and XP

Hello, i need some help. A samba3 (3.6.9-151.el6_4.1) ADS member (WIN 2008 AD Master) Server did his work for years. Since hours some Clients can not connect to the name (\\fileserver) connecting to \\192... sometimes work. Log say: 2013/10/09 09:54:27.735101, 3] smbd/sesssetup.c:660(reply_spnego_negotiate) reply_spnego_negotiate: Got secblob of size 1638 [2013/10/09 09:54:27.735423, 3]

I'm running a Samba 3.0.0 server in production in security = ADS mode against a W2k ADS server. Works just fine, thanks! We're sort of under pressure to regrade to a 2003 AD server, which sent me trying stuff out a bit. Meager results. The 3.0.0 I have (linked with MIT krb5-1.2.8) refuses to verify incoming tickets: [2003/10/28 16:27:36, 3]

List, Long and confusing message follows... I'm facing a frustrating problem. XP clients can use resoures on the samba server by IP-address, but not by name. So, "net view \\servername" gives "access denied" but "net view \\ipaddress" gives list of shared resources. Samba server (3.2.7 sernet rpm) is a member server in W2003 domain. I emphasise that with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm trying to access a Samba 3.0 server (running on Debian unstable) in an Active Directory environment. I successfully joined the domain, klist shows my Kerberos ticket(s) and I can use smbclient -k to access a Windows 2000 server. However, when I try to access a share on the Samba machine from a Windows 2000 client, I'm being asked

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's an update for those of you struggling to get Samba working in an AD domain environment. ~ Summary: in securirty = ads, clients can browse to the ~ Samba member server via IP but not by name (either netbios ~ or DNS). Kinit and wbinfo -t all work as expected. The apparent reason for this is that the 2k client uses NTLMSSP when you

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]

Running into a lot of people upgrading to the 3.0.6 package that all of a sudden begin to experience the "Failed to verify incoming ticket!" errors etc., that are generally associated with a kerberos package incompatibility. However many of these people are running later versions of kerberos *and* reverting to a previous version of Samba appears to fix the issue. Is there something new

Hi All, I have machine M1 hosting Samba PDC. It stores only user information. I have machine M2 acting as KDC server. I have machine M3 hosting CIFS shares and it joins into the domain hosted by PDC M1. I have machine M4 used as CIFS client. On M2, I have added users and cifs/host service principals for M3. Also added service principal in keytab file. I have added all the user and service

I'm running Windows Server 2008 and trying to connect to Samba 3.0.37 on Opensolaris. The Samba system is a member of a Windows Server 2008-based Active Directory domain - it was able to join the domain just fine - and Windows XP, Windows 2000, Windows Vista, and Windows 7 can connect, but Windows Server 2008 SP2 cannot connect. The log file is posted below - I'm guessing the key is the

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