similar to: smbd/sesssetup.c:reply_spnego_kerberos(173) Failed to verify incoming ticket!

Hi Ryan! i didn't build samba, i used the binaries shipped with my debian sarge distro... do you think it's an issue with the kerberos version this samba is using? Joysn On Tue, Feb 01, 2005 at 05:11:30PM -0500, Ryan Frantz wrote: > > This sounds similar to a problem I was having (RH AS 2.1, though). What > was the configure command you used to build Samba? > > I kept

One thing to rule out is that there is a clock difference of greater than 5 minutes between Samba Domain Member and the DCs. Make sure that you Samba Domain Member clock has approximately the same time as the DC. You can do net time set -S dcname/dcip. -Marc > -----Original Message----- > From: joysn@gmx.net [mailto:joysn@gmx.net] > Sent: Tuesday, February 01, 2005 2:19 PM > To:

Hi List - I have a friend that runs a Windows domain with Active Directory and is setting up some new laptops with Redhat. He wants to automate installs, etc. on these laptops as he would on a Windows machine. Just wondering if anyone has any experience with this - and also if anyone knows of a good tutorial for joining a Linux machine to a Windows domain. I've heard that it is possible.

Hi all, I am currently running samba 3.0.10-1 on a Debian box, my smb.conf file looks as follow workgroup = WORKGROUP server string = "Samba Server" netbios name = MyComputerName local master = no domain master = no preferred master = no guest account = nobody guest ok = no log file = /var/log/samba/log.%m max log size = 1000 realm =

I use Samba 3.0.2rc2 on Suse 9.0 (heimdal 0.6-68) as a Domainmember for File -and Printservices (about 100 Users). The Linuxbox ist added to the ADS, the User are mapped through winbindd. Everything works.. The I upgraded to Samba 3.0.2 and if I start the daemon, after a while follow Error occured if a Domainclient will connect to the Sambabox: [2004/02/13 13:33:43, 1]

Hi. I we are migrating form domain ad.adc.com to ad.xyz.com , there is a trust between the two domains. Before the move the file server was work perfectly, post migration I get the following in the samba logs [2013/08/19 08:07:15.961679, 1] smbd/sesssetup.c:342(reply_spnego_kerberos) Failed to verify incoming ticket with error NT_STATUS_LOGON_FAILURE! [2013/08/19 08:07:25.983662, 1]

Hi everyone, I've done a lot of reading on this issue over the last couple of days I had a "Red Hat Linux release 9 (Shrike)" box running 3.0.3a and the stock redhat krb5 package and it was authenticating against a w2k AD domain (over which I have very little control save for my little OU). things were working ok, but I wanted to update it to the new bug fixed versions.

Hi ! My problem is that : [2004/05/12 16:07:30, 1] smbd/sesssetup.c:reply_spnego_kerberos(173) Failed to verify incoming ticket! [2004/05/12 16:07:30, 1] smbd/sesssetup.c:reply_spnego_kerberos(173) Failed to verify incoming ticket! [2004/05/12 16:07:39, 1] smbd/sesssetup.c:reply_spnego_kerberos(173) Failed to verify incoming ticket! [2004/05/12 16:07:59, 0]

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

Hello list! When em0 has an inet address while bridge0 doesn't, it seems to be OK: ----- bs1% uname -a FreeBSD bs1.sp34.ru 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun May 25 20:15:26 MSD 2008 root@bs1.sp34.ru:/usr/obj/usr/src/sys/BSM i386 bs1% ifconfig em0; ifconfig tap0; ifconfig bridge0 em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

Hi, I'm trying to get Samba 3.0.2 working against a Windows 2003 Active Directory. I can join the Linux box (RedHat Advanced Server) to the domain using "net ads join" and it appears in the Windows machine's Users and Computers snap in but when trying to map a drive from Windows you just get a continuous password dialog bog and on the Linux box Samba produces the following error

I am running samba 3.0.23d on Gentoo. I have a particularly problematic server that is a domain member of our AD domain. After joining the domain, shares are available and user credentials work just fine. Then, suddenly for no apparent reason, it stops working. And, then again, just as quickly as the problem starts, it goes away. I have looked at this thing as many ways as I can possibly

Hello, a few people asked about this problem here, but up to now I have not seen a solution. System: fresh installed Debian Woody with backported packages from backports.org, nothing else, only samba3 running. System ist intended as replacement for our old windows-fileserver. Situation: after installation and configuration all worked well, accessing shares works without password-checking.

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]

Hello I was tried to use Winbind to migration Windows 2003 users and groups but cannot shown machine account. Anyone has solution ? Thanks _________________________________________________________________ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!

Hi all, I have installed Samba 3.0.7 on HP-UX and I have configured to work with "security = ADS" with a Windows 2000 Domain Controller and kerberized connection. It works fine, I have joined the domain and I can use the share defined, but the log contains: [2005/07/28 09:46:32, 1] smbd/service.c:make_connection_snum(648) 10.11.50.51 (10.11.50.51) connect to service SHARE initially

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

> Message: 4 > Date: Fri, 27 Jul 2012 15:29:41 -0700 > From: Harry Mangalam <hjmangalam at gmail.com> > Subject: [Gluster-users] Change NFS parameters post-start > To: gluster-users <gluster-users at gluster.org> > Message-ID: > <CAEib2OnKfENr8NhVwkvpsw21C5QJmzu_=C9j144p2Gkn7KP=LQ at mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 >

Hi, I have set up our samba box in 'ADS' mode; the problem I have is clients connecting to the server can not do so by using its netbios name. Only when they use the IP address of the machine are they able to be authenticated and browse the box. When clients connect via the netbios name this message will appear in my samba logs with the IP of the connecting client;

Good morning everyone, I have had Samba 3.0.9 running on Solaris, connected to a Windows AD domain for a couple of weeks now, and i've suddenly started getting the following errors: [2005/01/07 11:31:55, 1] smbd/sesssetup.c:reply_spnego_kerberos(250) Username <domain>\IT075$ is invalid on this system It looks like some sort of issue with Kerberos, but I'm able to connect to