'NT AUTHORITY\NETWORK SERVICE'

[NuJoizey]

sql server 2005 express running on server2003

did a data import from an existing installation of sql server 2000.

import worked, but I keep getting the above error when my app tries to connect to data store from a user outside of .netStudio, like via the internet - for example:

http://localhost/myApp/Default.aspx

gives the error,

and

http//myipaddress/myApp/Default.aspx gives the error,

yet

http://localhost:4747/myApp/Default.aspx,

(after pressing ctrl f5 in visual studio) does render my page correctly.

I tried to add the user NetworkService under myApp's database properties in sql server 2005 express, but it's not there.

I think something got mixed up in the import, and somehow, the database thinks that it's still in the old domain under the 2000 installation - i.e. i can't even browse for any of the users on this installation to grant access to the DB

help!! how do i fix this?

 

[onpnt]

Did you transfer all the logins to the new server?

How is authentication setup? when you do this..

http://localhost:4747/myApp/Default.aspx..you're

running the app under your account. I'm assuming you have full rights so that is not a good test. When you run the app from IIS security context is completely different depending on how you have set things up.

Basically give us more information on how you set up security on the IIS server and you database

[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]

 

[NuJoizey]

hi thanks for the response -

first of all, let me say I don't know a ton about MSSQL server 2005

I didn't transfer the logins to the new server, but why would I have to? I just wanted the data, and not any of the security settings, at it is a completely new installation on a brand new instance of MSSQL 2005 express on a lone server2003 machine connected to the internet.

I do know that my sql server installation now is set to use windows authentication as opposed to the sql server's. But this isn't working, so I thought about changing it.

This article looks like it gives me 3 alternatives on how to do that, and although I understand the concepts of what it is saying, I have no idea where to click to do this -

http://support.microsoft.com/kb/316989/

should i be able to get this thing to work using windows authentication, or am i wasting my time?

 

[NuJoizey]

i got some joy thru implementing asp.net impersonation - i think it was method 3 of the above article: see the below tek-tips thread where this story continues:

http://www.tek-tips.com/viewthread.cfm?qid=1339711&page=1