similar to: samba 3.0.2a & Win2003 AD controler

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several issues fixes since the 3.0.2a release and new features have been added as well. See the "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several issues fixes since the 3.0.2a release and new features have been added as well. See the "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include:

Hello the list, I have a problem using smbclient with samba 3.0.2a + kerberos, in a Win2000 AD environment. When I run smbclient -k -U <AD user> -L <server> where <AD user> is an AD user, and <server> the samba server OR the AD controller, I get the following error : krb5_cc_get_principal failed (No credentials cache found) spnego_gen_negTokenTarg failed: No

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

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

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

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]

Thanks TMS, that is not a major problem as of now.. i dont know why but i m facing many problems/errors while using samba :). now the major problem is wbinfo -g is not showing the full list. only few domain groups it is showing . do u have any idea about this ??? .please help On Fri, Jun 25, 2010 at 6:44 PM, <tms3 at tms3.com> wrote: > > > > --- Original message --- >

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK. I've done some more research, and here's what I get. smbd --version Version 3.0.0 strings libkrb5.so.3.2 | grep BRAND KRB5_BRAND: krb5-1-3-1-final 1.3.1 20030730 Everything seems to work, but trying to access the Samba server results in: [2003/12/11 14:54:19, 3] libads/kerberos_verify.c:ads_verify_ticket(308) ~ ads_verify_ticket: enc

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

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 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 All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

Hi, i have problems connecting to DFS-Share from Client WindowsXP. Same configuration works fine for Windows Vista and 7. On Windows 7 the LMCompatibility Level is 3. the striking point I see in logfile is following 2010/12/20 10:30:17, 1] smbd/service.c:make_connection_snum(1119) 10.184.144.171 (10.184.144.171) signed connect to service applbin initially as user useracc

Hi all, We're having some issues getting Samba to work in the way we'd like it to in our domain infrastructure. We have a real Windows domain WIN (WIN.DOC.IC.AC.UK) which is run on Windows 2003 domain controllers. We also have an MIT Kerberos realm DOC.IC.AC.UK. A realm trust exists such that WIN.DOC.IC.AC.UK trusts DOC.IC.AC.UK for authentication, and users have appropriate Kerberos