I am in a Public College setting with a forest that includes 5 child
domains. When new Outlook 2003 profiles are created, and outlook is
launched (or check names is clicked in the profile setup) we get a
logon prompt for a Global Catalog server of another domain. I am
confused as to why the global catalog server in our domain isn't being
used. These logon prompts were not occuring before Exchange sp2 was
applied last week.

Packet captures seem to do not indicate any attempts to connect to our
DC. Any ideas?

I believe the opposite is supposed to happen. They did change the DSProxy
algorithm in Exchange 2003 sp2 so Outlook can be better served with a global
catalog server IN the same domain when possible.

I assume there are GCs in the same domains as the mailbox-enabled users?
Are the GCs in the same Active Directory Site as the Exchange servers?

wrote in message
ups.com...
I am in a Public College setting with a forest that includes 5 child
domains. When new Outlook 2003 profiles are created, and outlook is
launched (or check names is clicked in the profile setup) we get a
logon prompt for a Global Catalog server of another domain. I am
confused as to why the global catalog server in our domain isn't being
used. These logon prompts were not occuring before Exchange sp2 was
applied last week.

Packet captures seem to do not indicate any attempts to connect to our
DC. Any ideas?

I'm a server guy and don't realize you could be talking about Office 2003
sp2 versus Exchange 2003 sp2

"William [MVP]" wrote in message
...
I believe the opposite is supposed to happen. They did change the DSProxy
algorithm in Exchange 2003 sp2 so Outlook can be better served with a
global catalog server IN the same domain when possible.

I assume there are GCs in the same domains as the mailbox-enabled users?
Are the GCs in the same Active Directory Site as the Exchange servers?

wrote in message
ups.com...
I am in a Public College setting with a forest that includes 5 child
domains. When new Outlook 2003 profiles are created, and outlook is
launched (or check names is clicked in the profile setup) we get a
logon prompt for a Global Catalog server of another domain. I am
confused as to why the global catalog server in our domain isn't being
used. These logon prompts were not occuring before Exchange sp2 was
applied last week.

Packet captures seem to do not indicate any attempts to connect to our
DC. Any ideas?

Yes, I am speaking of Exchange sp2. The new algorith should be the
following, except it isnt working as it is supposed too:

Recall that with SP2, we score the desirability of a global catalog
based several constraints:

1. A GC that is available (RPC ping) - 16 points

2. A GC that supports the Clients protocol - 8 points

3. A GC belonging to the users domain - 4 points

4. A GC within the same AD site as the Exchange Server - 2
points

5. A GC that is one of the GCs that the Exchange Server is
currently using - 1 point

Our GC is in the same domain/site. We have tried using the rpcping
utility from the resouce kit (although I cant figure out what to use as
the endpoint/uuid of the GC) to the GC and it does reply.

Lost and confused ....

Is the GC it is using hardcoded somewhere?

You could try the Exchange Provider Closest GC reg entry. MS KB 319206

W

wrote in message
oups.com...
Yes, I am speaking of Exchange sp2. The new algorith should be the
following, except it isnt working as it is supposed too:

Recall that with SP2, we score the desirability of a global catalog
based several constraints:

1. A GC that is available (RPC ping) - 16 points

2. A GC that supports the Clients protocol - 8 points

3. A GC belonging to the users domain - 4 points

4. A GC within the same AD site as the Exchange Server - 2
points

5. A GC that is one of the GCs that the Exchange Server is
currently using - 1 point

Our GC is in the same domain/site. We have tried using the rpcping
utility from the resouce kit (although I cant figure out what to use as
the endpoint/uuid of the GC) to the GC and it does reply.

Lost and confused ....