ASPNET user Where are others

Hello.

When pages on domain controler I faced problem: ASPNET user does not have access to MS SQL server? WHY does it has to have? My site uses integrated windows authentication.

Thanks in advanceAll you have to do is to to add the ASPNET user (windows user account) to the Users list of your database. To do that in Enterprise Manager, expand your database's tree, click on Users and select New from the toolbar. In the window that will come up select the ASPNET user from the "Login name" dropdownlist.|||I ran into same problem, only that I'm using MSDE and don't know where to get Enterprise Manager. Could you point out which MSDN package (or CD) contains that application? Or is there a way to do it without EM? Thanks a lot!|||Enterprise manager comes with SQL Server. If you don't have SQL Server try to find a replacement of Enterpise Manager. I remember seeing one in www.sourceforge.net. It is web based, built with ASP.NET. I am not sure if it will let you assogn a new user to your DB. But, you can give it a try|||Thanks!|||Well, bun in ASP 3 all I had to do is to grant access to a database for a user who is ACTUALLY browsing my page. Now, in ASP.NET, all the users will have access to a database with the same priveledges, same as ASPNET user. Is there any workaroud?

Thanks

ASPNET user with network resources elsewhere on a domain

I've been trying to workout how, without impersonation, I can allow an application running under the default ASPNET user to access a network resource (SQL Server/ADAM) not on the same physical machine.

It seems that because the ASPNET user is a local user not a domain user I can't setup windows authentication on the network resource. That seems to leave impersonation which MS et al say is unwise.

Have I mised something here?

Regards,

Steve.Yes.

You can change the user running the asp.net process. ONly the STANDARD user is a local user. It CAN also be a domain user, per your choosing.

ASP/SQL Server app not responding

We have a domain which we "hang" several applications off in separate
folders. In other words:
www.mydomain.com/app1
www.mydomain.com/app2
www.mydomain.com/app3
Each application functions differently. App1 may access a Microsoft Access
database through regular ASP pages while app2 accesses a MS SQL database
through ASP.NET, and app3 access a MS SQL Server database through regular
ASP. The MS SQL Server is running on a different server within the same
LAN. Our web server is running Windows Server 2003, and the server hosting
the database is running Windows Server 2000.
What is happening is after a few hours of running, the application that
accesses MS SQL Server through ASP (App3) starts slowing down, and will
eventually stop responding all-together. The progress bar in the browser
will just move very slowly, and never get there. I've let it run for
between 5 and 10 minutes with no response. We reboot the web server (which
I really hate to do, but don't have a choice), and the application starts
responding again.
When App3 stops responding, I can still go to app1, and it works just fine,
no problem. App2 (accessing SQL Server through ASP.NET) will not respond
either. However, when App 3 stops responding, I can't access anything in
that folder at all, not even a standard .asp page that contains no code at
all, let alone a SQL Server connection. So, I'm not sure if it's got
anything to do with SQL Server or not. The only thing that makes me suspect
that is that the ASP.NET which access SQL Server also has stopped
responding.
Does anyone know any reason the application would do this? It just started
doing this recently. We have had some changes, including having to rebuild
our domain controller, which is also the machine that hosts our SQL Server
database. We also recently bought a new router, and we also installed all
of the latest patches and updates on our Windows 2003 server (this is the
most recent change). I tend to suspect the updates as causing the problems,
because we ran fine all last week, which is after our router upgrade, and
the server rebuild. But I desperately need to figure this out. This
application is a national application, so could have hundreds of users
ticked off at us for this problem.
Any help or hints that anyone can give us is really appreciated.
Thanks,
Jesse
what is the memory usage of your 3 applications?
have you setup different application pool?
restarting IIS should solve the issue. (iisreset instead-of a reboot)
look at different performance counters to understand what's appends. maybe
you don't close your database connections.
look at your SQL server side to verify how many connections are opened and
if there is no dead lock.
you can configure an application pool to restarts himself at a regular
basis. maybe this could solve your issue. only the app3 could restart every
3 hours for example.
"Jesse" <nospam@.fake.com> wrote in message
news:ehfYxmDqFHA.3084@.TK2MSFTNGP09.phx.gbl...
> We have a domain which we "hang" several applications off in separate
> folders. In other words:
> www.mydomain.com/app1
> www.mydomain.com/app2
> www.mydomain.com/app3
> Each application functions differently. App1 may access a Microsoft
> Access database through regular ASP pages while app2 accesses a MS SQL
> database through ASP.NET, and app3 access a MS SQL Server database through
> regular ASP. The MS SQL Server is running on a different server within
> the same LAN. Our web server is running Windows Server 2003, and the
> server hosting the database is running Windows Server 2000.
> What is happening is after a few hours of running, the application that
> accesses MS SQL Server through ASP (App3) starts slowing down, and will
> eventually stop responding all-together. The progress bar in the browser
> will just move very slowly, and never get there. I've let it run for
> between 5 and 10 minutes with no response. We reboot the web server
> (which I really hate to do, but don't have a choice), and the application
> starts responding again.
> When App3 stops responding, I can still go to app1, and it works just
> fine, no problem. App2 (accessing SQL Server through ASP.NET) will not
> respond either. However, when App 3 stops responding, I can't access
> anything in that folder at all, not even a standard .asp page that
> contains no code at all, let alone a SQL Server connection. So, I'm not
> sure if it's got anything to do with SQL Server or not. The only thing
> that makes me suspect that is that the ASP.NET which access SQL Server
> also has stopped responding.
> Does anyone know any reason the application would do this? It just
> started doing this recently. We have had some changes, including having
> to rebuild our domain controller, which is also the machine that hosts our
> SQL Server database. We also recently bought a new router, and we also
> installed all of the latest patches and updates on our Windows 2003 server
> (this is the most recent change). I tend to suspect the updates as
> causing the problems, because we ran fine all last week, which is after
> our router upgrade, and the server rebuild. But I desperately need to
> figure this out. This application is a national application, so could
> have hundreds of users ticked off at us for this problem.
> Any help or hints that anyone can give us is really appreciated.
> Thanks,
> Jesse
>
|||> what is the memory usage of your 3 applications?
I don't know how to track memory usage for individaul apps. How do I do
that?

> have you setup different application pool?
Yes, I have separate application pools for each application. Perhaps this
is what allows one app to continue functioning while one seems to freeze up.

> restarting IIS should solve the issue. (iisreset instead-of a reboot)
It doesn't. That was one of the first things I did. Actually, I stopped and
restarted the one web site. I didn't try stopping and restarting all of IIS.
Maybe I'll try that next time.

> look at different performance counters to understand what's appends. maybe
> you don't close your database connections.
This is one issue that I'm thinking may be causing the problem. I'm about to
go through all of my files from all of my applications and check for that
sort of problem. I kind of suspect that is the issue.

> look at your SQL server side to verify how many connections are opened and
> if there is no dead lock.
How do I do that?

> you can configure an application pool to restarts himself at a regular
> basis. maybe this could solve your issue. only the app3 could restart
> every 3 hours for example.
Good suggestion. How do I do that? Also, when it restarts, will it affect
anyone that is in the app at the time?
Thanks for all the good suggestions.
Jesse

ASP/SQL Server app not responding

We have a domain which we "hang" several applications off in separate
folders. In other words:
www.mydomain.com/app1
www.mydomain.com/app2
www.mydomain.com/app3
Each application functions differently. App1 may access a Microsoft Access
database through regular ASP pages while app2 accesses a MS SQL database
through ASP.NET, and app3 access a MS SQL Server database through regular
ASP. The MS SQL Server is running on a different server within the same
LAN. Our web server is running Windows Server 2003, and the server hosting
the database is running Windows Server 2000.
What is happening is after a few hours of running, the application that
accesses MS SQL Server through ASP (App3) starts slowing down, and will
eventually stop responding all-together. The progress bar in the browser
will just move very slowly, and never get there. I've let it run for
between 5 and 10 minutes with no response. We reboot the web server (which
I really hate to do, but don't have a choice), and the application starts
responding again.
When App3 stops responding, I can still go to app1, and it works just fine,
no problem. App2 (accessing SQL Server through ASP.NET) will not respond
either. However, when App 3 stops responding, I can't access anything in
that folder at all, not even a standard .asp page that contains no code at
all, let alone a SQL Server connection. So, I'm not sure if it's got
anything to do with SQL Server or not. The only thing that makes me suspect
that is that the ASP.NET which access SQL Server also has stopped
responding.
Does anyone know any reason the application would do this? It just started
doing this recently. We have had some changes, including having to rebuild
our domain controller, which is also the machine that hosts our SQL Server
database. We also recently bought a new router, and we also installed all
of the latest patches and updates on our Windows 2003 server (this is the
most recent change). I tend to suspect the updates as causing the problems,
because we ran fine all last week, which is after our router upgrade, and
the server rebuild. But I desperately need to figure this out. This
application is a national application, so could have hundreds of users
ticked off at us for this problem.
Any help or hints that anyone can give us is really appreciated.
Thanks,
Jessewhat is the memory usage of your 3 applications?
have you setup different application pool?
restarting IIS should solve the issue. (iisreset instead-of a reboot)
look at different performance counters to understand what's appends. maybe
you don't close your database connections.
look at your SQL server side to verify how many connections are opened and
if there is no dead lock.
you can configure an application pool to restarts himself at a regular
basis. maybe this could solve your issue. only the app3 could restart every
3 hours for example.
"Jesse" <nospam@.fake.com> wrote in message
news:ehfYxmDqFHA.3084@.TK2MSFTNGP09.phx.gbl...
> We have a domain which we "hang" several applications off in separate
> folders. In other words:
> www.mydomain.com/app1
> www.mydomain.com/app2
> www.mydomain.com/app3
> Each application functions differently. App1 may access a Microsoft
> Access database through regular ASP pages while app2 accesses a MS SQL
> database through ASP.NET, and app3 access a MS SQL Server database through
> regular ASP. The MS SQL Server is running on a different server within
> the same LAN. Our web server is running Windows Server 2003, and the
> server hosting the database is running Windows Server 2000.
> What is happening is after a few hours of running, the application that
> accesses MS SQL Server through ASP (App3) starts slowing down, and will
> eventually stop responding all-together. The progress bar in the browser
> will just move very slowly, and never get there. I've let it run for
> between 5 and 10 minutes with no response. We reboot the web server
> (which I really hate to do, but don't have a choice), and the application
> starts responding again.
> When App3 stops responding, I can still go to app1, and it works just
> fine, no problem. App2 (accessing SQL Server through ASP.NET) will not
> respond either. However, when App 3 stops responding, I can't access
> anything in that folder at all, not even a standard .asp page that
> contains no code at all, let alone a SQL Server connection. So, I'm not
> sure if it's got anything to do with SQL Server or not. The only thing
> that makes me suspect that is that the ASP.NET which access SQL Server
> also has stopped responding.
> Does anyone know any reason the application would do this? It just
> started doing this recently. We have had some changes, including having
> to rebuild our domain controller, which is also the machine that hosts our
> SQL Server database. We also recently bought a new router, and we also
> installed all of the latest patches and updates on our Windows 2003 server
> (this is the most recent change). I tend to suspect the updates as
> causing the problems, because we ran fine all last week, which is after
> our router upgrade, and the server rebuild. But I desperately need to
> figure this out. This application is a national application, so could
> have hundreds of users ticked off at us for this problem.
> Any help or hints that anyone can give us is really appreciated.
> Thanks,
> Jesse
>|||> what is the memory usage of your 3 applications?
I don't know how to track memory usage for individaul apps. How do I do
that?
> have you setup different application pool?
Yes, I have separate application pools for each application. Perhaps this
is what allows one app to continue functioning while one seems to freeze up.
> restarting IIS should solve the issue. (iisreset instead-of a reboot)
It doesn't. That was one of the first things I did. Actually, I stopped and
restarted the one web site. I didn't try stopping and restarting all of IIS.
Maybe I'll try that next time.
> look at different performance counters to understand what's appends. maybe
> you don't close your database connections.
This is one issue that I'm thinking may be causing the problem. I'm about to
go through all of my files from all of my applications and check for that
sort of problem. I kind of suspect that is the issue.
> look at your SQL server side to verify how many connections are opened and
> if there is no dead lock.
How do I do that?
> you can configure an application pool to restarts himself at a regular
> basis. maybe this could solve your issue. only the app3 could restart
> every 3 hours for example.
Good suggestion. How do I do that? Also, when it restarts, will it affect
anyone that is in the app at the time?
Thanks for all the good suggestions.
Jesse

ASP/SQL Server app not responding

We have a domain which we "hang" several applications off in separate
folders. In other words:
www.mydomain.com/app1
www.mydomain.com/app2
www.mydomain.com/app3
Each application functions differently. App1 may access a Microsoft Access
database through regular ASP pages while app2 accesses a MS SQL database
through ASP.NET, and app3 access a MS SQL Server database through regular
ASP. The MS SQL Server is running on a different server within the same
LAN. Our web server is running Windows Server 2003, and the server hosting
the database is running Windows Server 2000.
What is happening is after a few hours of running, the application that
accesses MS SQL Server through ASP (App3) starts slowing down, and will
eventually stop responding all-together. The progress bar in the browser
will just move very slowly, and never get there. I've let it run for
between 5 and 10 minutes with no response. We reboot the web server (which
I really hate to do, but don't have a choice), and the application starts
responding again.
When App3 stops responding, I can still go to app1, and it works just fine,
no problem. App2 (accessing SQL Server through ASP.NET) will not respond
either. However, when App 3 stops responding, I can't access anything in
that folder at all, not even a standard .asp page that contains no code at
all, let alone a SQL Server connection. So, I'm not sure if it's got
anything to do with SQL Server or not. The only thing that makes me suspect
that is that the ASP.NET which access SQL Server also has stopped
responding.
Does anyone know any reason the application would do this? It just started
doing this recently. We have had some changes, including having to rebuild
our domain controller, which is also the machine that hosts our SQL Server
database. We also recently bought a new router, and we also installed all
of the latest patches and updates on our Windows 2003 server (this is the
most recent change). I tend to suspect the updates as causing the problems,
because we ran fine all last week, which is after our router upgrade, and
the server rebuild. But I desperately need to figure this out. This
application is a national application, so could have hundreds of users
ticked off at us for this problem.
Any help or hints that anyone can give us is really appreciated.
Thanks,
Jessewhat is the memory usage of your 3 applications?
have you setup different application pool?
restarting IIS should solve the issue. (iisreset instead-of a reboot)
look at different performance counters to understand what's appends. maybe
you don't close your database connections.
look at your SQL server side to verify how many connections are opened and
if there is no dead lock.
you can configure an application pool to restarts himself at a regular
basis. maybe this could solve your issue. only the app3 could restart every
3 hours for example.
"Jesse" <nospam@.fake.com> wrote in message
news:ehfYxmDqFHA.3084@.TK2MSFTNGP09.phx.gbl...
> We have a domain which we "hang" several applications off in separate
> folders. In other words:
> www.mydomain.com/app1
> www.mydomain.com/app2
> www.mydomain.com/app3
> Each application functions differently. App1 may access a Microsoft
> Access database through regular ASP pages while app2 accesses a MS SQL
> database through ASP.NET, and app3 access a MS SQL Server database through
> regular ASP. The MS SQL Server is running on a different server within
> the same LAN. Our web server is running Windows Server 2003, and the
> server hosting the database is running Windows Server 2000.
> What is happening is after a few hours of running, the application that
> accesses MS SQL Server through ASP (App3) starts slowing down, and will
> eventually stop responding all-together. The progress bar in the browser
> will just move very slowly, and never get there. I've let it run for
> between 5 and 10 minutes with no response. We reboot the web server
> (which I really hate to do, but don't have a choice), and the application
> starts responding again.
> When App3 stops responding, I can still go to app1, and it works just
> fine, no problem. App2 (accessing SQL Server through ASP.NET) will not
> respond either. However, when App 3 stops responding, I can't access
> anything in that folder at all, not even a standard .asp page that
> contains no code at all, let alone a SQL Server connection. So, I'm not
> sure if it's got anything to do with SQL Server or not. The only thing
> that makes me suspect that is that the ASP.NET which access SQL Server
> also has stopped responding.
> Does anyone know any reason the application would do this? It just
> started doing this recently. We have had some changes, including having
> to rebuild our domain controller, which is also the machine that hosts our
> SQL Server database. We also recently bought a new router, and we also
> installed all of the latest patches and updates on our Windows 2003 server
> (this is the most recent change). I tend to suspect the updates as
> causing the problems, because we ran fine all last week, which is after
> our router upgrade, and the server rebuild. But I desperately need to
> figure this out. This application is a national application, so could
> have hundreds of users ticked off at us for this problem.
> Any help or hints that anyone can give us is really appreciated.
> Thanks,
> Jesse
>|||> what is the memory usage of your 3 applications?
I don't know how to track memory usage for individaul apps. How do I do
that?

> have you setup different application pool?
Yes, I have separate application pools for each application. Perhaps this
is what allows one app to continue functioning while one seems to freeze up.

> restarting IIS should solve the issue. (iisreset instead-of a reboot)
It doesn't. That was one of the first things I did. Actually, I stopped and
restarted the one web site. I didn't try stopping and restarting all of IIS.
Maybe I'll try that next time.

> look at different performance counters to understand what's appends. maybe
> you don't close your database connections.
This is one issue that I'm thinking may be causing the problem. I'm about to
go through all of my files from all of my applications and check for that
sort of problem. I kind of suspect that is the issue.

> look at your SQL server side to verify how many connections are opened and
> if there is no dead lock.
How do I do that?

> you can configure an application pool to restarts himself at a regular
> basis. maybe this could solve your issue. only the app3 could restart
> every 3 hours for example.
Good suggestion. How do I do that? Also, when it restarts, will it affect
anyone that is in the app at the time?
Thanks for all the good suggestions.
Jesse

ASP.NET/IIS/SQL help !

Hi.

Let me tell you my domain environment. It's NT 4.0 domain with a
Windows 2000 member server running as ASP.NET/IIS/MS SQL 2000, all in one
box, and it worked fine. Recently, we bought a new box with Windows 2003
standard version and trying to move ASP.NET and IIS to this box. However;
we're getting "Login failed for user 'NT Authority\Anonymous Logon'" error
when we access the ASP.NET page. I believe it has something to do with
moving the asp.net/iis to a different box and leave SQL in the old box. I've
done some research and there're some possibilities that have caused this:

1. It would require Active Directory domain environment when you move
asp.net/iis to a different box and authenticates with the SQL
server on the old box?

2. ASPNET account locally on both boxes need to be matched?

3. reconfigure the Machine.config and Web.config in the asp.net?

Can anyone help me on this with the details?

ThanksHi Charlie

Not exactly sure why you are getting this error but it sounds it's more
a problem of the IIS configuration than SQL Server. You might want to
repost in an IIS group.

If you place a very simple index.aspx (a blank webform) in the root of
your website on the Windows 2003 box and try calling it like
http://localhost/myapp/index.aspx - Do you get the same error? In this
case it's a pure IIS problem. Check the properties of your web
application root and make sure that anonymous logon is enabled.

Also check that you have the right settings in web.config.

<!-- AUTHENTICATION
This section sets the authentication policies of the application.
Possible modes are "Windows", "Forms", "Passport" and "None"

"None" No authentication is performed.
"Windows" IIS performs authentication (Basic, Digest, or Integrated
Windows) according to its settings for the application. Anonymous
access must be disabled in IIS.
"Forms" You provide a custom form (Web page) for users to enter their
credentials, and then you authenticate them in your application. A user
credential token is stored in a cookie.
"Passport" Authentication is performed via a centralized
authentication service provided
by Microsoft that offers a single logon and core profile services for
member sites.
--
Let me know the result.

M

ASP.NET/IIS/SQL help

Hi.
Let me tell you my domain environment. It's NT 4.0 domain with a
Windows 2000 member server running as ASP.NET/IIS/MS SQL 2000, all in one
box, and it worked fine. Recently, we bought a new box with Windows 2003
standard version and trying to move ASP.NET and IIS to this box. However;
we're getting "Login failed for user 'NT Authority\Anonymous Logon'" error
when we access the ASP.NET page. I believe it has something to do with
moving the asp.net/iis to a different box and leave SQL in the old box. I've
done some research and there're some possibilities that have caused this:
1. It would require Active Directory domain environment when you move
asp.net/iis to a different box and authenticates with the SQL
server on the old box?
2. ASPNET account locally on both boxes need to be matched?
3. reconfigure the Machine.config and Web.config in the asp.net?
Can anyone help me on this with the details?
Thanks
"Charlie Ting" <cting74@.hotmail.com> wrote in
news:O6ednQldj8dcG4vfRVn-sw@.golden.net:

> we're getting "Login failed for user 'NT
> Authority\Anonymous Logon'" error when we access the ASP.NET page. I
> believe it has something to do with moving the asp.net/iis to a
> different box and leave SQL in the old box.
My knowledge is limited. but I'll hazard a good guess...
As IIS is on a new server the IUSER_newservername is being used to access
the virtual directory, which in turn is not an authenticated user as far as
sql server is concerned.
Hope it helps?

ASP.NET/IIS/SQL help

Hi.
Let me tell you my domain environment. It's NT 4.0 domain with a
Windows 2000 member server running as ASP.NET/IIS/MS SQL 2000, all in one
box, and it worked fine. Recently, we bought a new box with Windows 2003
standard version and trying to move ASP.NET and IIS to this box. However;
we're getting "Login failed for user 'NT Authority\Anonymous Logon'" error
when we access the ASP.NET page. I believe it has something to do with
moving the asp.net/iis to a different box and leave SQL in the old box. I've
done some research and there're some possibilities that have caused this:
1. It would require Active Directory domain environment when you move
asp.net/iis to a different box and authenticates with the SQL
server on the old box?
2. ASPNET account locally on both boxes need to be matched?
3. reconfigure the Machine.config and Web.config in the asp.net?
Can anyone help me on this with the details?
Thanks"Charlie Ting" <cting74@.hotmail.com> wrote in
news:O6ednQldj8dcG4vfRVn-sw@.golden.net:

> we're getting "Login failed for user 'NT
> Authority\Anonymous Logon'" error when we access the ASP.NET page. I
> believe it has something to do with moving the asp.net/iis to a
> different box and leave SQL in the old box.
My knowledge is limited. but I'll hazard a good guess...
As IIS is on a new server the IUSER_newservername is being used to access
the virtual directory, which in turn is not an authenticated user as far as
sql server is concerned.
Hope it helps'

ASP.NET/IIS/SQL help

Hi.
Let me tell you my domain environment. It's NT 4.0 domain with a
Windows 2000 member server running as ASP.NET/IIS/MS SQL 2000, all in one
box, and it worked fine. Recently, we bought a new box with Windows 2003
standard version and trying to move ASP.NET and IIS to this box. However;
we're getting "Login failed for user 'NT Authority\Anonymous Logon'" error
when we access the ASP.NET page. I believe it has something to do with
moving the asp.net/iis to a different box and leave SQL in the old box. I've
done some research and there're some possibilities that have caused this:
1. It would require Active Directory domain environment when you move
asp.net/iis to a different box and authenticates with the SQL
server on the old box?
2. ASPNET account locally on both boxes need to be matched?
3. reconfigure the Machine.config and Web.config in the asp.net?
Can anyone help me on this with the details?
Thanks"Charlie Ting" <cting74@.hotmail.com> wrote in
news:O6ednQldj8dcG4vfRVn-sw@.golden.net:
> we're getting "Login failed for user 'NT
> Authority\Anonymous Logon'" error when we access the ASP.NET page. I
> believe it has something to do with moving the asp.net/iis to a
> different box and leave SQL in the old box.
My knowledge is limited. but I'll hazard a good guess...
As IIS is on a new server the IUSER_newservername is being used to access
the virtual directory, which in turn is not an authenticated user as far as
sql server is concerned.
Hope it helps'

asp.net sql connection problem

Hi all,
I have a production environment where I have a 2-node SQL 2005 Cluster
running on boxes which are part of a domain "MyCompany". I have setup a
domain user account called "netasp" and then given it permissions to the
database. I then setup a new App Pool in IIS on my Web Server (not part of
domain, can access SQL server via TCP) with identity setup to a local
account called "netasp" with the same password as the domain user account. I
then setup my website under this App Pool and tried my app. For some reason
it will not connect. This works in a development environment where my web &
sql is on the same box (non cluster environment). How do I go about getting
this to work? For security reasons, my web servers cannot be part of the
domain.
TIA!On Tue, 18 Apr 2006 02:48:39 -0500, <param@.community.nospam> wrote:
Hi all,
I have a production environment where I have a 2-node SQL 2005 Cluster
running on boxes which are part of a domain "MyCompany". I have setup a
domain user account called "netasp" and then given it permissions to the
database. I then setup a new App Pool in IIS on my Web Server (not part of
domain, can access SQL server via TCP) with identity setup to a local
account called "netasp" with the same password as the domain user account.
I
then setup my website under this App Pool and tried my app. For some reaso
n
it will not connect. This works in a development environment where my web
&
sql is on the same box (non cluster environment). How do I go about gettin
g
this to work? For security reasons, my web servers cannot be part of the
domain.
Is your web app and database connection configured for Windows integrated se
curity? If so you
probably have a delegation issue.
Paul
~~~~
Microsoft MVP (Visual Basic)|||My web app actually uses forms authentication by authenticating against the
database. I have heard of cases where people got this to work. I just need
some guidance/help in getting it to work.
TIA!
"Paul Clement" <UseAdddressAtEndofMessage@.swspectrum.com> wrote in message
news:dhl942hp9ifa1gncs1aokpfdqn2s2d1tjp@.
4ax.com...
> On Tue, 18 Apr 2006 02:48:39 -0500, <param@.community.nospam> wrote:
> Hi all,
>
> I have a production environment where I have a 2-node SQL 2005 Cluster
> running on boxes which are part of a domain "MyCompany". I have setup a
> domain user account called "netasp" and then given it permissions to the
> database. I then setup a new App Pool in IIS on my Web Server (not part
> of
> domain, can access SQL server via TCP) with identity setup to a local
> account called "netasp" with the same password as the domain user
> account. I
> then setup my website under this App Pool and tried my app. For some
> reason
> it will not connect. This works in a development environment where my
> web &
> sql is on the same box (non cluster environment). How do I go about
> getting
> this to work? For security reasons, my web servers cannot be part of the
> domain.
>
> Is your web app and database connection configured for Windows integrated
> security? If so you
> probably have a delegation issue.
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)|||The problem is that you gave permissions to the domain account, but you
running it as a local account. The remote SQL Server doesn't know about
your local 'netasp', it only knows about the domain one. I'm not sure you
can 'fool' the SQL server in thinking that the local machine account of the
remote web server is the same thing as the domain account it knows about. I
think you'd have to make your web server part of the domain, and run it
under the domain account. That, or just use username/password for the the
sql server authentication instead of integrated.
<param@.community.nospam> wrote in message
news:ODwLDyrYGHA.4652@.TK2MSFTNGP04.phx.gbl...
> Hi all,
> I have a production environment where I have a 2-node SQL 2005 Cluster
> running on boxes which are part of a domain "MyCompany". I have setup a
> domain user account called "netasp" and then given it permissions to the
> database. I then setup a new App Pool in IIS on my Web Server (not part of
> domain, can access SQL server via TCP) with identity setup to a local
> account called "netasp" with the same password as the domain user account.
> I then setup my website under this App Pool and tried my app. For some
> reason it will not connect. This works in a development environment where
> my web & sql is on the same box (non cluster environment). How do I go
> about getting this to work? For security reasons, my web servers cannot be
> part of the domain.
> TIA!
>|||I would love to use SQL Auth, but the beauty of windows auth is I dont have
to specify the username/pwd in the config file. Is there no way at all to
get this to work? Does MS recommend putting your Web Servers in the same
domain as the SQL? Our security consultant told us never to do that. Leave
the Web in the DMZ..
TIA!
"Marina Levit [MVP]" <someone@.nospam.com> wrote in message
news:eOeZGZvYGHA.3848@.TK2MSFTNGP05.phx.gbl...
> The problem is that you gave permissions to the domain account, but you
> running it as a local account. The remote SQL Server doesn't know about
> your local 'netasp', it only knows about the domain one. I'm not sure you
> can 'fool' the SQL server in thinking that the local machine account of
> the remote web server is the same thing as the domain account it knows
> about. I think you'd have to make your web server part of the domain, and
> run it under the domain account. That, or just use username/password for
> the the sql server authentication instead of integrated.
> <param@.community.nospam> wrote in message
> news:ODwLDyrYGHA.4652@.TK2MSFTNGP04.phx.gbl...
>|||I can't say I have complete knowledge of windows security, but I don't know
how to get this to work, although there could be a way.
First off, if someone gets access to your web server, you could argue that
they will get access to the sql server through windows authentication if
they really try anyway - so it will be the same as if they saw the
username/password in the config file.
As far as storing the username/password in the config file (or elsewhere in
a different file, even outside your virtual directory), you could encrypt
the connection information to provide an extra level of security.
<param@.community.nospam> wrote in message
news:uYxROfvYGHA.3532@.TK2MSFTNGP05.phx.gbl...
>I would love to use SQL Auth, but the beauty of windows auth is I dont have
>to specify the username/pwd in the config file. Is there no way at all to
>get this to work? Does MS recommend putting your Web Servers in the same
>domain as the SQL? Our security consultant told us never to do that. Leave
>the Web in the DMZ..
> TIA!
> "Marina Levit [MVP]" <someone@.nospam.com> wrote in message
> news:eOeZGZvYGHA.3848@.TK2MSFTNGP05.phx.gbl...
>|||On Tue, 18 Apr 2006 09:53:06 -0500, <param@.community.nospam> wrote:
I would love to use SQL Auth, but the beauty of windows auth is I dont hav
e
to specify the username/pwd in the config file. Is there no way at all to
get this to work? Does MS recommend putting your Web Servers in the same
domain as the SQL? Our security consultant told us never to do that. Leave
the Web in the DMZ..
See if the following helps:
How To: Use Forms Authentication with Active Directory in Multiple Domains i
n ASP.NET 2.0
http://msdn.microsoft.com/library/d... />
000021.asp
Paul
~~~~
Microsoft MVP (Visual Basic)|||I guess, I need to clarify. I do not wish to use Active Directory in anyway
to authenticate my web application users. They will be authenticated off
tables in SQL Server. The problem I am having is making the Asp.Net Web
Application connect to and authenticate against the SQL Server using a
standard specified Windows account. Is there a way to do it when the SQL
server is in a domain environment and the Web Server are in a Workgroup
environment. I have tried SQL Auth and it works fine.
TIA!
"Paul Clement" <UseAdddressAtEndofMessage@.swspectrum.com> wrote in message
news:rh8a4218grgi70ba3tef4td7n80lmcrus5@.
4ax.com...
> On Tue, 18 Apr 2006 09:53:06 -0500, <param@.community.nospam> wrote:
> I would love to use SQL Auth, but the beauty of windows auth is I dont
> have
> to specify the username/pwd in the config file. Is there no way at all
> to
> get this to work? Does MS recommend putting your Web Servers in the same
> domain as the SQL? Our security consultant told us never to do that.
> Leave
> the Web in the DMZ..
>
> See if the following helps:
> How To: Use Forms Authentication with Active Directory in Multiple Domains
> in ASP.NET 2.0
> http://msdn.microsoft.com/library/d...>
ht000021.asp
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)|||<param@.community.nospam> wrote in message
news:uWbzbqxYGHA.1580@.TK2MSFTNGP02.phx.gbl...
>I guess, I need to clarify. I do not wish to use Active Directory in anyway
>to authenticate my web application users. They will be authenticated off
>tables in SQL Server. The problem I am having is making the Asp.Net Web
>Application connect to and authenticate against the SQL Server using a
>standard specified Windows account. Is there a way to do it when the SQL
>server is in a domain environment and the Web Server are in a Workgroup
>environment. I have tried SQL Auth and it works fine.
Right - how do you expect to use Windows Auth if both machines are not in a
domain?
Tom Kaminski IIS MVP
http://www.microsoft.com/windowsser...ty/centers/iis/
http://mvp.support.microsoft.com/
http://www.iistoolshed.com/ - tools, scripts, and utilities for running IIS|||Marina wrote on Tue, 18 Apr 2006 10:42:07 -0400:

> The problem is that you gave permissions to the domain account, but you
> running it as a local account. The remote SQL Server doesn't know about
> your local 'netasp', it only knows about the domain one. I'm not sure you
> can 'fool' the SQL server in thinking that the local machine account of
> the remote web server is the same thing as the domain account it knows
> about. I think you'd have to make your web server part of the domain, and
> run it under the domain account. That, or just use username/password for
> the the sql server authentication instead of integrated.
By using the same login name and password on both machines it should work -
certainly does here where I have an IIS server running sites under local
accounts that match credentials on a SQL server machine and they login fine,
both servers are configured to run in the same workgroup (no domains running
in my DMZ). I am however doing this using ASP and via ODBC and OLE DB
connections, so it could be that something is different in the way ASP.NET
passes credentials around.
Dan