According to Q320853, we made fixes related to kerberos trust relationship traversal in SP2, GSSAPI-compatible delegation, and using more than one KDC in an MIT Realm. Hence, you "need" SP2 to make full interoperability work if your scenario uses something of the above. Without seeing the article I don't know more than that.
Installing the latest SP is generally good regardless. ----- This message is provided "AS IS" with no warranties, and confers no rights. Message may originate from an unmonitored alias ("davespam"). If so, use "davidchr" if a direct reply is required. Any opinions or policies stated within are my own and do not necessarily constitute those of my employer. I reside in Washington, USA, where Title 19 declares that sending me Unsolicited Commercial Email can result in a $500 fine. Harvesting of this address for purposes of bulk email (spam and UCE) is expressly prohibited unless by my explicit prior request. I retaliate viciously against spammers and spam sites. > -----Original Message----- > From: Turbo Fredriksson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 10:42 PM > To: [EMAIL PROTECTED] > Subject: Re: Win logon to a MIT Kerberos V KDC? > > > >>>>> "Actually" == Actually davidchr <[EMAIL PROTECTED]> writes: > > >> 1. Installed W2k Pro 2. Installed SP3 a. Auth to non-M$ KDC > >> requires SP2 or greater! SP3 is the latest from M$. > > Actually> Clarification: > > Actually> No service pack is required to make Win2K authenticate > Actually> to a non-MS KDC-- it works out of the box. However, > Actually> installing the latest SP is still always recommended. > > On some M$ site page, it was said that SP2 (or higher) was > required. ________________________________________________ > Kerberos mailing list [EMAIL PROTECTED] > http://mailman.mit.edu/mailman/listinfo/kerberos > ________________________________________________ Kerberos mailing list [EMAIL PROTECTED] http://mailman.mit.edu/mailman/listinfo/kerberos