ASPNET password and authentication

From: Dan (elm0e_at_hotmail.com)
Date: 05/16/03 

Date: Fri, 16 May 2003 09:59:23 -0700

Sam,

The following excerpt is from page 300 of the 'Building
Secure ASP.NET applications...hope this helps...

Dan

==============================================
Important: If you change the ASPNET password to a known
value, the password in the
Local Security Authority (LSA) on the local computer will
no longer match the account
password stored in the Windows Security Account Manager
(SAM) database. If you need to
revert to the AutoGenerate default, you must do the
following:
Run Aspnet_regiis.exe to reset ASP.NET to its default
configuration. For more information,
see article Q306005, "HOWTO: Repair IIS Mapping After You
Remove and Reinstall IIS," in
the Microsoft Knowledge Base. When you do this, you get a
new account and a new
Windows Security Identifier (SID). The permissions for
this account are set to their default
values. As a result, you need to explicitly reapply
permissions and privileges that you had
originally set for the old ASPNET account.

==============================================

>-----Original Message-----
>I am having authentication problems with the Microsoft
>CRM. I am receiving an error message "SQL Server Login
>failed for user (null)".
>
>A while back I changed the local ASPNET password on the
>web server from the original password. I was wondering
if
>this could be a cause, and how do I set it back to the
>original password which was auto generated.
>
>In the machine.config in the processmodel the username
is
>set to "machine" and the password is set
to "AutoGenerate".
>So is the ASPNET account even being used?
>
>Thanks for any advice
>Sam
>.
>