Verification Failed: "Logon failure: unknown user name or bad password" (-17900 )
obsr...@gmail.com
(-17900 )
I have tried everything I can think of to get entourage working.
Anyone have any hints? OWA works from this system, ssl is turned on for
the account and I have the correct address to the owa server
(https://server.company.com/exchange) in the sedrver field. What is
the best way to verify webdav is operating properly? Is there anything
else anyone can think of?
What, exactly, does -17900 mean?
Is there any way to enable additional logging to figure out what the
heck is going on?
obsr...@gmail.com
BTW: the -17900 only comes up when doing the account verification. If
I try to manually set everything to the owa server, it still does not
work and gives me the same logon failure error but with no error codes.
Diane Ross
1164562331.8...@n67g2000cwd.googlegroups.com, "obsr...@gmail.com"
<obsr...@gmail.com> wrote:
> Verification Failed: "Logon failure: unknown user name or bad password"
> (-17900 )
>
> I have tried everything I can think of to get entourage working.
> Anyone have any hints? OWA works from this system, ssl is turned on for
> the account and I have the correct address to the owa server
> (https://server.company.com/exchange) in the sedrver field. What is
> the best way to verify webdav is operating properly? Is there anything
> else anyone can think of?
>
> What, exactly, does -17900 mean?
This is the description of error -17900:
<http://www.entourage.mvps.org/error/page.html#error-17099>
--
Diane Ross, Microsoft Mac MVP
Entourage Help Page
<http://www.entourage.mvps.org/>
The Entourage Blog lists the EHP as one of the top five Microsoft Entourage
resources.
<http://blogs.msdn.com/entourage/>
William Smith
obsr...@gmail.com wrote:
Try omitting the "https://" from your Exchange server address. This is
already being handled by the selection of the SSL checkbox.
If that doesn't work, logon with OWA with a browser and then copy the
entire string sans the "https://" and paste it into the Exchange server
field in Entourage.
Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP - Mac/Windows)
obsr...@gmail.com
William: Unfortuantely no luck. I tried both ways, without the https
(just server.com/exchange) and with the entire string that shows in
safari after logging in.
William Smith
obsr...@gmail.com wrote:
> William: Unfortuantely no luck. I tried both ways, without the https
> (just server.com/exchange) and with the entire string that shows in
> safari after logging in.
A bit of troubleshooting...
1. Do you get the same error message with a different Identity and a
different user account?
2. Do you have another Mac to test the same account?
obsrving
William Smith
"obsrving" <obsr...@gmail.com> wrote:
> Same error, and 4 macs in this house alone! :)
> > 2. Do you have another Mac to test the same account?
Since this is failing on all Macs then I'd say you've probably still got
something wrong in your account settings.
How about the Domain field in your Exchange account setup? Are you
trying to use something like "domain.com" or are you trying to use
something like "DOMAIN"? This field should be the same as your Windows
DOMAIN name (similar to what you'll find in the Domain field at the
bottom of a Windows login).
obsrving
I have tried both)
I decided to bring one mac into the office and I am able to directly
log into the exchange server using entourage without SSL, but not using
the OWA server even on the internal network. So it seems to be
specific to the OWA system somehow.
BTW: The OWA system requires SSL, so I cannot try it without that
option turned on.
Is there any way to turn on additional logging to figure out why it is
failing? Seems to me that should be fairly simple and show something
more than just logon failure.
Can I go to a webpage on the server to determine if webdav is available
properly and is allowing logins?
I really appreciate the help, and hopefully we can put this to bed
soon. I am sure others have similar issues and will find this
troubleshooting useful.
William Smith
"obsrving" <obsr...@gmail.com> wrote:
> It is correct. (both the domain.com and domain address are valid and
> I have tried both)
>
> I decided to bring one mac into the office and I am able to directly
> log into the exchange server using entourage without SSL, but not using
> the OWA server even on the internal network. So it seems to be
> specific to the OWA system somehow.
>
> BTW: The OWA system requires SSL, so I cannot try it without that
> option turned on.
>
> Is there any way to turn on additional logging to figure out why it is
> failing? Seems to me that should be fairly simple and show something
> more than just logon failure.
>
> Can I go to a webpage on the server to determine if webdav is available
> properly and is allowing logins?
>
> I really appreciate the help, and hopefully we can put this to bed
> soon. I am sure others have similar issues and will find this
> troubleshooting useful.
Glad you're at least making progress.
I don't know of any additional logging you can turn on or look for on
your computer. Office apps aren't the greatest about writing to local
log files. Someone else may have an answer for that. You can note the
dates and times you're trying to connect from home and ask your Exchange
administrator if he sees anything in his connection logs.
As for a web page, so long as you're able to access your account through
your company's OWA site then this is enough to use Entourage. When using
OWA does your company have any additional authentication process that
takes place prior to your login? Are you required to authenticate using
a SecurID token or something similar? Or do you simply log in once and
you're viewing your account?
obsrving
although it does ask for the type of system we are logging in on as a
radio button to set how long OWA will allow your login before auto
logging you out. I am assuming this is a modification of the basic
login form.
Is there any way to get around that with entourage? (Besides getting
access to the native form)
CostasM
William Smith wrote:
> I don't know of any additional logging you can turn on or look for on
> your computer. Office apps aren't the greatest about writing to local
> log files. Someone else may have an answer for that. You can note the
> dates and times you're trying to connect from home and ask your Exchange
> administrator if he sees anything in his connection logs.
In topic "Connection problems to Exchange after user account changes"
in this forum, it was suggested to use Interarchy to trace
communications on port 80 to see what is happening with Entourage.
CostasM
William Smith
"obsrving" <obsr...@gmail.com> wrote:
The only radio button option I'm familiar with is the one that asks if
you're connecting from a private or public computer. This simply keeps
some of your login information from being stored on the computer. Is
this what you mean? I do know that someone is able to use Entourage with
OWA configured this way.
If you're referring to something different then you may have found your
problem. Your administrator could possibly clue you in to what he's done.
obsrving
unfortunately. I just didn't realize that was a stock option.
CostsM: Wish I could, but it is ssl only. I need a way to watch the
transfer within entourage, not the actual data stream being
transmitted. This really should be a possibility, and I can't imagine
Microsoft wouldn't have that capacity in there even if it isn't
broadcast much.
obsrving
appears in safari after login into entourage again. Now I am getting a
new error since getting the sync going that once on the internal
network. Now with the full CookieAuth.dll?GetLogonWrapper?url....
string in there, I get a 170 error. The string includes the virtual
url name and username so I am not posting that information, but I did
copy and past that section. I tried it with and without my username,
and with my login id in the string vs username and a bunch of other
options. Nothing worked and continued getting me 170 errors.
Any chance that helps?
Can I point entourage directly at the dll it uses for login on only at
the general login page? If so, what is the normal address for that
dll?
I did search through the newsgroups for error 170 but I see only
references to exchange 5.5 that come close. We are using 2003 and not
5.5.
Rich
works for a few seconds and fails. I've tried many of the same things
you have.
I noticed it started happening after I installed the latest OS updates
from Apple this week. Could it be related?
Rich
Diane Ross
1165426028.7...@79g2000cws.googlegroups.com, "Rich"
<rich.co...@gmail.com> wrote:
Re-apply the Mac OS X 10.4.8 combo updater Once again, re-application of the
current combination updater (Mac OS X 10.4.8 for PowerPC or Intel) has
proven useful in the case of Security Update 2006-007. Doing so overwrites
potentially problem-causing files.
See MacFixIt for other solutions:
Troubleshooting Security Update 2006-007
<http://www.macfixit.com/index.php>
<http://www.macfixit.com/article.php?story=20061204233133704>
Look in the box on the right called What's Related for other links to update
problems.
obsrving
Unfortunately mine has not worked since before the latest update so
this has nothing to do with my original issue.
Diane: Have you seen concrete examples of this issue where applying
that specific fix a second time corrects this specific issue with
entourage? I have a hard time believing those kinds of fixes, as
Microsoft seems to quote that logic over and over. Many of the times I
have worked with them they say to try it again because "it worked once
before" but on an issue that had nothing to do with the current setup.
This seems to relate to safari, and I am assuming entourage uses its
own system to talk the OWA server.
Sorry if I am being critical, but I am frustrated and want to know
specifics about what is not working.
Someone has to know, how do we turn on additional logging?
Diane Ross
From a previous message you said:
> CostsM: Wish I could, but it is ssl only. I need a way to watch the
> transfer within entourage, not the actual data stream being
> transmitted. This really should be a possibility, and I can't imagine
> Microsoft wouldn't have that capacity in there even if it isn't
> broadcast much.
Download the Mac OS X versions here.
<http://www2.entropy.ch/download/tcpflow-0.21.pkg.tar.gz> (Mac OS X 10.3.x / Panther)
<http://www2.entropy.ch/download/tcpflow-0.20-jaguar.pkg.tar.gz> (Mac OS 10.2 / Jaguar)
Really short version on using tcpflow;
When you install, you do not see an application.
To run the test for email, quit all other apps that might be connecting to the internet like your browser, ftp client.
Copy/paste in this command in the Terminal:
sudo /usr/local/bin/tcpflow -i en0 -c
Now try to send the email and watch the traffic in the window of the Terminal. You should see what is failing.
I use use this script to activate tcpflow (easy for multiple use):
activate
tell application "Terminal"
activate
do script with command "sudo /usr/local/bin/tcpflow -i en0 -c"
end tell
Keep the script in your User’s --> Preferences --> Script folder.
--
Diane
> Organization: http://groups.google.com
> Newsgroups: microsoft.public.mac.office.entourage
> Date: 7 Dec 2006 05:55:27 -0800
> Subject: Re: Verification Failed: "Logon failure: unknown user name or bad
> password" (-17900 )
>
>
obsrving
other people it seems) need something internal to entourage to tell us
why it is erroring out.
Diane Ross wrote:
> I thought you reported it started AFTER the update. Sorry about the
> confusion. The info on reapplying the update came from MacFixIt not
> Microsoft. One other thought on the problem is to try a different browser
> than Safari.
>
> --B_3248345057_2543635
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 6150
>
> <HTML>
> <HEAD>
> <TITLE>Re: Verification Failed: "Logon failure: unknown user name or bad password" (-17900 )</TITLE>
> </HEAD>
> <BODY>
> <FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>I thought you reported it started AFTER the update. Sorry about the confusion. The info on reapplying the update came from MacFixIt not Microsoft. One other thought on the problem is to try a different browser than Safari.<BR>
> <BR>
> From a previous message you said:<BR>
> > CostsM: Wish I could, but it is ssl only. I need a way to watch the<BR>
> > transfer within entourage, not the actual data stream being<BR>
> > transmitted. This really should be a possibility, and I can't imagine<BR>
> > Microsoft wouldn't have that capacity in there even if it isn't<BR>
> > broadcast much.<BR>
> <BR>
> Try using tcpflow to watch the traffic between Entourage and your server.<BR>
> <BR>
> Download the Mac OS X versions here.<BR>
> <BR>
> <a href="http://www2.entropy.ch/download/tcpflow-0.21.pkg.tar.gz"><http://www2.entropy.ch/download/tcpflow-0.21.pkg.tar.gz></a> (Mac OS X 10.3.x / Panther)<BR>
> <BR>
> <a href="http://www2.entropy.ch/download/tcpflow-0.20-jaguar.pkg.tar.gz"><http://www2.entropy.ch/download/tcpflow-0.20-jaguar.pkg.tar.gz></a> (Mac OS 10.2 / Jaguar)<BR>
> <BR>
> Really short version on using tcpflow;<BR>
> <BR>
> </SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>When you install, you do not see an application.<BR>
> <BR>
> To run the test for email, quit all other apps that might be connecting to the internet like your browser, ftp client.<BR>
> <BR>
> Copy/paste in this command in the Terminal:<BR>
> <BR>
> sudo /usr/local/bin/tcpflow -i en0 -c<BR>
> <BR>
> Now try to send the email and watch the traffic in the window of the Terminal. You should see what is failing.<BR>
> </SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
> I use use this script to activate tcpflow (easy for multiple use):<BR>
> <BR>
> <FONT COLOR="#0000FF">activate<BR>
> <B>tell</B></FONT> <FONT COLOR="#0000FF">application</FONT> "Terminal"<BR>
> <FONT COLOR="#0000FF">activate<BR>
> </FONT> <FONT COLOR="#0000FF">do script</FONT> <FONT COLOR="#0000FF">with command</FONT> "sudo /usr/local/bin/tcpflow -i en0 -c"<BR>
> <FONT COLOR="#0000FF"><B>end</B></FONT> <FONT COLOR="#0000FF"><B>tell<BR>
> </B></FONT><BR>
> Keep the script in your User’s --> Preferences --> Script folder.<BR>
> <BR>
> -- <BR>
> Diane <BR>
> <BR>
> <FONT COLOR="#0000FF">> From: obsrving <obsr...@gmail.com><BR>
> > Organization: <a href="http://groups.google.com">http://groups.google.com</a><BR>
> > Newsgroups: microsoft.public.mac.office.entourage<BR>
> > Date: 7 Dec 2006 05:55:27 -0800<BR>
> > Subject: Re: Verification Failed: "Logon failure: unknown user name or bad <BR>
> > password" (-17900 )<BR>
> > <BR>
> > <BR>
> > Unfortunately mine has not worked since before the latest update so<BR>
> > this has nothing to do with my original issue.<BR>
> > <BR>
> > Diane: Have you seen concrete examples of this issue where applying<BR>
> > that specific fix a second time corrects this specific issue with<BR>
> > entourage? I have a hard time believing those kinds of fixes, as<BR>
> > Microsoft seems to quote that logic over and over. Many of the times I<BR>
> > have worked with them they say to try it again because "it worked once<BR>
> > before" but on an issue that had nothing to do with the current setup.<BR>
> > This seems to relate to safari, and I am assuming entourage uses its<BR>
> > own system to talk the OWA server.<BR>
> > <BR>
> > Sorry if I am being critical, but I am frustrated and want to know<BR>
> > specifics about what is not working.<BR>
> > <BR>
> > Someone has to know, how do we turn on additional logging?<BR>
> > <BR>
> > Diane Ross wrote:<BR>
> </FONT><FONT COLOR="#008000">>> On 12/6/06 9:27 AM, in article<BR>
> >> 1165426028.7...@79g2000cws.googlegroups.com, "Rich"<BR>
> >> <rich.co...@gmail.com> wrote:<BR>
> >> <BR>
> </FONT><FONT COLOR="#FF0000">>>> Any luck? I just started having this same problem this week. Mine<BR>
> >>> works for a few seconds and fails. I've tried many of the same things<BR>
> >>> you have.<BR>
> >>> <BR>
> >>> I noticed it started happening after I installed the latest OS updates<BR>
> >>> from Apple this week. Could it be related?<BR>
> </FONT><FONT COLOR="#008000">>> <BR>
> >> Re-apply the Mac OS X 10.4.8 combo updater Once again, re-application of the<BR>
> >> current combination updater (Mac OS X 10.4.8 for PowerPC or Intel) has<BR>
> >> proven useful in the case of Security Update 2006-007. Doing so overwrites<BR>
> >> potentially problem-causing files.<BR>
> >> <BR>
> >> See MacFixIt for other solutions:<BR>
> >> <BR>
> >> Troubleshooting Security Update 2006-007<BR>
> >> <BR>
> >> <a href="http://www.macfixit.com/index.php"><http://www.macfixit.com/index.php></a><BR>
> >> <BR>
> >> <a href="http://www.macfixit.com/article.php?story=20061204233133704"><http://www.macfixit.com/article.php?story=20061204233133704></a><BR>
> >> <BR>
> >> Look in the box on the right called What's Related for other links to update<BR>
> >> problems.<BR>
> >> <BR>
> >> --<BR>
> >> Diane Ross, Microsoft Mac MVP<BR>
> >> Entourage Help Page<BR>
> >> <a href="http://www.entourage.mvps.org/"><http://www.entourage.mvps.org/></a><BR>
> >> The Entourage Blog lists the EHP as one of the top five Microsoft Entourage<BR>
> >> resources. <BR>
> >> <a href="http://blogs.msdn.com/entourage/"><http://blogs.msdn.com/entourage/></a><BR>
> </FONT><FONT COLOR="#0000FF">> <BR>
> </FONT></SPAN></FONT>
> </BODY>
> </HTML>
>
>
> --B_3248345057_2543635--
obsrving
to troubleshoot this?
Are there absolutely NO user accessable logs produced by entourage?
iw8s...@gmail.com
and log me in to the server? All I get is authorization failed
(#5.7.0.) I have set the default account to be used which initially was
successful in logging on to the server. After readiing all of these
posts I have little encourgement in the program ever doing what it was
created to do. listeng to the terminology I feel very ignorant trying
to make progress solving this issue.
Ray
Townsend@discussions.microsoft.com Peter Townsend
I am having the same problem, on my new Mac. My E-mail works perfectly well
but my wife’s gives the error message 17900. I’ve checked doubled checked
and tripled checked and her settings are all sets the same as my account.
I’ve checked the details with my service provider and heard details are
correct.
I am new to Mac computers, as this is the first Mac I have hand.
If you could help solve this problem for me, I’ll be most grateful.
Thank you
Peter Townsend
obsrving
is she? Same computer? OWA? etc. Sorry, I understand you are new at
this but you need to include more details to get us to help.
If it is OWA, try doing it through safari and tell us if you see
cookieauth.dll in the website string during login. If you do, you are
screwed my friend. Microsoft's mac group, in their infinite wisdom,
decided not to include a way to log into the default configuration of
exchange 2003's front end servers. The only way to fix the situation
is have your IT groups change the way they configure the servers.
Check my other posts for the link to Microsoft's site with the
details.
Of course the windows mobile devices work just fine with
cookieauth.dll, so this is purely the macbu not noticing a glaring
error or the people from higher up making sure that entourage has
small but significant issues in it, keeping as many users as possible
on the windows alternatives.
On Feb 9, 10:07 am, Peter Townsend <Peter
manuela...@gmail.com
I checked all settings and am sure they are correct. I have created a new account which worked for a while but stopped working this morning. Someone else in my family uses the same Mac, with a different Google Account but using the same settings and all works fine.
Hopefully someone can help.
Thx