Hi,

I have a web server that I'm trying to use to connect to
a SQL Server. If I try to create an ODBC DSN to the SQL
machine, I get SQL Server Error: 1326.

If I open network neighborhood on the web server and
browse to the sql server machine, it prompts me for a
username/password to browse the machine. After I enter
the administrator user/pass to browse the machine, I can
then go back and create an ODBC DSN without any problems.

How can I get it to let me connect with a DSN without
first browsing/authenticating via network neighborhood?
Most of the time, the web server will be running but not
logged in....so I need the DSN to be "trusted".

Thanks!

Allan,

I am assuming that you are trying to NT authentication in teh DSN. If this
is the case, the error 1326 indicates that the user who is logged on does
not have permission on the box where SQL Server is installed. The prompt
for the password would indicate the same thing. There are a couple of thngs
you can do:

1. If you are logged on as a local account to the machine you are creating
the DSN on:
Create an account on the SQL Server machine with the same name a password.
This should allow you to connect

2: If you are logged on with a domain account to the machine you are
creating the DSN on:
Make sure the domain account has an account on the SQL Server machine.

Once you get this to work creating the DSN, you will have to make sure that
the ISUR anonymous account has access to the SQL Server machine and a SQL
Server login in order to connect from an ASP page. This assumes of course
that you are using ASP pages and anonymous authentication.

Rand