similar to: v3.0.0, AD, 2k3 mumbles

I'm pleased to announce the release of the "arsenal" package v3.0.0 on CRAN (https://cran.r-project.org/package=arsenal)! "arsenal" has experienced some major growth in the last few months, starting with the release of v2.0.0 in January. We tried to maintain backwards compatibility wherever possible, but had to eliminate it in some places. With that said, here's the

I'm pleased to announce the release of the "arsenal" package v3.0.0 on CRAN (https://cran.r-project.org/package=arsenal)! "arsenal" has experienced some major growth in the last few months, starting with the release of v2.0.0 in January. We tried to maintain backwards compatibility wherever possible, but had to eliminate it in some places. With that said, here's the

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:

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

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

I have a Tyan Tiger S2466 MPX motherboard with Dual Atlon MP 2800+ CPUs and 1GB PC2100 DDR SDRAM. For disk drive I have an LSI53C1030 and 4 Seagate ST336607LWs in a software raid 5 configuration. I installed Centos 4.1 and everything was fine running kernel-smp-2.6.9-11.EL. However when I upated to Centos 4.2 I have run into problems. Namely after a finite amount of disk traffic the system

Hi everyone ! My getent passwd and getent group are not working but my wbinfo -ugmt commands are. Does Somebody know what I missed ? Any check list ? Thanks ! Bertram _________________________________________________________________ MSN Search, le moteur de recherche qui pense comme vous ! http://search.msn.fr/

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

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

On Tue, Dec 2, 2014 at 2:26 AM, Gregory Sloop <gregs at sloop.net> wrote: > I love the idea of a low-power high-performance appliance. A NAS will > work fine for storage, but it's not going to act as a DC etc. [At least > none that I'm aware of and would trust.] > > Even appliances sorta like this, that I've seen, are easily five times the > price. > >

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

Hello List We run a Solaris9 Server running Samba 3.0.20, Local Users (no winbind) but authenticating against ADS. There are up to 800 concurrent users, mostly Windows XP SP3. When clients access MyDocuments, which is redirected to the Samba share, we observe several "Session Setup AndX Request"s followed by "Session Setup AndX Response, Error: