D
dln
Hi. Our site has recently upgraded to using Office 2003 on Windows XP and
we connect to Exchange 2003. I have run into a couple of instances where
the Outlook client will not connect to the Exchange server and Outlook
reports "Your Exchange server is unavailable". This problem appears to be
profile related and not a DNS error.
Until recently, all of the users at my site were using peer-to-peer
networking. A few weeks ago, we started upgrading people to the domain
model. The Exchange connectivity problem occurs with people who have not
yet moved into the domain and are trying to connect to the new Exchange 2003
server (our site has an older Exchange 2000 server and a new install of
Exchange 2003). Once we move the system into the domain, the connectivity
problem goes away. However, once we copy the user's local profile over to
the domain profile, the connectivity problem returns. If we log out and log
back in as different domain account (thereby forcing a new profile creation
for that user), we can connect to the Exchange server as any user in the
domain.
So based on this, I'm begining to think that there is an artifact left over
from the local user profile that is creating the connectivity problem. So
far I've tried reconfiguring mail support through both Outlook and the Mail
applet in the Control Panel. I've attempted to reconfigure the existing
account and also completely removed the account, rebooted and then tried to
re-add the account. Nothing has worked so far and nothing is logged in the
Event logs of either the client machine or the Exchange server. Does
anybody have any ideas as to why I'm getting the connectivity problem and
what I can do to solve it?
Thanks.
we connect to Exchange 2003. I have run into a couple of instances where
the Outlook client will not connect to the Exchange server and Outlook
reports "Your Exchange server is unavailable". This problem appears to be
profile related and not a DNS error.
Until recently, all of the users at my site were using peer-to-peer
networking. A few weeks ago, we started upgrading people to the domain
model. The Exchange connectivity problem occurs with people who have not
yet moved into the domain and are trying to connect to the new Exchange 2003
server (our site has an older Exchange 2000 server and a new install of
Exchange 2003). Once we move the system into the domain, the connectivity
problem goes away. However, once we copy the user's local profile over to
the domain profile, the connectivity problem returns. If we log out and log
back in as different domain account (thereby forcing a new profile creation
for that user), we can connect to the Exchange server as any user in the
domain.
So based on this, I'm begining to think that there is an artifact left over
from the local user profile that is creating the connectivity problem. So
far I've tried reconfiguring mail support through both Outlook and the Mail
applet in the Control Panel. I've attempted to reconfigure the existing
account and also completely removed the account, rebooted and then tried to
re-add the account. Nothing has worked so far and nothing is logged in the
Event logs of either the client machine or the Exchange server. Does
anybody have any ideas as to why I'm getting the connectivity problem and
what I can do to solve it?
Thanks.