SCIENTIFIC-LINUX-USERS Archives

October 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stephen Isard <[log in to unmask]>
Reply To:
Stephen Isard <[log in to unmask]>
Date:
Thu, 19 Oct 2017 10:31:11 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
On Wed, 18 Oct 2017 20:45:41 -0400, Glenn (Gedaliah) Wolosh <[log in to unmask]> wrote:

>> On Oct 18, 2017, at 8:26 PM, Stephen Isard <[log in to unmask]> wrote:
>> 
>> On Wed, 18 Oct 2017 20:05:13 -0400, Bluejay Adametz <[log in to unmask]> wrote:
>> 
>>>> Since the clocks of the two machines appear to agree, I would
>>>> have expected that either both should produce the error or neither.
>>> 
>>> Are they both getting tickets from the same source? (might be a dumb
>>> question...)
>> 
>> To the best of my understanding, they are.  That is, the admin_server machine name is the same for both machines and resolves to the same ip address on both machines.
>
>The admin_server is not where the tickets are coming from. Are the “kdc” entries the same on both machines?

The admin_server entry in /etc/krb5.conf is the only machine name in the file and it is kdc.domain.name.
>
>—Gedaliah Wolosh
>
>> 
>>>                - Bluejay Adametz, CFII, A&P, http://wildcorvid.org
>>> 
>>> "I hate quotations." - Ralph Waldo Emerson
>>> 
>>> --
>>> NOTICE:  This message, including any attachments, is only for the use of
>>> the intended recipient(s) and may contain confidential, sensitive and/or
>>> privileged information, or information otherwise prohibited from
>>> dissemination or disclosure by law or regulation, including applicable
>>> export regulations.  If the reader of this message is not the intended
>>> recipient, you are hereby notified that any use, disclosure, copying,
>>> dissemination or distribution of this message or any of its attachments is
>>> strictly prohibited.  If you received this message in error, please contact
>>> the sender immediately by reply email and destroy this message, including
>>> all attachments, and any copies thereof.

ATOM RSS1 RSS2