minameismud's questions

I've got an asp.net app that relies on Request.LogonUserIdentity.Name to be populated with the username of the person logged onto the client machine. In IIS7 on the webserver, I've disabled Anonymous Authentication and enabled ASP.NET Impersonation & Windows Authentication. (I'm logging onto the webserver with a service account, not my own.) When I try to browse to the site from my desktop, I get prompted for my network credentials which fail - 401 Unauthorized.... I'm using .Net 3.5 sp Whatever. The server is running IIS 7.5.

Application Pool:

• Managed Pipeline Mode: Classic
• Load User Profile: false
• Identity: ApplicationPoolIdentity

Web Application:

• .NET Auth Rules: Allow All Users
• Enabled auth types: ASP.NET Impersonation, Windows

File-system Folder permissions:

• Creator Owner: Special Permissions
• Machine\IUsr: Read & Execute, List folder contents, Read
• Machine\System: Full Control
• My Domain Account: Full Control
• Machine\Administrators: Full Control
• Machine\Users: Read & Execute, List folder contents, Read
• Machine\IIS_IUSRS: Read & Execute, List folder contents, Read
• Trusted Installer: Full Control

I've tried adding Machine\Everyone and Domain\Domain Users with Read and also with Full Control and I'm still being blocked.

Myself and a coworker are both Site Admins for every site collection we've got. Well, until Friday night. Most admin privileges were disabled for two entire site collections. There is no custom code running anywhere in MOSS, and there are no workflows set up at all.

On both of the affected site collections, my Site Actions menu shows these options:

• View All Site Content
• View Reports
  • Checked Out To Me
  • Last Modified By Me
  • Pending Approval
  • My Tasks
  • All Draft Documents
  • Going Live Within Next Seven Days
  • Expiring Within Next Seven Days
• Manage Content and Structure

We were thinking it was some sort of licensing issue where an expired license key simply removes admin privileges (allowing your content to sill be accessible) while not allowing you to edit stuff.

Here's the site collection layout:

• Root site collection (still have access)
  • Site Collection 1 (no access)
  • Site Collection 2 (no access)
  • Site Collection 3 (still have access)
  • Site Collection the rest (still have access)

I ran the enumsites operation of stsadm on the root site collection, and the output shows that my coworker is the owner and I am secondary owner (Admin and Secondary Admin match in Central Administration for all site collections). It matches the output from two weeks ago exactly (I have it to compare to).

Any ideas? Other spots I should check within Central Admin?