IIS 6 stopped working, IUSR account has no access

[link470]

Windows Server 2003 with IIS 6.

 

I'm in a huge pickle at the moment. Somehow something happened to one of our web servers and I can't make it serve web pages as IUSR. I've always used the builtin IUSR account to serve websites from IIS and our other IIS server is working just fine. This one however doesn't want to show anything when the contents being published has IUSR as read/execute [i get a 404 page]. However, if I add everyone to the list, I can see contents from a web browser. I'd type more of a description but I'm frantically trying to get this web server back up. I need it running for tomorrow. Any help would be greatly appreciated. I know I didn't provide much information at all. PHP was installed, but I uninstalled it in the mean time to remove any complications. I'm just trying to serve some HTML pages right now and even that seems to prove too difficult a task for IIS 6 to handle. I've tried a few means of resetting the IUSR account's password and trying things listed here and here but I'm not having much luck.

[SYNACK]

Have you tried recreating it as sometimes it does get stroppy, I had this happen after a domain join because IIS had been installed before the domain join it messed with the password and permission setting wasting the account.

 

You could try this Recreating IIS IUSR_ and IWAM_ Accounts - Knowledge Base - TASKE Technology Inc.

 

IIS also keeps a record of what it thinks the password is and this can get out of sync so you could try this:

You can set the IUSR Password using the following command:

C:\Inetpub\AdminScripts>cscript adsutil.vbs set w3svc/anonymoususerpass “P@ssword”You then need to sync it with this command:

C:\Inetpub\AdminScripts>cscript.exe synciwam.vbs -v

 

also worth a read:

http://www.dotnetscraps.com/dotnetscraps/post/Change-IIS-Server-%28Machine%29-name-including-IUSR-and-IWAM-account.aspx

[link470]

Thanks for your reply! I managed to get the server up and running. At the moment, the permissions are Everyone read, which I'm not a fan of, but that's the only way it seems to work. The website is up and for the next few days it's critical to stay online so I'm not sure if I should make any tweaks. Ended up installing PHP 5.2.11 since I've had luck with that version especially on server 2008 even though this is a server 2003 box.

 

The other interesting thing is when I remove Everyone's permissions on the web root, I don't get a 403 or 401.x error, I get a 404. Just page cannot be found. Doesn't prompt for a password, just can't find the page.

 

The only thing now is it seems a bit slow serving PHP pages. Static HTML is no problem. But there's a lag [5 seconds or so] between pages for PHP [MySQL is installed locally, but these are PHP pages even that aren't using a database]. I'm using PHP-CGI, wondering if that may be an issue and if I should use FastCGI instead. I've never had luck getting ISAPI to work on Windows.

 

::EDIT::

 

Wow...so that's interesting...

 

First off, here's the website in question:

http://sisp.sd63.bc.ca/

 

I pulled an old IT site template I had made awhile back as a test and put it in the root under a folder IT-1, I gave it only IUSR read permissions. Then, I made a copy and called it IT-2, and I added Everyone as well as IUSR. Look at the difference.

 

IT-1

IT-2

 

Any ideas?

Edited September 16, 2010 by link470

[pete]

Are the two servers at the same patch level? i.e did one get the Black Tuesday IIS patch, but the other didn't?

[link470]

Yup, all servers have all updates as of this past Tuesday.

[birchanger]

Location or permissions on the CSS?

[link470]

Location or permissions on the CSS?

 

Shouldn't make a difference. For IT site templates for example, they're each exact copies of the IT template site root that I designed. One root [and propagated down] has permissions for everyone and IUSR, and the other has permissions for only IUSR. The IUSR one is the one that looks wrong. The only difference between the two directories is permissions, they have identical files.