IWA problems - IIS Forum

Hello all!

I experience some problems with an application recently.

Basically, IWA works half the time. That is, some users are able to access the VB.net application without any problem. Some others can, but if they refresh , they will get a 401. Finally, some people just can't access the application (I mean, the authetication box popup and even if they enter their username / password, it doesn't authorize them).

I have already disabled Anonymous Access for the application in IIS (V6.0).

Also, I have noticed that every users can acces some "simple" pages / files. For exemple, everyone can access every images in the /images directory. So I guess it's not a NTFS problem.

My "not simple" pages sometimes use System.Web.HttpContext.Current.User or have linked .js and .css files.

With Fiddler, for every page I request I see three "session". One 401, another 401 and finally a 200.

Seriously, I don't know where to look, and this is getting urgent.

I would really appreciate if anyone could help me a little... !!

myth0s

Newbie

26 Posts

May 20th, 2008
09:12 PM
#2

Re: IWA problems

Okay, after some more investigation, I have found that :

1 - In a web page, if I remove all references to external elements (images, style sheets, etc), everybody can access the page.

If I add, ie, a single image (<img src="whatever.png">) or a external javascript file, people will get the authentication box if they refresh the page.

2- If I open Fiddler, everything work. So if I refresh a page without Fiddler, I get the authentication box, but if Fiddler is running I can refresh as much as I want.

I don't understand what is happening here :(

myth0s

Newbie

26 Posts

May 21st, 2008
02:24 PM
#4

Re: IWA problems

Quote:

Originally Posted by kenobewan

What is fiddler? Sounds like you have a permissions prob. Does the aspnet account have access to the directory?

Fiddler is an HTTP Debugger (you can see all the requests sent/received as well as a lot of information about them)

The application pool runs with IWAM_SERVERNAME, not NETWORK_SERVICE, so I gave read permission to the whole folder to IWAM_SERVERNAME.

What is really strange though, is that I can access individual files.

If I do a simple test page with some text and one image : image.png. I cannont refresh that page or the credential box will popup (but I can enter the url of that page as much as I want in the address bar!).

However, if I direct my browser directly to the image (let's say server.domain/app1/images/image.png), I can see the image. And I can refresh as much as I like.

For now, I will give full access to the directory for IWAM_SERVERNAME (is there another asp_account than IWAM... ?)

Thanks a lot for your support!

myth0s

Newbie

26 Posts

June 6th, 2008
09:58 PM
#6

Re: IWA problems

Quote:

Originally Posted by kenobewan

Try adding aspnet account. HTH.

After granting Full Control to virtually everyone (Aspnet account, Anonymous Logon, Everyone, etc), I created a new application pool run with Network Service identity. Everything's working fine now.

Thanks for your help :)