Ok, a bit of a tricky one for me.

Environment:
Windows 2003 Server SP1 (brand new install)
FP Extensions 2002

I can log into admin just fine on the default web.  But it fails when I try
to log into newly created webs.  No matter if I am using the local admin
account or the domain admin account or any other account, the login screen
just flashes and says invalid login.  The last part of the equation, I am
doing this from a terminal services session.

The twist:
When I do this from any other workstation, it all works fine.  I can
administer it just fine.

What I've tried:
Removing, rebooting, re-installing FP 2002 Extensions.  Checked to make sure
there were no IP restrictions.  Checked to make sure the personal fiirewall
wasn't enabled.

Anybody know what I'm missing?

[ Post a follow-up to this message ]

I have a Win 2003 SP1 / IIS 6.0 / FPSE 2002 as well.  I had the same problem
EXCEPT I could not access the website admin from another workstation.  By
pure mistake, I found a solution.  However I want to be sure this does not
compromise security to my websites and my server as the follwing procedure
did popup a security message.

My websites by default were ALL set to "Integrated Windows Authentication"
I changed that to "Basic Authentication (Password sent in clear text)" and
WAHLLAH! I can get in now.  This was a real head banger for me and glad to
have a solution since knowone seemed to know what was causing this.

This is what I did:

Right click on the website from inside IIS:  Select Properties/Directory
Security Tab/Edit Button/
Uncheck - "Integrated Windows Authentication"
Check    - "Basic Authentications (Password sent in clear text)"

I would however like others to comment on the potential security issue this
authentiocation mode change raises.
Is FPSE supposed to be in Windows Authentication mode?
OR is not being able to use Windows Authentication indicitive of another
underlying problem?

I did not have this issue with my previous server that was re-build for
other reasons.  Only after a fresh OS install this this issues consistantly
occure with ALL my websites.

Hope this helps you!
Jody

"Kevin Antel" wrote:

> Ok, a bit of a tricky one for me.
>
> Environment:
> Windows 2003 Server SP1 (brand new install)
> FP Extensions 2002
>
> I can log into admin just fine on the default web.  But it fails when I tr
y
> to log into newly created webs.  No matter if I am using the local admin
> account or the domain admin account or any other account, the login screen
> just flashes and says invalid login.  The last part of the equation, I am
> doing this from a terminal services session.
>
> The twist:
> When I do this from any other workstation, it all works fine.  I can
> administer it just fine.
>
> What I've tried:
> Removing, rebooting, re-installing FP 2002 Extensions.  Checked to make su
re
> there were no IP restrictions.  Checked to make sure the personal fiirewal
l
> wasn't enabled.
>
> Anybody know what I'm missing?
>
>
>

[ Post a follow-up to this message ]

Try setting the security settings on the IE browser to low... this seems to
of corrected a somewhat similar issue for me.


"Kevin Antel" <kevina@cqlcorp.com> wrote in message
news:ONNlseUtFHA.3628@TK2MSFTNGP14.phx.gbl...
> Ok, a bit of a tricky one for me.
>
> Environment:
> Windows 2003 Server SP1 (brand new install)
> FP Extensions 2002
>
> I can log into admin just fine on the default web.  But it fails when I
> try to log into newly created webs.  No matter if I am using the local
> admin account or the domain admin account or any other account, the login
> screen just flashes and says invalid login.  The last part of the
> equation, I am doing this from a terminal services session.
>
> The twist:
> When I do this from any other workstation, it all works fine.  I can
> administer it just fine.
>
> What I've tried:
> Removing, rebooting, re-installing FP 2002 Extensions.  Checked to make
> sure there were no IP restrictions.  Checked to make sure the personal
> fiirewall wasn't enabled.
>
> Anybody know what I'm missing?
>

[ Post a follow-up to this message ]