SQL Server End User Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an ASP.NET Site. My Web Server is a Windows 2003 Server, My SQL Server
2000 runs on another Windows 2003 server. I setup the website so that the
connection statement would be in the web.config file (with a generic userid
and password). I ran into a problem, for some reason the end users
credentials are being passed to the SQL Server. If I do not have their Global
User Name as a user in SQL Server, they are denied access. If I have there
name, it works. Now this would be great if we wanted that tight of security,
but in our case, it is a public website for everyone to see the data. What I
was trying to do is have the vb behiond the scenes program call the SQL
Server using the generic user id and password and retrieve data. I thought I
had this working until I used an end user that had never used the SQL Server
before. Can some one walk through an example of how this should be setup?

Thank you.

Here is my web.config file
<configuration>
<appSettings>
<add key="DsnSqlOle" value="provider=SQLOLEDB;
server=Servername\development; database=databasename; uid=user; pwd=theword"/>
<add key="DsnSql"
value="server=Servername\development;uid=user;pwd=theword;database=databasename"/>
<!--This key is for directory locations for reports-->
<add key="ExportDir" value="Export\"/>
<add key="ReportDir" value="Reports\"/>
</appSettings>
<system.web>
<compilation defaultLanguage="vb" debug="true"><assemblies><add
assembly="CrystalDecisions.CrystalReports.Engine, Version=9.2.3300.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add
assembly="CrystalDecisions.ReportSource, Version=9.2.3300.0, Culture=neutral,
PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.Shared,
Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add
assembly="CrystalDecisions.Web, Version=9.2.3300.0, Culture=neutral,
PublicKeyToken=692fbea5521e1304"/><add
assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=9.2.3300.0,
Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>

<customErrors mode="Off"/>

<authentication mode="Windows" />

<authorization>
<deny users="?" />
</authorization>
<trace enabled="false" requestLimit="10" pageOutput="false"
traceMode="SortByTime" localOnly="true"/>

<sessionState mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20"/>

<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
</system.web>
</configuration>
 
Try adding "Network Library=dbmsoccn" to the connection string to force the
connection to use TCP/IP for the connection so that the SQL server login will
be used. The default network library for SQL server is Named Pipes which uses
Windows Authentication.
 
Ahh, I see the error, it should be dbmssocn.

Brad Roberts said:
Try adding "Network Library=dbmsoccn" to the connection string to force the
connection to use TCP/IP for the connection so that the SQL server login will
be used. The default network library for SQL server is Named Pipes which uses
Windows Authentication.
Click to expand...
 
Back
Top