Page 1 of 1

IIS Authentication

Posted: Mon Oct 22, 2007 3:18 am
by mct0
We have recently had a change of IT service provider at a client who runs webinator. They have messed with a bunch of settings and really, in general, "helped" enormously... so apologies if this is lacking in a bit of detail!

Bottom line is that we are now getting 401 errors when we try to do a walk.

Previously (digging thru the IIS logs) Webinator got a 401 error, then tried again with the appropriate user, then all was fine. Now, all of a sudden, once it gets a 401 it seems to give up. The site is secured via integrated authentication. One of the areas where the IT service provider has "helped" is in AD. The user we use is a local machine user, with admin privileges.

Logging in with the user webinator uses pops a windows login dialog no matter what we do, which I am suspicious is the root cause of the uissue. If I cancel rather than click OK on this dialog I get a 401.3 error.

Could this be the cause of our issues with Webinator? We have retained effectively the same setup for 2 years and all of a sudden it is now very borken indeed.

Basically scratching for anything in the way of an idea, as we are fresh out!

TIA,

mark

IIS Authentication

Posted: Mon Oct 22, 2007 10:25 am
by mark
Yeah, if you can't login using the user you have Webinator configured to use then Webinator won't be able to login either. Ask your IT folks why the Webinator account isn't working.

IIS Authentication

Posted: Mon Oct 22, 2007 6:57 pm
by mct0
Sorry... to clarify. I CAN log in using the user webinator uses, but only *after* I hit OK on the dialog box (which is totally prefilled including password).

For whatever reason, integrated authentication is popping the dialog even though it has the credentials.

My take is that this is what's causing webinator to fail. Would that be the correct asessment?

IIS Authentication

Posted: Mon Oct 22, 2007 9:10 pm
by John
That is probably correct. The webinator user is the one that you configured in Webinator to walk as, correct?

It may be that the "Logon as a batch job" or similar permission has been removed from Webinator. You might also check the "Digitally Sign Communications (always)" setting.