To All Experts:

I need your help.  I have exhausted my internal resources and cannot resolve
this issue.  I have checked other sites and resources and cannot find a
solution.  Here is what has happened.

In our Active Directory (AD) a user had two accounts one named ISDJD and the
other DJDOE.  The later DJDOE was used to access a web site using FrontPage
2002 Server Extensions through AD authentication.  In and effort to clean up
these extra accounts in AD the DJDOE account was deleted from AD and the
ISDJD account was renamed DJDOE.  Now the user can no longer access the web
site.

I created two new accounts in AD testcase1 and testcase2 and recreated the
problem on a test site deleting testcase2 and renaming testcase1 to
testcase2.  I removed the account from within the FrontPage web site and
then added the renamed testcase2 account back.  Still, no luck, cannot login
with the account.  I then deleted the testcase2 account from AD and recreate
d
it back in AD with the same name and password.  I then added back the newly
created testcase2
account to the FrontPage web site and it still does not work.

Can someone explain what is going on here and how I might go about fixing
the problem?  Web sites running on both Windows 2000 IIS 5.0 and Windows
2003 IIS 6.0 have the same issue.

Please help if you can.

Thanks,

[ Post a follow-up to this message ]

Suggest your contact MS Product Support.

--
 ========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
 ========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
 ========================================
======

"Thomas" <Thomas@discussions.microsoft.com> wrote in message
news:5107B22D-BBB0-4F07-BF6D-833FC04E749A@microsoft.com...
> To All Experts:
>
> I need your help.  I have exhausted my internal resources and cannot resol
ve
> this issue.  I have checked other sites and resources and cannot find a
> solution.  Here is what has happened.
>
> In our Active Directory (AD) a user had two accounts one named ISDJD and t
he
> other DJDOE.  The later DJDOE was used to access a web site using FrontPag
e
> 2002 Server Extensions through AD authentication.  In and effort to clean 
up
> these extra accounts in AD the DJDOE account was deleted from AD and the
> ISDJD account was renamed DJDOE.  Now the user can no longer access the we
b
> site.
>
> I created two new accounts in AD testcase1 and testcase2 and recreated the
> problem on a test site deleting testcase2 and renaming testcase1 to
> testcase2.  I removed the account from within the FrontPage web site and
> then added the renamed testcase2 account back.  Still, no luck, cannot log
in
> with the account.  I then deleted the testcase2 account from AD and recrea
ted
> it back in AD with the same name and password.  I then added back the newl
y
> created testcase2
> account to the FrontPage web site and it still does not work.
>
> Can someone explain what is going on here and how I might go about fixing
> the problem?  Web sites running on both Windows 2000 IIS 5.0 and Windows
> 2003 IIS 6.0 have the same issue.
>
> Please help if you can.
>
> Thanks,
>

[ Post a follow-up to this message ]

Thomas:

Have you any idea how IIS or FrontPage 2002 Server Extensions handle Domain
Account authentication.  Does either of them store or use sid history simila
r
to that of Windows SharePoint Services?  Some way or another IIS or FrontPag
e
Server Extensions maintains the previous account credentials or components
thereof and will not recognize the account changes.  Surely I am not the
first to encounter this problem   Anyone else out there have this problem?

I appreciate anything additional you can add.

Thanks,

Thomas

"Thomas A. Rowe" wrote:

> Suggest your contact MS Product Support.
>
> --
>  ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
>  ========================================
======
> If you feel your current issue is a results of installing
> a Service Pack or security update, please contact
> Microsoft Product Support Services:
> http://support.microsoft.com
> If the problem can be shown to have been caused by a
> security update, then there is usually no charge for the call.
>  ========================================
======
>
> "Thomas" <Thomas@discussions.microsoft.com> wrote in message
> news:5107B22D-BBB0-4F07-BF6D-833FC04E749A@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

No. This would be more of a server or IIS related issue then FP, which is wh
y I suggested contact MS
Product Support, but you could also post to either the server or IIS newsgro
up.

--
 ========================================
======
Thomas A. Rowe (Microsoft MVP - FrontPage)
 ========================================
======
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
 ========================================
======

"Thomas" <Thomas@discussions.microsoft.com> wrote in message
news:8379F1B8-348A-4928-BFF2-442D8624175F@microsoft.com...[vbcol=seagreen]
> Thomas:
>
> Have you any idea how IIS or FrontPage 2002 Server Extensions handle Domai
n
> Account authentication.  Does either of them store or use sid history simi
lar
> to that of Windows SharePoint Services?  Some way or another IIS or FrontP
age
> Server Extensions maintains the previous account credentials or components
> thereof and will not recognize the account changes.  Surely I am not the
> first to encounter this problem   Anyone else out there have this problem?
>
> I appreciate anything additional you can add.
>
> Thanks,
>
> Thomas
>
> "Thomas A. Rowe" wrote:
> 

[ Post a follow-up to this message ]

Thomas:

Thank you for your response.  I have posted over on the IIS newsgroup but
have not heard anything yet.  I have also posted to the Windows SharePoint
Services news group.  I do believe this is an issue with the FrontPage Serve
r
Extensions more so than IIS, although, I could be wrong.  The reason I say
this is because a tool has been developed for changing the SIDs in Windows
SharePoint Services.  Given that the Server Extension Technology has evolved
into Windows SharePoint Services in some form or another I had hoped that a
similar tool would be available for the Extensions.

If anyone is interested you can view the information I received here.

The WSSUserUtil is included in the Sharepoint Utility Suite version 2.5
http://www.microsoft.com/sharepoint...tail.asp?a1=724

Here is the thread, search for Domain Account renamed.

http://www.microsoft.com/technet/co...windowsservices

Patrick Feltz was kind enough to share this with me.  I have read the
material and it looks like this will work for me on my Windows SharePoint
Services sites.  In closing I think I will look at the SDK and see if there
is anything there.

Thanks,

Thomas



"Thomas A. Rowe" wrote:

> No. This would be more of a server or IIS related issue then FP, which is 
why I suggested contact MS
> Product Support, but you could also post to either the server or IIS newsg
roup.
>
> --
>  ========================================
======
> Thomas A. Rowe (Microsoft MVP - FrontPage)
>  ========================================
======
> If you feel your current issue is a results of installing
> a Service Pack or security update, please contact
> Microsoft Product Support Services:
> http://support.microsoft.com
> If the problem can be shown to have been caused by a
> security update, then there is usually no charge for the call.
>  ========================================
======
>
> "Thomas" <Thomas@discussions.microsoft.com> wrote in message
> news:8379F1B8-348A-4928-BFF2-442D8624175F@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]