Yet another outlook 2001 help request

[johnny t]

I see lots of help with the first step of connecting to an exchange
server - but after setting up my hosts file, and using the "Test
Connection..." - I got past the first step. The next step was the
login dialog to the exchange server. After entering my name, domain,
and password, I get the following error:

The logon credentials supplied were incorrect. Make sure your username
and domain are correct, then type your password again.

Now this is strange because I have no problems logging into our NT
Domain when mounting a samba share. I have quadruple verified that I
am entering the right username, password, and domain but nothing
works.

Note: I was actually waiting patiently for Entourage X Exchange
support, but was hopelessly disappointed when I found out it only
supports Exchange 2000 (we are running Exchange 5.5). This sucks!

Here is my hosts file in OS 9 (BTW, I get the same behavior in OS 9
and OS X classic mode):

srvr CNAME srvr.corp.company.com ; where srvr is the name of exchange
server
srvr.corp.company.com A 10.6.1.15


I am not sure the hosts file is correct, but this is the only setting
in which I have been able to successfully ping the exchange server
using only its name, and also get past the first step of setting up
Outlook 2001.

Any help would be appreciated!

-johnny

 

[William M. Smith]

Hi johnny!

My comments are inline with yours.

The logon credentials supplied were incorrect. Make sure your username
and domain are correct, then type your password again.

Now this is strange because I have no problems logging into our NT
Domain when mounting a samba share. I have quadruple verified that I
am entering the right username, password, and domain but nothing
works.

Are you trying to use your Exchange email name as your logon name or are you
using your Windows NT logon name? It should be your Windows NT logon name.

For example, my logon name for our Windows NT server running Exchange 5.5 is
"William Smith", but my Exchange account name is "william.smith". I must use
"William Smith".

Note: I was actually waiting patiently for Entourage X Exchange
support, but was hopelessly disappointed when I found out it only
supports Exchange 2000 (we are running Exchange 5.5). This sucks!

Our servers at work are still running 5.5 too and it would be nice to have
the new Entourage work with them, but in all fairness to Microsoft their
announcement in February stated that the new update would support Exchange
2000 or later.

Here is my hosts file in OS 9 (BTW, I get the same behavior in OS 9
and OS X classic mode):

srvr CNAME srvr.corp.company.com ; where srvr is the name of exchange
server
srvr.corp.company.com A 10.6.1.15


I am not sure the hosts file is correct, but this is the only setting
in which I have been able to successfully ping the exchange server
using only its name, and also get past the first step of setting up
Outlook 2001.

Your Hosts file is fine from what I see. Have you verified the IP address?
Keep in mind that any changes you make to the Hosts file while running in
Classic will require you to restart Classic to reload the informaiton. Also,
be sure to use SimpleText and not TextEdit to change a Hosts file. TextEdit
by default will save in rich text format.

Hope this helps! bill

 

[William M. Smith]

Hi johnny!

Again, my comments are inline with yours.

The way I verify the hosts file is to use a "ping" app to ping the
exchange server only using its server name and not the FQDN. Sinced
this worked, and the first step of setting up my Outlook account on
the Mac worked, I assumed that everything was setup correctly. I use
BBEdit for text editing, so rtf shouldn't be a problem.

If you have a functioning DNS server, which allows you to ping by name, then
you shouldn't need a Hosts file.

Try this:

1.) Quit the Classic environment
2.) Open your System Folder and MOVE the TCP/IP Preferences file from the
Preferences folder. Keep in in case this doesn't work and you can put it
back later.
3.) Try Outlook again using just the server name and not the FQDN.

Overall, I am quite happy with most of the M$ MacBU products and can't
blame them for not supporting an outdated product (Exchange 5.5). My
frustration is mostly from my overall disappointment in the exchange
product itself as well as my IT deparments lack of Mac support. I just
wish someone would develop the ultimate cross-platform collaboration
product...

Kudos to any I/T department that acknowledges Macs are a necessity in some
parts of business and supports them. I don't understand how someone can
justify the business decision to use Macs to their superiors, but I/T won't
acknowledge them as a business need and can get away with it.

The ultimate cross-platform collaboration product... hmmm. Million dollar
idea!

bill