From: DP on
We're running Outlook 2007, Communicator 2007, and Exchange 2007.

Each morning our XP users are prompted for their domain user credentials to
log into Outlook/MS Communicator. We believe it's the integration between
Communicator & Outlook, but we're not 100% sure.
If a user shuts down both Outlook & MOC at night, then they won't see the
login prompt in the morning, even after restarting the apps. If they only
shut down either only Outlook or only MOC, then the login prompt will appear.
And if both apps are left running overnight, the login will appear in the
morning.

This only started occurring only within the last few months, and we've had
these 2 programs running for a while before that. We did do some
administrative work on the Exchange side since then.
Is it possible this issue has to do with Autodiscovery or Public Folders?

We'll be glad to provide further info if needed. Thanks in advance.
From: John Oliver, Jr. [MVP] on
On the Outlook/Exchange side of the issue, anything in the Exchange event
log if you type in wrong login info? This would at least confirm it's a
Autodiscovery issue. You could also run the Outlook- Test Email
Autoconfiguration from the Taskbar of the local client to see if its
Outlook/Exchange issue.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2010
Microsoft Certified Partner


"DP" <DP(a)discussions.microsoft.com> wrote in message
news:06D6A90A-83B0-48B1-8CD2-65FC73672CA2(a)microsoft.com...
> We're running Outlook 2007, Communicator 2007, and Exchange 2007.
>
> Each morning our XP users are prompted for their domain user credentials
> to
> log into Outlook/MS Communicator. We believe it's the integration between
> Communicator & Outlook, but we're not 100% sure.
> If a user shuts down both Outlook & MOC at night, then they won't see the
> login prompt in the morning, even after restarting the apps. If they only
> shut down either only Outlook or only MOC, then the login prompt will
> appear.
> And if both apps are left running overnight, the login will appear in the
> morning.
>
> This only started occurring only within the last few months, and we've had
> these 2 programs running for a while before that. We did do some
> administrative work on the Exchange side since then.
> Is it possible this issue has to do with Autodiscovery or Public Folders?
>
> We'll be glad to provide further info if needed. Thanks in advance.