PDA

Click to See Complete Forum and Search --> : ODBC connection to SQL server Fails


lenin
May 29th, 2000, 01:55 PM
hi,
I have posted a question similar to below in previously, but still have not resolved it sufficiently well to be comfortable with the answer.
I have an issue with a small web page I am trying to get going:

I have done the following:

1. Via IIS I am allowing anonymous login with a login / password setup in IIS, which has a matching login on SQL server.
2. The DSN is set up for SQL authentication with the username / password set up as above.
3. using a VB Class component I try to access methods in the VB dll, but am getting a

"You are not authorized to view this page"

( The SQL user is allowed to be a data reader.)
error, despite the fact that I have a similar page which uses the exact same DSN/username/password!

The reason I used SQL Server authentication initially was because I could not even get connected with NT authentication ( getting "authentication failed for user '\'", I had anonymous logon turned of and integrated NT Authentication turned on for IIS Directory security)from an ASP script, however I did not have a problem with this when running the vb dll from within VB.

I have already trawled various FAQ's for similar setup. please presume before answering that:

1. The DSN is set up problem.
2. The user is set up correctly in SQL server,
3. IIS anonymous details are correct,

I have yet to come across anybody ( on the internet ) with similar connection problems to SQL server via a web client. Is there something extremely simple I am missing, ideally I would like to use NT authentication but this does not seem to be an option at the moment.

Thanks in advance.

Lenin

dvst8
May 29th, 2000, 07:31 PM
i have developped a web for a LAN, and this is what I had to do:

1. check the password synchronization box (in your IIS management console, right click on root of web, properties...)
2. NT challenge/response checked
3. You may have to specify an anonymous user such as IUSR_servername, with a password and give this person all read rights
4. Have SQL inherit NT login (when i access my DSN i don't need a separate pass/login)

I can't say I fully understand this stuff... there are multiple levels of security (i.e. Network Level, domain level, browser level, and then the database has it's own level) I had a real fun time getting mine going. I hope something I said might give you an idea...

good luck.