Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
- Date: Tue, 21 Nov 2006 18:37:21 -0800
The MS guy just works diff hours is all.
Shawn O'Connor wrote:
Marina,.
Thanks for your interest and help so far. I guess we lost the microsoft guy.
FYI though -- You are wrong about http://fqdn/exchange not working from inside the network. I usually setup a subdomain like office.domainname.com on the DNS and use this address for the security certificate. It's been working great for years.
But I digress.
Thanks for clearing up how the http://fqdn...etc. stuff works -- I believe I posted how I was doing that pretty clearly in one of my previous posts. At least we are on the same page. And indeed, I don't get the error message "page not found". I never reported getting that message.
For the record, I am using the FQDN for the webcertificate -- and I did make the change you suggested in your first post to use the IP address, but that resulted in the same error message first reported.
And finally, instead of focusing on the FQDN which has been working for me for the past 4-5 years now, I'd like to see if we couldn't shift our focus to the error message. I provided a lot of detail about when the error occurs and when it does not early on.
As for the IUSR account, most websites use this accont as they are by default set for anonymous user access. In the case of RWW and OWA that is still true up to the point where one is prompted for a password, upon which they are then using integrated windows authentication. I mentioned the IUSR account as it may be that it is at this point that there may be an issue -- because it is prior to being prompted for a user account.
And most importantly, I'm mentioning the anonymous user account because I'm grasping at straws. And I'm posting to this forum because I'm hoping someone has some insight that can point me in the right direction.
Thanks again for your help.
--Shawn
Hi Shawn,
If you are on dynamic dns service, you should be using that FQDN for the
webcertificate.
From inside the network you use http://servername/exchange, from outside
https://fqdn/exchange. The http://fqdn/exchange will never work from inside
the network, you should indeed get the page not found.
Why are you mentioning the anonymous user account in IIS? Have you been
playing around in IIS?
- Follow-Ups:
- Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- From: Marina Roos [SBS-MVP]
- Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- References:
- RE: RWW: version=1 msgtype=status status=-3 message=Password Incorrec
- From: Steven Zhu [MSFT]
- RE: RWW: version=1 msgtype=status status=-3 message=Password Inco
- From: Shawn O'Connor
- RE: RWW: version=1 msgtype=status status=-3 message=Password Inco
- From: Shawn O'Connor
- RE: RWW: version=1 msgtype=status status=-3 message=Password Incorrec
- Prev by Date: Re: Replacement Server w old one as Backup Hardware
- Next by Date: Re: block image spams
- Previous by thread: Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- Next by thread: Re: RWW: version=1 msgtype=status status=-3 message=Password Inco
- Index(es):
Relevant Pages
|