In November 2005 I posted an article on the DSProxy referral changes that are included in Exchange Server 2003 Service Pack 2. For the full article, please see http://blogs.technet.com/exchange/ar...
Updated Jul 01, 2019
Version 2.0
Blog Post
We are having a problem where after the SP2 being applied, SOME, but not all of our Outlook clients are getting logon popups from a GC in another domain in our forest. If the user either enters their credentials, or just exits out of the popup things seem to be ok.
The easiest way for me to replicate the problem is to create a new outlook 2003 profile, and click check names. The popup will always occur. This didn't happen before the Sp2 application. We have used RPCPING from the resource kit (although I only used the -s flag and specified the GC in our domain) and rpcpings were replied too. So why then are we being refered to a GC outside our domain? All others GC's are in other domains, and therefore my domains GC should win the DSACCESS algorithm. All GC's in the forest are in 1 site. Any ideas?
The easiest way for me to replicate the problem is to create a new outlook 2003 profile, and click check names. The popup will always occur. This didn't happen before the Sp2 application. We have used RPCPING from the resource kit (although I only used the -s flag and specified the GC in our domain) and rpcpings were replied too. So why then are we being refered to a GC outside our domain? All others GC's are in other domains, and therefore my domains GC should win the DSACCESS algorithm. All GC's in the forest are in 1 site. Any ideas?