> We have a Web site for staff use, which we maintain on a Windows 2003 Server
> (SE, SP2).  The Default Web Site properties have Authentication set as
> follows:  "Enable anonymous access" is unchecked; "Integrated Windows" and
> "Basic" authentication are checked, and our AD Windows domain (call it
> ourdomain.org) is entered as the Default Domain and Realm.  Seems all OK to
> me.  
> Because this Web site is for staff use only, we do not use our primary
> organization's domain name as the URL; instead we have set upwww.specialdomain.orgto point to this server.  
> When our users browse to our Web site from the Internet (i.e. not within our
> LAN) they are invited to log on, and they can log on with their full email
> address ("u***@ourdomain.org" and their regular Windows logon password.  BUT
> if they don't get it right the first time, they are "prompted" with the
> username "u***@specialdomain.org", which is dead wrong.  Of course, staff are
> inclined to accept whatever is filled in for them, so they try repeatedly to
> log on with this impossible username.
> Is there any way within IIS to control what appears as the prompt to folks
> attempting to log on?  
> Failing that, can anybody suggest any way to help my users avoid this trap?  
> Thanks, and happy holidays!

"DaveMo" wrote:

> On Dec 24, 3:40 pm, David H. <dav***@newspostalias.com> wrote:
> > We have a Web site for staff use, which we maintain on a Windows 2003 Server
> > (SE, SP2).  The Default Web Site properties have Authentication set as
> > follows:  "Enable anonymous access" is unchecked; "Integrated Windows" and
> > "Basic" authentication are checked, and our AD Windows domain (call it
> > ourdomain.org) is entered as the Default Domain and Realm.  Seems all OK to
> > me. 
> > Because this Web site is for staff use only, we do not use our primary
> > organization's domain name as the URL; instead we have set upwww.specialdomain.orgto point to this server. 
> > When our users browse to our Web site from the Internet (i.e. not within our
> > LAN) they are invited to log on, and they can log on with their full email
> > address ("u***@ourdomain.org" and their regular Windows logon password.  BUT
> > if they don't get it right the first time, they are "prompted" with the
> > username "u***@specialdomain.org", which is dead wrong.  Of course, staff are
> > inclined to accept whatever is filled in for them, so they try repeatedly to
> > log on with this impossible username.
> > Is there any way within IIS to control what appears as the prompt to folks
> > attempting to log on? 
> > Failing that, can anybody suggest any way to help my users avoid this trap? 
> > Thanks, and happy holidays!
>
> Odd behaviors such as this are usually what cause people to implement
> forms-based authentication for outward-facing sites.
>
> Dave
>

> That works very well for OWA, I agree.  I'm not sure how I would get started
> implementing it for a "regular" IIS Web site.  I guess the first step would
> be getting an SSL key for it.  I wouldn't know what to do after that.  Well,
> I guess my users will survive...
>
>
>
> "DaveMo" wrote:
> > On Dec 24, 3:40 pm, David H. <dav***@newspostalias.com> wrote:
> > > We have a Web site for staff use, which we maintain on a Windows 2003 Server
> > > (SE, SP2).  The Default Web Site properties have Authentication set as
> > > follows:  "Enable anonymous access" is unchecked; "Integrated Windows" and
> > > "Basic" authentication are checked, and our AD Windows domain (call it
> > > ourdomain.org) is entered as the Default Domain and Realm.  Seems all OK to
> > > me.  
> > > Because this Web site is for staff use only, we do not use our primary
> > > organization's domain name as the URL; instead we have set upwww.specialdomain.orgtopoint to this server.  
> > > When our users browse to our Web site from the Internet (i.e. not within our
> > > LAN) they are invited to log on, and they can log on with their full email
> > > address ("u***@ourdomain.org" and their regular Windows logon password.  BUT
> > > if they don't get it right the first time, they are "prompted" with the
> > > username "u***@specialdomain.org", which is dead wrong.  Of course, staff are
> > > inclined to accept whatever is filled in for them, so they try repeatedly to
> > > log on with this impossible username.
> > > Is there any way within IIS to control what appears as the prompt to folks
> > > attempting to log on?  
> > > Failing that, can anybody suggest any way to help my users avoid this trap?  
> > > Thanks, and happy holidays!
>
> > Odd behaviors such as this are usually what cause people to implement
> > forms-based authentication for outward-facing sites.
>
> > Dave- Hide quoted text -
>
> - Show quoted text -