Outlook 2003 won't connect with Exchange Sever 2000

  • Thread starter Thread starter Spike
  • Start date Start date
S

Spike

I just installed Office 2003 and tried to use Outlook 2003
to access my Exchange Server 2000 mail box. It won't
connect. I keep getting the error message

Task 'Microsoft Exchange Server' reported error
(0x8004011D) : 'The server is not available. Contact your
administrator if this condition persists.'

I still have Outlook 2002 installed on another machine in
the office and it can still access the same server and
mailbox without problems.

Please, anyone with any experience here? Thanks.
 
On the machine with OL2003, can you ping the Exchange server by name? Is
your network's DNS set up properly (all computers and servers pointing only
to the internal AD-integrated DNS server in their IP config)?
 
Have you tried creating a new mail profile? What is the authentication type
set to under the advanced tab of the Exchange server properties? Did you
enter the Exchange server with its FQDN in the server name?

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to the
Swen virus, all e-mails sent to my actual account will be deleted w/out
reading.

After searching google.groups.com and finding no answer
Spike <[email protected]> asked:

| I just installed Office 2003 and tried to use Outlook 2003
| to access my Exchange Server 2000 mail box. It won't
| connect. I keep getting the error message
|
| Task 'Microsoft Exchange Server' reported error
| (0x8004011D) : 'The server is not available. Contact your
| administrator if this condition persists.'
|
| I still have Outlook 2002 installed on another machine in
| the office and it can still access the same server and
| mailbox without problems.
|
| Please, anyone with any experience here? Thanks.
 
Yes, I did create a new mail profile. The default for
KEBROS/NTLM was selected but I've tried all the choices.

When I set up the new account and 'check names' the server
returns the proper information.

I've tried the FQDN in the server name and the IP address,
it converts back to the FQDN. Since it 'checks the name'
isn't it connecting?
 
Yes, I can ping the server by name. No, the network DNS is
not set up to the internal AD-intergrated DNS server.

Since the Exchange Server will 'check the name' when you
create a new profile, am I not talking to the server. It
underlines the user name and it will change it's name to
the FQDN even if I put in an IP address for it.
 
I am having similar problems when behind my home router. Connection works
fine with a dialup connection and on company LAN, but something is getting
blocked by my home router. I can VPN through the router to office LAN and it
connects ok. I have Universal PnP turned on now, but still will not connect.
Outlook 2002 worked fine.
 
Since you're using Active Directory, you don't want to have
external/Internet DNS servers specified in any of the server/workstation IP
configurations. Specify only the AD-integrated DNS server's IP address, and
in the DNS server properties on the server itself, set up forwarders to your
ISP's DNS servers.
 
I went back and checked and I do have the DNS server set
up the way you describe. When I do an IPconfig /all the
DNS server that is reported is my internal server.

The forwarders are set to the DNS servers of my ISP. It
must be working because everyone can get to URLs all over
the Internet.

Any other ideas?

It's trying to connect to the server down in the lower
right hand part of the window. It tries and when it fails
it justs displays a small message 'Disconnected'.
 
I've run into this same issue. As expected Microsoft has identified th
issue in a knowledge base, but hasn't given a solution. What I di
notice was that when I had caching turned on for the account I receive
that error and I couldn't get into the public folders. As soon as
turned off the caching option both of those issues went a way. I'
trying to figure out how they're related. MS's kb is #82412
 
ackdov said:
*I've run into this same issue. As expected Microsoft has identifie
the issue in a knowledge base, but hasn't given a solution. What
did notice was that when I had caching turned on for the account
received that error and I couldn't get into the public folders. A
soon as I turned off the caching option both of those issues went
way. I'm trying to figure out how they're related. MS's kb i
#824123 *
Click to expand...

If you are accessing the mail from VPN you may try to key in your mai
server IP in hosts file
 
Back
Top