Outlook 2003 --cache mode--

[BBW]

I notices that one of the PCs in a remote office was running Office2002. I
upgraded it to Office 2003, which went fine. I loaded Outlook and it loaded
fine, could send/recieve emials. In Control Panel, EMail, User Profiles,
Change Mail Settings, I changed it to Cached.

Now Outlook doesn't load but does ask me for authentication from a server in
a different domain in the forest...? DCDiag is fine on the servers.

If i put it back to NOT cached, Outlook works fine...

Any thoughts....

 

[VanguardLH]

I notices that one of the PCs in a remote office was running Office2002. I
upgraded it to Office 2003, which went fine. I loaded Outlook and it loaded
fine, could send/recieve emials. In Control Panel, EMail, User Profiles,
Change Mail Settings, I changed it to Cached.

Now Outlook doesn't load but does ask me for authentication from a server in
a different domain in the forest...? DCDiag is fine on the servers.

If i put it back to NOT cached, Outlook works fine...

Any thoughts....

Well, do you actually connect to an Exchange server?

 

[BBW]

Well, do you actually connect to an Exchange server?

No I don't get connected in cached mode, only get conneted in non-cached
mode...?

Why would cached mode stop the connection.

 

[VanguardLH]

No I don't get connected in cached mode, only get conneted in non-cached
mode...?

Why would cached mode stop the connection.

Okay, I'll rephrase. Are you using or attempting to use Exchange as
your mail server?

Mentioning DCDiag does not equate to saying that you actually use
Exchange as the mail server. "This command-line tool [DCdiag] analyzes
the state of domain controllers in a forest or enterprise and reports
any problems to assist in troubleshooting." I see nothing mentioned for
command-line syntax that mentions that DCdiag includes any
troubleshooting for Exchange
(http://technet2.microsoft.com/windo...a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true).

Webcast on cached *Exchange* mode
http://support.microsoft.com/servic...n/wc030305/manifest.xml&WMPVer=11.0.5721.5230

Confusing is that you say Outlook doesn't load but asks you for
authentication. Um, how could Outlook be asking for authentication if
it didn't load? If you use the Mail applet in Control Panel to look at
the Exchange account defined that Outlook will use, did you specify the
correct Exchange server host?

 

[BBW]

No I don't get connected in cached mode, only get conneted in non-cached
mode...?

Why would cached mode stop the connection.

Okay, I'll rephrase. Are you using or attempting to use Exchange as
your mail server?

Mentioning DCDiag does not equate to saying that you actually use
Exchange as the mail server. "This command-line tool [DCdiag] analyzes
the state of domain controllers in a forest or enterprise and reports
any problems to assist in troubleshooting." I see nothing mentioned for
command-line syntax that mentions that DCdiag includes any
troubleshooting for Exchange
(http://technet2.microsoft.com/windo...a1e8-40cd-ae8a-7f52848a90f21033.mspx?mfr=true).

Webcast on cached *Exchange* mode
http://support.microsoft.com/servic...n/wc030305/manifest.xml&WMPVer=11.0.5721.5230

Confusing is that you say Outlook doesn't load but asks you for
authentication. Um, how could Outlook be asking for authentication if
it didn't load? If you use the Mail applet in Control Panel to look at
the Exchange account defined that Outlook will use, did you specify the
correct Exchange server host?

Yes Exchange 2K3 SP2.
While logged into the network, and loading Outlook 2K3sp2 in cache mode, it
prompts me to authenticate via a DC in another domain...?
I mentioned dcdiag to let you know that the DCs are ok so why be prompted to
go to another DC for authentican...?
Very strange, that is why I am looking for advise.

 

[VanguardLH]

...


Yes Exchange 2K3 SP2. While logged into the network, and loading
Outlook 2K3sp2 in cache mode, it prompts me to authenticate via a DC
in another domain...? I mentioned dcdiag to let you know that the DCs
are ok so why be prompted to go to another DC for authentican...?
Very strange, that is why I am looking for advise.

I wonder if Exchange is on a trusted DC to the PDC to which the
problematic host gets its authentication. If the DC is not trusted then
maybe that is why you are getting prompted for credentials to authorize
you can get there. This is a stretch since you say Outlook connects
okay when not in cached mode. Since cached mode relies on UDP to send
unsolicited packets between server and client, maybe you have something
blocking UDP as mentioned in the example KB articles at:

http://support.microsoft.com/kb/839226/en-us
http://support.microsoft.com/kb/325930/en-us

Those are iffy that they might apply or help you. The one at:

http://support.microsoft.com/kb/910346/en-us

seems like it might be more applicable to your situation. You also
mentioned that the problematic host is "remote". Are you connecting it
via VPN from the remote site to your corporate network? That brings up
a can of worms at to which subnet or security zone in your network that
host connects when it reaches you network and what traffic is allowed
from there to wherever is the Exchange server. You might also want to
look at:

http://support.microsoft.com/kb/910346/en-us

This is getting out of my league since I've never had to administer
domains. Might be something to ask in an Exchange newsgroup since this
group is really to discuss the client program and you're really having a
remote networking and/or Exchange problem.

 

[BBW]

I wonder if Exchange is on a trusted DC to the PDC to which the
problematic host gets its authentication. If the DC is not trusted then
maybe that is why you are getting prompted for credentials to authorize
you can get there. This is a stretch since you say Outlook connects
okay when not in cached mode. Since cached mode relies on UDP to send
unsolicited packets between server and client, maybe you have something
blocking UDP as mentioned in the example KB articles at:

http://support.microsoft.com/kb/839226/en-us
http://support.microsoft.com/kb/325930/en-us

Those are iffy that they might apply or help you. The one at:

http://support.microsoft.com/kb/910346/en-us

seems like it might be more applicable to your situation. You also
mentioned that the problematic host is "remote". Are you connecting it
via VPN from the remote site to your corporate network? That brings up
a can of worms at to which subnet or security zone in your network that
host connects when it reaches you network and what traffic is allowed
from there to wherever is the Exchange server. You might also want to
look at:

http://support.microsoft.com/kb/910346/en-us

This is getting out of my league since I've never had to administer
domains. Might be something to ask in an Exchange newsgroup since this
group is really to discuss the client program and you're really having a
remote networking and/or Exchange problem.

Problem fixed. He leave's the company next week. I am sure a rebuild will
fix it.

Thanks again.