C
Chris
I use Outlook 2003 on a Windows XP Professional to
connect to Microsoft Exchange Server 2000. We have
approximately 30 users connected to our exchange server
and my computer is the only one so far that is using
Outlook 2003. Everyone else is using previous versions of
Outlook on Windows 98 and XP Professional.
Periodically duing the day (10 to 20 times) Outlook
will "disconnect" from the Exchange Server and then
prompt me for a domain login. When I get this login
screen I opened up my computer and verified that I CAN
browse my network drives so I know that my computer is
not completely disconnected from the network. At this
point, I can log back in and Outlook will reconnect with
the Exchange Server.
I have checked the network layer (swapped cables, updated
network card drivers, changed network cards, moved to a
different switch, etc) and don't believe that is the
problem. None of this seems to help. I've also scoured
the newsgroups to see if others are having similar
problems but can't find anything related.
I do have a couple of event log entries that seem to be
related to the problem. The system log reports event ids
40960 and 40961 and the application log reports event id
26.
connect to Microsoft Exchange Server 2000. We have
approximately 30 users connected to our exchange server
and my computer is the only one so far that is using
Outlook 2003. Everyone else is using previous versions of
Outlook on Windows 98 and XP Professional.
Periodically duing the day (10 to 20 times) Outlook
will "disconnect" from the Exchange Server and then
prompt me for a domain login. When I get this login
screen I opened up my computer and verified that I CAN
browse my network drives so I know that my computer is
not completely disconnected from the network. At this
point, I can log back in and Outlook will reconnect with
the Exchange Server.
I have checked the network layer (swapped cables, updated
network card drivers, changed network cards, moved to a
different switch, etc) and don't believe that is the
problem. None of this seems to help. I've also scoured
the newsgroups to see if others are having similar
problems but can't find anything related.
I do have a couple of event log entries that seem to be
related to the problem. The system log reports event ids
40960 and 40961 and the application log reports event id
26.