similar to: Samba, ADS and "Failed to verify incoming ticket!"

Hello What is sequence for "auth methods" running in ADS mode ? How I can find this ? With best regards Martynas

Hello I have Samba running as AD member. In addition there is a support of quest user connections to shares, that allow guest connections to shares, where access is restricted on IP addresses base. Problem is, that Administrator is not mapped to guest, because Administrator in AD domain is locked. Samba gets respond NT_STATUS_ACCOUNT_LOCKED_OUT and denies connection. While computers, that are

I am struggling with a Samba/Server 2003 problem which doesn't make sense. I have compiled Samba 3.0.14a and MIT Kerberos 1.3.6 several times on different machines. I have a set of RPMS which work fine on one of my workstations, but do not work on the server. On the server I get the dreaded: reply_spnego_kerberos(173) Failed to verify incoming ticket! in the logs. I have compiled

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

Hello I see, that "enable asu support = no: is available and I can point ADMIN$ wherever I want. I just want ask if this setting will not have any other impact to my current services (Samba installation is ADS membership). Can you provide more detailed explanation of "enable asu support = no" impact ? Thank you ! With best regards Martynas -----Original Message----- From:

Hello everyone, I'm sorry for this long post, but I think there is a real understanding problem for many people on ADS domain membership. I'm not the first to post about this type of problem, however I didn't find an answer to it in the archives and I followed the HOWTO-collection. Well, this is what I'm doing : I am using samba-3.0.1 compiled from source, MIT kerberos 1.3.1

Hello I want use stand alone samba server 3.0.0 on Solaris 8 box. We have users configure locally, but authentication is done via Kerberos server. I expected to deal with samba installation quite easy, but got stuck. As I understood from documentation - there are two ways how to do that : 1. Install pam authentication. Well this works fine from samba side. Alias - it requires password

Hello I have samba 3.0.13 running in ADS mode. For some specific reason I want to disable winbindd authentication while I want winbindd keep running. If I understood right - option "auth methods" would help to do that. But I am not sure if this will not break existing services : auth methods = guest sam All users that authenticate are created locally in /etc/passwd file. Can anybody

Hello I decided to test password migration (on Solaris 8 box with SUNWspro C) and built samba with pam_smbpass module : CC=cc ./configure --prefix=/opt/local/samba --with-acl-support --with-pam --with-pam_smbpass Then installed bin/pam_smbpass.so in /usr/lib/security : # ls -al /usr/lib/security/pam_smbpass.so -rwxr-xr-x 1 root sys 2091380 Oct 23 11:01

Hello Is it possible to get information when next official Samba release (> 3.0.14a) will be published ? Thank you very much for information. With best regards Martynas

Hello Is it possible to make ADMIN$ share (Samba 3.0.14a) world writeable and pointing to specific directory ? I am interested in building some sort of honey pot that would allow virus to transfer files to ADMIN$ under putting mode logging around. Any other solutions with samba ? Martynas

Hi, We are experiencing a problem with Samba 3.6.4 on Solaris 10 update 10. This problem has only recently started since an upgrade to v3.6.3 and was still present after rebuilding to 3.6.4. We are using the version of samba packaged by OpenCSW. >From a client perspective, the issue is manifested as intermittent very poor performance or intermittent inability to save a file to the share at

Hello I need some advice from gurus. I identified several Windows NT computers, that are persistently trying to access my samba server. They are connecting to IPC$ with NULL information both in password and username fields. Below you will find excerpt from samba log file. My questions would be following. What is SPOOLSS_ADDPRINTEREX ? Can it be some kind of worm ? If yes, how I can catch it

Hi all, By some days around 12:00 o'clock I have the following problem with my SUSE Linux 2.6.11.4-21.9-default i686 i386 GNU/Linux, with Samba Version 3.0.21a-0.1-SUSE: xxx:~ # tail /var/log/samba/log.machine01 [2006/02/23 12:05:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(180) Failed to verify incoming ticket! [2006/02/23 12:06:04, 0] tdb/tdbutil.c:tdb_log(772)

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, We are experiencing ADS lower performance on Samba-3.0.22 for HPUX. I did Google search, and find out one message posted at http://lists.samba.org/archive/samba/2005-November/114231.html at the earlier time. >From my observation, it seems there was a spin on reply_spnego_negotiate()/ reply_spnego_kerberos() calls that invokes register_vuid() to register uvid with different vuid# for a

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:

I have a server with ubuntu 6.06 LTS with samba 3.0.23d (compiled against heimdal krb5) and heimdal-clients0.7.1-1ubuntu3. I have configured samba as a ADS domain member. Problem is that when I want to access a samba share from a windows xp domain member I am keep asked for user and password and debug level 3 shows this on log.<workstation_name> : ... [2006/11/30 12:42:15, 3]

[2008/06/11 12:07:03, 3] smbd/sesssetup.c:reply_spnego_negotiate(525) Got OID 1 2 840 113554 1 2 2 [2008/06/11 12:07:03, 3] smbd/sesssetup.c:reply_spnego_negotiate(525) Got OID 1 3 6 1 4 1 311 2 2 10 [2008/06/11 12:07:03, 3] smbd/sesssetup.c:reply_spnego_negotiate(528) Got secblob of size 1205 [2008/06/11 12:07:03, 3] libads/kerberos_verify.c:ads_secrets_verify_ticket(249)

Hi, Thanks to all who responded to my initial post to the list regarding "Ticket not yet valid" messages in my samba logs. I neglected to include this in my initial post - we had already suspected clock synchronisation problems, and all of our servers (AIX Samba server and windows clients) are all synchronised to the AD DC, which is sychronised to an internet atomic clock in Melbourne.