Re: DNS/Kerberos/LDAP integration question
- From: "Spin" <Spin@xxxxxxxx>
- Date: Sat, 28 Jan 2006 20:01:03 -0500
Joe, you are truly a gentleman and a scholar.
--
Spin
"Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:ONtJjiGJGHA.1124@xxxxxxxxxxxxxxxxxxxxxxx
> LDAP is not involved in the logon process. The best way to understand
> what happens is to use a packet sniffer. Perhaps you could hook up a
> machine via a hub and capture some packets while another machine logs on?
> Look for port 389 access to the domain controller if you are checking for
> LDAP. Kerberos is 88, etc. There is no better way to understand what
> happens on the wire than to do some packet sniffing.
>
> Note that as I said before, this does not include any LDAP code in logon
> scripts and such. We are just talking about the actual logon.
.
- References:
- DNS/Kerberos/LDAP integration question
- From: Spin
- Re: DNS/Kerberos/LDAP integration question
- From: Al Mulnick
- Re: DNS/Kerberos/LDAP integration question
- From: Spin
- Re: DNS/Kerberos/LDAP integration question
- From: Joe Kaplan \(MVP - ADSI\)
- DNS/Kerberos/LDAP integration question
- Prev by Date: Re: DNS/Kerberos/LDAP integration question
- Next by Date: Re: DNS/Kerberos/LDAP integration question
- Previous by thread: Re: DNS/Kerberos/LDAP integration question
- Next by thread: Re: DNS/Kerberos/LDAP integration question
- Index(es):
Relevant Pages
|