Integrated Authentication AND Basic Authentication

We finally got our Integrated Authentication working on our Intranet. It was not an easy task because we have a remote SQL Server. The page are written in ASP, so I went ahead and used my current ODBC connections that I had set up during development when we were just using Basic Authentication -- I just switched it in the DSN ODBC Wizard from Windows Authentication to SQL and used named pipes. Works like a charm.

However, in messing with things, now BASIC authentication doesn't work. We need users off-network to be able to log in and get to the Intranet.

Here's my question, when using Integrated Authentication, does it just naturally roll down to Basic Authentication next or do both have to be checked. I can't seem to get either way to work so if anyone has advice??

avoid it entirely? =)

What authentication are you thinking of? The IIS authentication or the SQL Server authentication.

I think he's talking about that integrated authentication option in IIS where somehow your desktop login becomes your web identity.

Its a neat idea, but you're always going to run into the terrible restrictions as you've discovered. Some things should just remain separate.

Plus for your forcing technology upon your users, which in most cases is bad.