Dreaded -17900 error with Entourage and Exchange 2003

[mbm]

Still having SIGNIFICANT issues with Entourage... Wiped my installation and did a fresh install of Office 08... When connecting to Exchange server I get the dreaded -17900 error (bad username or password). Both are confirmed correct. I can login via OWA with no problem. I can login via IMAP with no problem. Try and login in Exchange mode to get calendars, global address etc and I get the error.

Exchange server is 2003. Thought it might be an Active Directory issue or something with the existing mail account. So I worked with IT and set up a new mail account with a new AD user. Clean install of Office 2008 again... Still get the -17900 error and can't get Entourage to access the server. OWA and IMAP work...

What the &*(^. It is unbelievable that a clean install of Entourage can't login to a clean account on Exchange server.

Any suggestions?!

 

[Diane Ross]

Still having SIGNIFICANT issues with Entourage... Wiped my installation and
did a fresh install of Office 08... When connecting to Exchange server I get
the dreaded -17900 error (bad username or password). Both are confirmed
correct. I can login via OWA with no problem. I can login via IMAP with no
problem. Try and login in Exchange mode to get calendars, global address etc
and I get the error.

Exchange server is 2003. Thought it might be an Active Directory issue or
something with the existing mail account. So I worked with IT and set up a new
mail account with a new AD user. Clean install of Office 2008 again... Still
get the -17900 error and can't get Entourage to access the server. OWA and
IMAP work...

What the &*(^. It is unbelievable that a clean install of Entourage can't
login to a clean account on Exchange server.

Any suggestions?!

Error -17099

Relaying to <the email address> prohibited by administrator Email could not
be sent Account name (my account name) Error -17099

Error -17099 is an Entourage error kSMTPServerReplyErr, and is returned when
the SMTP server has returned a permanent or transient error or returns an
unexpected result code.

This error is coming from your ISP.

Users have reported this error when sending to large groups. ISPs limit the
number in a group. Usual number is 50 recipients to avoid spammer misuse.
Entourage has no limit. You should contact your mail provider to ascertain
the maximum number of recipients per message and note it. You can use the
free "Split Recipients" script to send a mass e-mail in separate mailings
automatically:

Split Recipients for Entourage 2001

Split Recipients for Entourage X

Most ISPs also require you to use their SMTP address when sending.

 

[mbm]

You misread the error code.

It is -17900

NOT -17099

-17900 is "bad user name or password" even though EVERYTHING is correct (as confirmed with IMAP and OWA).

 

[Barry Wainwright]

You misread the error code.

It is -17900

NOT -17099

-17900 is "bad user name or password" even though EVERYTHING is correct (as
confirmed with IMAP and OWA).

Does your user name or password contain unusual characters, such as accented
characters (é, ö, ç etc.) or the Œ/¹ or Œ\¹ characters?

--
Barry Wainwright
Microsoft MVP (see <http://www.microsoft.com/mvp/> for details)
Visit the Entourage User¹s Weblog for Hints, tips and troubleshooting
information:
http://www.barryw.net/weblog/

 

[mbm]

No special characters... upper case letters, lower case letters and a few numbers...

 

[Diane Ross]

You misread the error code.

It is -17900

NOT -17099

-17900 is "bad user name or password" even though EVERYTHING is correct (as
confirmed with IMAP and OWA).

Sorry about that. I suggest monitoring the traffic between your Entourage
and your ISP. I should tell you exactly what is failing. It might seem a bit
complicated, but just follow the steps one at a time and you'll see what is
going on behind the scenes.

Test your network with tcpflow. Another application, EavesDrop, I ran into
recently that does the same thing but has a different interface.

<http://www.baurhome.net/software/eavesdrop/index.html>


Here are the short and simple instructions on using tcpflow:

1. Download the Mac OS X version here (freeware).

<http://web.archive.org/web/20020610050659/http://www2.entropy.ch/download/t
cpflow-0.20.dmg.gz>

2. When you install, you will not find a tcpflow window, nor an icon on
your dock. tcpflow is designed to work in the background.

3. To run the test for email, quit all other applications that might be
connecting to the internet like your browser, ftp client.

4. Copy/paste in this command in the Terminal or use the script ²tcpflow
activate² (see below):

sudo /usr/local/bin/tcpflow -i en0 -c

5. Now try to send an email and watch the traffic in the window of the
Terminal. You should see what is happening.

6. For an example see this page:

<http://www.entourage.mvps.org/troubleshoot/tcpflow.html#example>

Script to activate tcpflow:

Download this script and place it in your User's Script folder.

<http://www.entourage.mvps.org/downloads/scripts/tcpflow activate.zip>

Place the script here:

Users --> Library --> Script folder

If you activate the Script Menu in the Finder you can easily access the
script there. To activate the Script menu, go to your Applications folder in
the Finder. Select the AppleScript folder and open AppleScript Utility. ˆ
Show Script Menu in menu bar

Select the script to automatically start the Terminal with the correct
command. Enter your password and tcpflow will be activated. Next use
Entourage to send a test message.

Using the script makes it easy to use tcpflow for subsequent testing.

 

[mbm]

Unfortunately this is not with an ISP. This is across a LAN to an internal server and it still will not work. There is nothing between my computer and the server and nothing else would be causing this problem.