Re: Looking for details on how machine password aging works.
From: Glenn LeCheminant (the.only_at_gmail.com)
Date: 10/16/04
- Next message: Andrei Ungureanu: "RE: FSMO Error"
- Previous message: Aftab Siddiqi: "Re: Point workstation to a particular DC"
- In reply to: Bill: "Looking for details on how machine password aging works."
- Next in thread: barabba: "Re: Looking for details on how machine password aging works."
- Reply: barabba: "Re: Looking for details on how machine password aging works."
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 16 Oct 2004 01:43:00 -0700
Bill,
Machine account passwords do not expire as user account passwords do.
Machines automatically update their passwords every 7 days, but this is not
required.
Domain controllers keep a history of one password. This provides for
replication latency.
You may be thinking of the secure channel that is established between client
and domain controller.
This channel provides RPC encryption as I understand it and is not a
kerberos ticket. Unfortunately I was unable to find much documentation on
it. e.g. does it expire?
Now machine accounts can and do get kerberos tickets to gain access to
network resources. e.g. applying group policies requires a ticket. These
tickets will automatically be renewed in the background. If it fails to
renew, that in and of itself will not prevent a user from using or renewing
her ticket.
Hope that was helpful. Wish I knew more on the secure channel stuff.
Glenn
"Bill" <bill@barfcoswill.com> wrote in message
news:eV9CEGysEHA.1276@TK2MSFTNGP12.phx.gbl...
> I'm hoping someone either knows, or can point me to a reference on this. I
> need to understand what happens in the scenario below.
>
> A user gets his Kerberos ticket and starts accessing files on a member
> server.
> That member server's machine account password expires.
> The member server initiates a password change with its DC.
> Before the password change gets propagated back to the KDC that the user
got
> his user ticket from, the user makes another request to the server. At
this
> point, his ticket will contain wrong information about that member server.
>
> In the case outlined, what will the user experience? Does he get a request
> to reauthenticate? If so, what does the client do to make sure the new
> connection succeeds?
>
> Does the member server go and get a fresh ticket from a different DC? If
so,
> what is the mechanism to tell it to do so?
>
> Any insights thankfully accepted.
>
>
>
>
- Next message: Andrei Ungureanu: "RE: FSMO Error"
- Previous message: Aftab Siddiqi: "Re: Point workstation to a particular DC"
- In reply to: Bill: "Looking for details on how machine password aging works."
- Next in thread: barabba: "Re: Looking for details on how machine password aging works."
- Reply: barabba: "Re: Looking for details on how machine password aging works."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|