B
Ben
Hi,
We've been using Exchange 2003 & Outlook 2003 successfully for about 4
years now. We've never had any real issues, and it’s been working
well.
However, for some reason since Friday we've been getting communication
problems between Exchange & Outlook. Yesterday I had a user complain
that Outlook always opens in 'Work Offline' mode, no matter what mode
you set it to be before closing. If you click the connection status
menu bar in the bottom right corner of Outlook, you can untick 'Work
Offline' and Outlook connects, and sends/receives mail without any
problem. I thought it might be a corrupt profile, so I tried setting
up a new profile for the user, but found that I receive an error
message 'Name could not be resolved. Operation failed.' Usually we
just enter exchange.domain.com & Joe Bloggs, and it resolves almost
instantly, so I tried entering the server name & user name in every
variation possible, just host name, full DNS name, i.e. exchange,
exchnage.domain.com, user display name & full user name with prefix,
i.e. Joe Bloggs, joe.bloggs, domain\joe.bloggs etc. Still nothing! In
the end I left the user with the old profile, and told them I'd look
into it.
However, now this morning I have come in, and found that my Outlook is
opening in offline mode by default as well, although as before, I can
untick 'work offline' and Outlook connects & sends/receives fine. Also
my 2nd mailbox (helpdesk) wasn't opening; I think the error message
was 'mailbox unavailable' or something. So I edited my Outlook
account, removed the mailbox from the 'advanced' > 'open additional
mailbox' tab, then tried to add it again. However, I now receive the
same 'Name could not be resolved. Operation failed' error message as
our other user.
I've tried rebooting the exchange server, changing the default
language to UK English (which I read in MS KB 838800 could fix the
issue), but still the problem persists.
Could anyone shed any light on the issue, or provide a possible fix?
We're running Windows 2003 Server Standard Edition SP2, Exchange 2003
SP2 Standard Edition, clients are Windows XP SP3, Office/Outlook 2003
SP3 (v11.8169.8172).
Many thanks
Ben
We've been using Exchange 2003 & Outlook 2003 successfully for about 4
years now. We've never had any real issues, and it’s been working
well.
However, for some reason since Friday we've been getting communication
problems between Exchange & Outlook. Yesterday I had a user complain
that Outlook always opens in 'Work Offline' mode, no matter what mode
you set it to be before closing. If you click the connection status
menu bar in the bottom right corner of Outlook, you can untick 'Work
Offline' and Outlook connects, and sends/receives mail without any
problem. I thought it might be a corrupt profile, so I tried setting
up a new profile for the user, but found that I receive an error
message 'Name could not be resolved. Operation failed.' Usually we
just enter exchange.domain.com & Joe Bloggs, and it resolves almost
instantly, so I tried entering the server name & user name in every
variation possible, just host name, full DNS name, i.e. exchange,
exchnage.domain.com, user display name & full user name with prefix,
i.e. Joe Bloggs, joe.bloggs, domain\joe.bloggs etc. Still nothing! In
the end I left the user with the old profile, and told them I'd look
into it.
However, now this morning I have come in, and found that my Outlook is
opening in offline mode by default as well, although as before, I can
untick 'work offline' and Outlook connects & sends/receives fine. Also
my 2nd mailbox (helpdesk) wasn't opening; I think the error message
was 'mailbox unavailable' or something. So I edited my Outlook
account, removed the mailbox from the 'advanced' > 'open additional
mailbox' tab, then tried to add it again. However, I now receive the
same 'Name could not be resolved. Operation failed' error message as
our other user.
I've tried rebooting the exchange server, changing the default
language to UK English (which I read in MS KB 838800 could fix the
issue), but still the problem persists.
Could anyone shed any light on the issue, or provide a possible fix?
We're running Windows 2003 Server Standard Edition SP2, Exchange 2003
SP2 Standard Edition, clients are Windows XP SP3, Office/Outlook 2003
SP3 (v11.8169.8172).
Many thanks
Ben