Ed Molinari
03-30-1999, 08:55 PM
To all,
I have come across a situation that I don't quite understand concerning an ODBC 3.0 authentication issue. Our application is 2 tier across a web server and a sql server box. For reasons that I will not even attempt to describe, we are forced by our client to run these servers as workgroup servers. When we set up ODBC on the web server, I configured a DSN that uses Named Pipes and the renamed IUSR account, and this tests fine. However, when we use this DSN from the web app, we get an ODBC driver error. The renamed IUSR account will only work WITH A NULL password, as a matter of fact, even an administrator account will not work WITH a password. I have configured local accounts on each server that have synchronized passwords, and can map drives etc. where permissions allow, in the context of that user. What am I missing? The renamed account does have an SQL login and that password is also synchronized. I also tried TCP/IP sockets with a connection string as recommended in a Technet Article only to result in the same error.
Thanks In Advance,
Ed Molinari
I have come across a situation that I don't quite understand concerning an ODBC 3.0 authentication issue. Our application is 2 tier across a web server and a sql server box. For reasons that I will not even attempt to describe, we are forced by our client to run these servers as workgroup servers. When we set up ODBC on the web server, I configured a DSN that uses Named Pipes and the renamed IUSR account, and this tests fine. However, when we use this DSN from the web app, we get an ODBC driver error. The renamed IUSR account will only work WITH A NULL password, as a matter of fact, even an administrator account will not work WITH a password. I have configured local accounts on each server that have synchronized passwords, and can map drives etc. where permissions allow, in the context of that user. What am I missing? The renamed account does have an SQL login and that password is also synchronized. I also tried TCP/IP sockets with a connection string as recommended in a Technet Article only to result in the same error.
Thanks In Advance,
Ed Molinari