Security ASP-MSDE

Security ASP-MSDE

Post by Mario Arauj » Tue, 07 Nov 2000 04:00:00



Hi! I'm developing a web application that uses ASPs and the MSDE database.
I've tow computers, one with IIS4.0 and the other with MSDE. Both have
NTServer 4.0. My problem is when I'm trying to connect to the MSDE using an
authenticated nt user the result is the following error:
--
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user '\'.
/Default.asp, line 37
--
I'm using this connection string:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=DATABASE;Data Source=COMPUTER;Locale
Identifier=2070;Connect Timeout=15;General Timeout=0;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC;"

Can anyone give me a tip for this problem?

Many Thanks in Advance,
Mario

 
 
 

Security ASP-MSDE

Post by Sven Aelterma » Tue, 07 Nov 2000 04:00:00


This is a very common problem. A authentication is not valid on one server
only, i.e. it cannot traverse accross servers.

The easiest solution to this is to create a user IUSR_<machinename> on the
db server that has the exact same password as the IUSR_<machinename> on your
web server.

I do believe there is more info on this in the FAQ.

(You are using Anonymous access right?)

--

Kind regards

Sven Aelterman
IT
Global Communication N.V.

Remember: Bugs come in through Windows.

http://www.aelterman.com
http://www.my-it.org


Quote:> Hi! I'm developing a web application that uses ASPs and the MSDE database.
> I've tow computers, one with IIS4.0 and the other with MSDE. Both have
> NTServer 4.0. My problem is when I'm trying to connect to the MSDE using
an
> authenticated nt user the result is the following error:
> --
> Microsoft OLE DB Provider for SQL Server error '80040e4d'
> Login failed for user '\'.
> /Default.asp, line 37
> --
> I'm using this connection string:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=DATABASE;Data Source=COMPUTER;Locale
> Identifier=2070;Connect Timeout=15;General Timeout=0;Use Procedure for
> Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC;"

> Can anyone give me a tip for this problem?

> Many Thanks in Advance,
> Mario


 
 
 

Security ASP-MSDE

Post by Sven Aelterma » Tue, 07 Nov 2000 04:00:00


Something must be wrong with me today... can't seem to formulate anything
right.

A authentication is not valid on one server only, i.e. it cannot traverse
accross servers.

must become

An authentication is valid on one server only, i.e. it cannot traverse
accross servers.

--

Kind regards

Sven Aelterman
IT
Global Communication N.V.

Remember: Bugs come in through Windows.

http://www.aelterman.com
http://www.my-it.org


> This is a very common problem. A authentication is not valid on one server
> only, i.e. it cannot traverse accross servers.

> The easiest solution to this is to create a user IUSR_<machinename> on the
> db server that has the exact same password as the IUSR_<machinename> on
your
> web server.

> I do believe there is more info on this in the FAQ.

> (You are using Anonymous access right?)

> --

> Kind regards

> Sven Aelterman
> IT
> Global Communication N.V.

> Remember: Bugs come in through Windows.

> http://www.aelterman.com
> http://www.my-it.org



> > Hi! I'm developing a web application that uses ASPs and the MSDE
database.
> > I've tow computers, one with IIS4.0 and the other with MSDE. Both have
> > NTServer 4.0. My problem is when I'm trying to connect to the MSDE using
> an
> > authenticated nt user the result is the following error:
> > --
> > Microsoft OLE DB Provider for SQL Server error '80040e4d'
> > Login failed for user '\'.
> > /Default.asp, line 37
> > --
> > I'm using this connection string:
> > "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> > Info=False;Initial Catalog=DATABASE;Data Source=COMPUTER;Locale
> > Identifier=2070;Connect Timeout=15;General Timeout=0;Use Procedure for
> > Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC;"

> > Can anyone give me a tip for this problem?

> > Many Thanks in Advance,
> > Mario

 
 
 

Security ASP-MSDE

Post by Mario Arauj » Tue, 07 Nov 2000 04:00:00


You ask if I'm using Anonymous access?
No. Allow Anonymous is disabled and Windows NT Challenge/Response is
enabled.


>This is a very common problem. A authentication is not valid on one server
>only, i.e. it cannot traverse accross servers.

>The easiest solution to this is to create a user IUSR_<machinename> on the
>db server that has the exact same password as the IUSR_<machinename> on
your
>web server.

>I do believe there is more info on this in the FAQ.

>(You are using Anonymous access right?)

>--

>Kind regards

>Sven Aelterman
>IT
>Global Communication N.V.

>Remember: Bugs come in through Windows.

>http://www.aelterman.com
>http://www.my-it.org



>> Hi! I'm developing a web application that uses ASPs and the MSDE
database.
>> I've tow computers, one with IIS4.0 and the other with MSDE. Both have
>> NTServer 4.0. My problem is when I'm trying to connect to the MSDE using
>an
>> authenticated nt user the result is the following error:
>> --
>> Microsoft OLE DB Provider for SQL Server error '80040e4d'
>> Login failed for user '\'.
>> /Default.asp, line 37
>> --
>> I'm using this connection string:
>> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
>> Info=False;Initial Catalog=DATABASE;Data Source=COMPUTER;Locale
>> Identifier=2070;Connect Timeout=15;General Timeout=0;Use Procedure for
>> Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC;"

>> Can anyone give me a tip for this problem?

>> Many Thanks in Advance,
>> Mario

 
 
 

Security ASP-MSDE

Post by Sven Aelterma » Tue, 07 Nov 2000 04:00:00


Are you on a domain then? If you are, I have no clue what is going on
(unless the users logging on would not be domain users).

If not, duplicate each and every account to the DB server (same user name
and pwd)

--

Kind regards

Sven Aelterman
IT
Global Communication N.V.

Remember: Bugs come in through Windows.

http://www.aelterman.com
http://www.my-it.org


> You ask if I'm using Anonymous access?
> No. Allow Anonymous is disabled and Windows NT Challenge/Response is
> enabled.


> >This is a very common problem. A authentication is not valid on one
server
> >only, i.e. it cannot traverse accross servers.

> >The easiest solution to this is to create a user IUSR_<machinename> on
the
> >db server that has the exact same password as the IUSR_<machinename> on
> your
> >web server.

> >I do believe there is more info on this in the FAQ.

> >(You are using Anonymous access right?)

> >--

> >Kind regards

> >Sven Aelterman
> >IT
> >Global Communication N.V.

> >Remember: Bugs come in through Windows.

> >http://www.aelterman.com
> >http://www.my-it.org



> >> Hi! I'm developing a web application that uses ASPs and the MSDE
> database.
> >> I've tow computers, one with IIS4.0 and the other with MSDE. Both have
> >> NTServer 4.0. My problem is when I'm trying to connect to the MSDE
using
> >an
> >> authenticated nt user the result is the following error:
> >> --
> >> Microsoft OLE DB Provider for SQL Server error '80040e4d'
> >> Login failed for user '\'.
> >> /Default.asp, line 37
> >> --
> >> I'm using this connection string:
> >> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> >> Info=False;Initial Catalog=DATABASE;Data Source=COMPUTER;Locale
> >> Identifier=2070;Connect Timeout=15;General Timeout=0;Use Procedure for
> >> Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC;"

> >> Can anyone give me a tip for this problem?

> >> Many Thanks in Advance,
> >> Mario

 
 
 

1. MSDE Security Vs Access Security

We just upgraded an application from Access to MSDE.  In Access the
database used user-level security and was encrypted.  This database has
sensitive information that we do not want our competition to get their
hands on.

In access they could not open the database unless they knew a valid
username and password.  However with SQL it appears to me that all
someone would have to do is attach the database file to MSDE or SQL
server installation then view the databases using their administrator
account.  So, now that we have upgraded this to SQL server and MSDE for
local users, how can I protect someone from getting the database files
(mdf & ldf) and attaching them to another SQL database then viewing the
data?  

Or can I restrict all user access to the file, including administrators.

Thank you,

Brad W. Young

2. Please help clarify 4gl/SE connectivity

3. MSDE/ASP help needed

4. Problems with C-Isam V5.00

5. Need Help with Using Windows NT authentication, MSDE and ASP

6. new recordset with default data

7. anyone used MSDE from an ASP page?

8. Porting P4DOS 4.5 to P4W 4.5

9. HELP: MSDE Security breached

10. MSDE Security settings

11. MSDE security Q and limits?

12. Error Installing MSDE for ASP.NET QuickStart Tutorial

13. MSDE,Win XP, & Login failure from ASP