Hello SQL pros -
I am having a problem with enabling the remote connections for Analysis
Services 2005, Here's the gist...
--Error Information--
"To configure Analysis Services for Remote Connections, you must be an
adminsitrator for Analysis Services Windows Service (SQLSAC).
Additonal Info
A connection cannot be made. Ensure that service is running
(Microsoft.AnalysisServices)
No connection could be made because the target machine actively refused
it (System)."
--Actions Taken--
1) Analysis Services Windows Service was confirmed to be running.
2) Analysis Services Windows Service was stopped and restarted.
3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
running under domain account with administrator priviledges.
4) Confirmed connectivity to Analysis Services instance through direct
connection (Windows Authentication)
--OS/System Information--
Windows 2000 Service Pack 5
--Clustering Roles--
Primary node for 1 SQL 2000 SP4 instance
Secondary node 1 SQL 2000 SP4 instance
Primary node for 1 Analysis Services 2000 instance
Primary node for 1 SQL 2005 instance, and primary
Primary node for 1 SQL 2005 Analysis Services Instance
I didn't find anything of relevance in the Windows logs or SQL logs.
So I am not sure where else to look. Is this a bug with 2005?
Any Suggestions to help troubleshoot are greatly appreciated!
thanks in advance.
benBP,
Do you have a firewall program installed? Is this or a previous version
CTP?
HTH
Jerry
"BP" <BPollitt01@.gmail.com> wrote in message
news:1148655002.461974.305510@.i39g2000cwa.googlegroups.com...
> Hello SQL pros -
> I am having a problem with enabling the remote connections for Analysis
> Services 2005, Here's the gist...
> --Error Information--
> "To configure Analysis Services for Remote Connections, you must be an
> adminsitrator for Analysis Services Windows Service (SQLSAC).
> Additonal Info
> A connection cannot be made. Ensure that service is running
> (Microsoft.AnalysisServices)
> No connection could be made because the target machine actively refused
> it (System)."
> --Actions Taken--
> 1) Analysis Services Windows Service was confirmed to be running.
> 2) Analysis Services Windows Service was stopped and restarted.
> 3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
> running under domain account with administrator priviledges.
> 4) Confirmed connectivity to Analysis Services instance through direct
> connection (Windows Authentication)
> --OS/System Information--
> Windows 2000 Service Pack 5
> --Clustering Roles--
> Primary node for 1 SQL 2000 SP4 instance
> Secondary node 1 SQL 2000 SP4 instance
> Primary node for 1 Analysis Services 2000 instance
> Primary node for 1 SQL 2005 instance, and primary
> Primary node for 1 SQL 2005 Analysis Services Instance
> I didn't find anything of relevance in the Windows logs or SQL logs.
> So I am not sure where else to look. Is this a bug with 2005?
> Any Suggestions to help troubleshoot are greatly appreciated!
> thanks in advance.
> ben
>
Showing posts with label connections. Show all posts
Showing posts with label connections. Show all posts
Monday, March 19, 2012
I'm Stumped! - (AS 2005 - Remote Connections Cannot be enabled)
Hello SQL pros -
I am having a problem with enabling the remote connections for Analysis
Services 2005, Here's the gist...
--Error Information--
"To configure Analysis Services for Remote Connections, you must be an
adminsitrator for Analysis Services Windows Service (SQLSAC).
Additonal Info
A connection cannot be made. Ensure that service is running
(Microsoft.AnalysisServices)
No connection could be made because the target machine actively refused
it (System)."
--Actions Taken--
1) Analysis Services Windows Service was confirmed to be running.
2) Analysis Services Windows Service was stopped and restarted.
3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
running under domain account with administrator priviledges.
4) Confirmed connectivity to Analysis Services instance through direct
connection (Windows Authentication)
--OS/System Information--
Windows 2000 Service Pack 5
--Clustering Roles--
Primary node for 1 SQL 2000 SP4 instance
Secondary node 1 SQL 2000 SP4 instance
Primary node for 1 Analysis Services 2000 instance
Primary node for 1 SQL 2005 instance, and primary
Primary node for 1 SQL 2005 Analysis Services Instance
I didn't find anything of relevance in the Windows logs or SQL logs.
So I am not sure where else to look. Is this a bug with 2005?
Any Suggestions to help troubleshoot are greatly appreciated!
thanks in advance.
benBP,
Do you have a firewall program installed? Is this or a previous version
CTP?
HTH
Jerry
"BP" <BPollitt01@.gmail.com> wrote in message
news:1148655002.461974.305510@.i39g2000cwa.googlegroups.com...
> Hello SQL pros -
> I am having a problem with enabling the remote connections for Analysis
> Services 2005, Here's the gist...
> --Error Information--
> "To configure Analysis Services for Remote Connections, you must be an
> adminsitrator for Analysis Services Windows Service (SQLSAC).
> Additonal Info
> A connection cannot be made. Ensure that service is running
> (Microsoft.AnalysisServices)
> No connection could be made because the target machine actively refused
> it (System)."
> --Actions Taken--
> 1) Analysis Services Windows Service was confirmed to be running.
> 2) Analysis Services Windows Service was stopped and restarted.
> 3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
> running under domain account with administrator priviledges.
> 4) Confirmed connectivity to Analysis Services instance through direct
> connection (Windows Authentication)
> --OS/System Information--
> Windows 2000 Service Pack 5
> --Clustering Roles--
> Primary node for 1 SQL 2000 SP4 instance
> Secondary node 1 SQL 2000 SP4 instance
> Primary node for 1 Analysis Services 2000 instance
> Primary node for 1 SQL 2005 instance, and primary
> Primary node for 1 SQL 2005 Analysis Services Instance
> I didn't find anything of relevance in the Windows logs or SQL logs.
> So I am not sure where else to look. Is this a bug with 2005?
> Any Suggestions to help troubleshoot are greatly appreciated!
> thanks in advance.
> ben
>
I am having a problem with enabling the remote connections for Analysis
Services 2005, Here's the gist...
--Error Information--
"To configure Analysis Services for Remote Connections, you must be an
adminsitrator for Analysis Services Windows Service (SQLSAC).
Additonal Info
A connection cannot be made. Ensure that service is running
(Microsoft.AnalysisServices)
No connection could be made because the target machine actively refused
it (System)."
--Actions Taken--
1) Analysis Services Windows Service was confirmed to be running.
2) Analysis Services Windows Service was stopped and restarted.
3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
running under domain account with administrator priviledges.
4) Confirmed connectivity to Analysis Services instance through direct
connection (Windows Authentication)
--OS/System Information--
Windows 2000 Service Pack 5
--Clustering Roles--
Primary node for 1 SQL 2000 SP4 instance
Secondary node 1 SQL 2000 SP4 instance
Primary node for 1 Analysis Services 2000 instance
Primary node for 1 SQL 2005 instance, and primary
Primary node for 1 SQL 2005 Analysis Services Instance
I didn't find anything of relevance in the Windows logs or SQL logs.
So I am not sure where else to look. Is this a bug with 2005?
Any Suggestions to help troubleshoot are greatly appreciated!
thanks in advance.
benBP,
Do you have a firewall program installed? Is this or a previous version
CTP?
HTH
Jerry
"BP" <BPollitt01@.gmail.com> wrote in message
news:1148655002.461974.305510@.i39g2000cwa.googlegroups.com...
> Hello SQL pros -
> I am having a problem with enabling the remote connections for Analysis
> Services 2005, Here's the gist...
> --Error Information--
> "To configure Analysis Services for Remote Connections, you must be an
> adminsitrator for Analysis Services Windows Service (SQLSAC).
> Additonal Info
> A connection cannot be made. Ensure that service is running
> (Microsoft.AnalysisServices)
> No connection could be made because the target machine actively refused
> it (System)."
> --Actions Taken--
> 1) Analysis Services Windows Service was confirmed to be running.
> 2) Analysis Services Windows Service was stopped and restarted.
> 3) Analysis Services Windows Service (and SQL Accounts) confirmed to be
> running under domain account with administrator priviledges.
> 4) Confirmed connectivity to Analysis Services instance through direct
> connection (Windows Authentication)
> --OS/System Information--
> Windows 2000 Service Pack 5
> --Clustering Roles--
> Primary node for 1 SQL 2000 SP4 instance
> Secondary node 1 SQL 2000 SP4 instance
> Primary node for 1 Analysis Services 2000 instance
> Primary node for 1 SQL 2005 instance, and primary
> Primary node for 1 SQL 2005 Analysis Services Instance
> I didn't find anything of relevance in the Windows logs or SQL logs.
> So I am not sure where else to look. Is this a bug with 2005?
> Any Suggestions to help troubleshoot are greatly appreciated!
> thanks in advance.
> ben
>
Wednesday, March 7, 2012
IIS 6 and Windows Authentication to SQL Server 2000
I am running a Windows Server 2003 machine as my web server. I would
like to use Windows authentication for connections to my SQL Server
2000 instance on a Windows 2000 server. I've read where mirroring the
ASPNET account and password on the web server and SQL server would
work. However, with IIS 6, ASP.NET runs under the 'NT
AUTHORITY\NETWORK SERVICE' account. Should I change the password of
the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
should I create another user like 'MY_WEB_USER' and mirror that on both
machines?
In short, how do I get Windows authentication to work between a Windows
Server 2003 web server and a Windows 2000 SQL server?
Thanks!
If you are truly using Windows Authentication, ie a user has an account on
the domain as well as SQL Server, you will do the following:
1. Ensure the user cannot sign in as anonymous
2. Add their account to a group that has SQL rights
You may mean "bastardized windows authentication", meaning SQL Server uses
WIndows Authentication, but you are using anon accounts in IIS. If you go
this route, you are advised to impersonate an account rather than give a
local account rights on another box. One way to easily do this is to place
the assembly in COM+ and declaratively assign a domain account to the
application.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"mcollier" wrote:
> I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>
|||Hi,
Are both the servers in the same domain?
If so create a domain user account and switch the identity of the ASP.NET
worker process to this acccount. You can do this by creating a new
application pool in IIS6.
Now configure this acccount as a login for sql server.
Don't forget to add this user to the IIS_WPG group on your Win2K3 machine.
HTH
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109016547.061210.221620@.f14g2000cwb.googlegr oups.com...
>I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>
|||Both servers are not in the same domain. I've done this before when I
had two Windows 2000 servers. Having one Windows 2003 and one Windows
2000 server seems to be somewhat more confusing.
|||What you did for WIndows 2000 should still work for Win2K3.
Create a user on both the machines with the same username and password.
Then configure the ASP.NET worker process to run under this user account on
win2k3 machine
and configure sql on win2k machine to accept this user as a valid login.
As long as the username/password are same on both the machines this should
work.
hth
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109041768.768522.120100@.f14g2000cwb.googlegr oups.com...
> Both servers are not in the same domain. I've done this before when I
> had two Windows 2000 servers. Having one Windows 2003 and one Windows
> 2000 server seems to be somewhat more confusing.
>
|||Ok, I think I see where you're going with this. I was thinking I could
use the ASPNET or NETWORK SERVICE account for both servers. But, that
doesn't appear to be the case. What you're saying is that I could
create a user on both servers, for example MY_WEB_USER. Then, set the
ASP.NET worker process to run as this account. I would also need to
give that user the correct permissions (similar to NETWORK SERVICE
probably). Sound about right?
|||Yep,
That is what I had in mind.
Let us know how it goes.
Thanks
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109125129.410024.221630@.f14g2000cwb.googlegr oups.com...
> Ok, I think I see where you're going with this. I was thinking I could
> use the ASPNET or NETWORK SERVICE account for both servers. But, that
> doesn't appear to be the case. What you're saying is that I could
> create a user on both servers, for example MY_WEB_USER. Then, set the
> ASP.NET worker process to run as this account. I would also need to
> give that user the correct permissions (similar to NETWORK SERVICE
> probably). Sound about right?
>
like to use Windows authentication for connections to my SQL Server
2000 instance on a Windows 2000 server. I've read where mirroring the
ASPNET account and password on the web server and SQL server would
work. However, with IIS 6, ASP.NET runs under the 'NT
AUTHORITY\NETWORK SERVICE' account. Should I change the password of
the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
should I create another user like 'MY_WEB_USER' and mirror that on both
machines?
In short, how do I get Windows authentication to work between a Windows
Server 2003 web server and a Windows 2000 SQL server?
Thanks!
If you are truly using Windows Authentication, ie a user has an account on
the domain as well as SQL Server, you will do the following:
1. Ensure the user cannot sign in as anonymous
2. Add their account to a group that has SQL rights
You may mean "bastardized windows authentication", meaning SQL Server uses
WIndows Authentication, but you are using anon accounts in IIS. If you go
this route, you are advised to impersonate an account rather than give a
local account rights on another box. One way to easily do this is to place
the assembly in COM+ and declaratively assign a domain account to the
application.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"mcollier" wrote:
> I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>
|||Hi,
Are both the servers in the same domain?
If so create a domain user account and switch the identity of the ASP.NET
worker process to this acccount. You can do this by creating a new
application pool in IIS6.
Now configure this acccount as a login for sql server.
Don't forget to add this user to the IIS_WPG group on your Win2K3 machine.
HTH
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109016547.061210.221620@.f14g2000cwb.googlegr oups.com...
>I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>
|||Both servers are not in the same domain. I've done this before when I
had two Windows 2000 servers. Having one Windows 2003 and one Windows
2000 server seems to be somewhat more confusing.
|||What you did for WIndows 2000 should still work for Win2K3.
Create a user on both the machines with the same username and password.
Then configure the ASP.NET worker process to run under this user account on
win2k3 machine
and configure sql on win2k machine to accept this user as a valid login.
As long as the username/password are same on both the machines this should
work.
hth
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109041768.768522.120100@.f14g2000cwb.googlegr oups.com...
> Both servers are not in the same domain. I've done this before when I
> had two Windows 2000 servers. Having one Windows 2003 and one Windows
> 2000 server seems to be somewhat more confusing.
>
|||Ok, I think I see where you're going with this. I was thinking I could
use the ASPNET or NETWORK SERVICE account for both servers. But, that
doesn't appear to be the case. What you're saying is that I could
create a user on both servers, for example MY_WEB_USER. Then, set the
ASP.NET worker process to run as this account. I would also need to
give that user the correct permissions (similar to NETWORK SERVICE
probably). Sound about right?
|||Yep,
That is what I had in mind.
Let us know how it goes.
Thanks
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109125129.410024.221630@.f14g2000cwb.googlegr oups.com...
> Ok, I think I see where you're going with this. I was thinking I could
> use the ASPNET or NETWORK SERVICE account for both servers. But, that
> doesn't appear to be the case. What you're saying is that I could
> create a user on both servers, for example MY_WEB_USER. Then, set the
> ASP.NET worker process to run as this account. I would also need to
> give that user the correct permissions (similar to NETWORK SERVICE
> probably). Sound about right?
>
IIS 6 and Windows Authentication to SQL Server 2000
I am running a Windows Server 2003 machine as my web server. I would
like to use Windows authentication for connections to my SQL Server
2000 instance on a Windows 2000 server. I've read where mirroring the
ASPNET account and password on the web server and SQL server would
work. However, with IIS 6, ASP.NET runs under the 'NT
AUTHORITY\NETWORK SERVICE' account. Should I change the password of
the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
should I create another user like 'MY_WEB_USER' and mirror that on both
machines?
In short, how do I get Windows authentication to work between a Windows
Server 2003 web server and a Windows 2000 SQL server?
Thanks!If you are truly using Windows Authentication, ie a user has an account on
the domain as well as SQL Server, you will do the following:
1. Ensure the user cannot sign in as anonymous
2. Add their account to a group that has SQL rights
You may mean "bastardized windows authentication", meaning SQL Server uses
WIndows Authentication, but you are using anon accounts in IIS. If you go
this route, you are advised to impersonate an account rather than give a
local account rights on another box. One way to easily do this is to place
the assembly in COM+ and declaratively assign a domain account to the
application.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"mcollier" wrote:
> I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>|||Hi,
Are both the servers in the same domain?
If so create a domain user account and switch the identity of the ASP.NET
worker process to this acccount. You can do this by creating a new
application pool in IIS6.
Now configure this acccount as a login for sql server.
Don't forget to add this user to the IIS_WPG group on your Win2K3 machine.
HTH
--
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109016547.061210.221620@.f14g2000cwb.googlegroups.com...
>I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>|||Both servers are not in the same domain. I've done this before when I
had two Windows 2000 servers. Having one Windows 2003 and one Windows
2000 server seems to be somewhat more confusing.|||What you did for Windows 2000 should still work for Win2K3.
Create a user on both the machines with the same username and password.
Then configure the ASP.NET worker process to run under this user account on
win2k3 machine
and configure sql on win2k machine to accept this user as a valid login.
As long as the username/password are same on both the machines this should
work.
hth
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109041768.768522.120100@.f14g2000cwb.googlegroups.com...
> Both servers are not in the same domain. I've done this before when I
> had two Windows 2000 servers. Having one Windows 2003 and one Windows
> 2000 server seems to be somewhat more confusing.
>|||Ok, I think I see where you're going with this. I was thinking I could
use the ASPNET or NETWORK SERVICE account for both servers. But, that
doesn't appear to be the case. What you're saying is that I could
create a user on both servers, for example MY_WEB_USER. Then, set the
ASP.NET worker process to run as this account. I would also need to
give that user the correct permissions (similar to NETWORK SERVICE
probably). Sound about right?|||Yep,
That is what I had in mind.
Let us know how it goes.
Thanks
--
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109125129.410024.221630@.f14g2000cwb.googlegroups.com...
> Ok, I think I see where you're going with this. I was thinking I could
> use the ASPNET or NETWORK SERVICE account for both servers. But, that
> doesn't appear to be the case. What you're saying is that I could
> create a user on both servers, for example MY_WEB_USER. Then, set the
> ASP.NET worker process to run as this account. I would also need to
> give that user the correct permissions (similar to NETWORK SERVICE
> probably). Sound about right?
>
like to use Windows authentication for connections to my SQL Server
2000 instance on a Windows 2000 server. I've read where mirroring the
ASPNET account and password on the web server and SQL server would
work. However, with IIS 6, ASP.NET runs under the 'NT
AUTHORITY\NETWORK SERVICE' account. Should I change the password of
the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
should I create another user like 'MY_WEB_USER' and mirror that on both
machines?
In short, how do I get Windows authentication to work between a Windows
Server 2003 web server and a Windows 2000 SQL server?
Thanks!If you are truly using Windows Authentication, ie a user has an account on
the domain as well as SQL Server, you will do the following:
1. Ensure the user cannot sign in as anonymous
2. Add their account to a group that has SQL rights
You may mean "bastardized windows authentication", meaning SQL Server uses
WIndows Authentication, but you are using anon accounts in IIS. If you go
this route, you are advised to impersonate an account rather than give a
local account rights on another box. One way to easily do this is to place
the assembly in COM+ and declaratively assign a domain account to the
application.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"mcollier" wrote:
> I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>|||Hi,
Are both the servers in the same domain?
If so create a domain user account and switch the identity of the ASP.NET
worker process to this acccount. You can do this by creating a new
application pool in IIS6.
Now configure this acccount as a login for sql server.
Don't forget to add this user to the IIS_WPG group on your Win2K3 machine.
HTH
--
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109016547.061210.221620@.f14g2000cwb.googlegroups.com...
>I am running a Windows Server 2003 machine as my web server. I would
> like to use Windows authentication for connections to my SQL Server
> 2000 instance on a Windows 2000 server. I've read where mirroring the
> ASPNET account and password on the web server and SQL server would
> work. However, with IIS 6, ASP.NET runs under the 'NT
> AUTHORITY\NETWORK SERVICE' account. Should I change the password of
> the 'NT AUTHORITY\NETWORK SERVICE' account to something I know, and
> create a mirrored 'NETWORK SERVICE' account on my SQL server? Or,
> should I create another user like 'MY_WEB_USER' and mirror that on both
> machines?
> In short, how do I get Windows authentication to work between a Windows
> Server 2003 web server and a Windows 2000 SQL server?
> Thanks!
>|||Both servers are not in the same domain. I've done this before when I
had two Windows 2000 servers. Having one Windows 2003 and one Windows
2000 server seems to be somewhat more confusing.|||What you did for Windows 2000 should still work for Win2K3.
Create a user on both the machines with the same username and password.
Then configure the ASP.NET worker process to run under this user account on
win2k3 machine
and configure sql on win2k machine to accept this user as a valid login.
As long as the username/password are same on both the machines this should
work.
hth
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109041768.768522.120100@.f14g2000cwb.googlegroups.com...
> Both servers are not in the same domain. I've done this before when I
> had two Windows 2000 servers. Having one Windows 2003 and one Windows
> 2000 server seems to be somewhat more confusing.
>|||Ok, I think I see where you're going with this. I was thinking I could
use the ASPNET or NETWORK SERVICE account for both servers. But, that
doesn't appear to be the case. What you're saying is that I could
create a user on both servers, for example MY_WEB_USER. Then, set the
ASP.NET worker process to run as this account. I would also need to
give that user the correct permissions (similar to NETWORK SERVICE
probably). Sound about right?|||Yep,
That is what I had in mind.
Let us know how it goes.
Thanks
--
Vikram Vamshi
Eclipsys Corporation
"mcollier" <michaelscollier@.gmail.com> wrote in message
news:1109125129.410024.221630@.f14g2000cwb.googlegroups.com...
> Ok, I think I see where you're going with this. I was thinking I could
> use the ASPNET or NETWORK SERVICE account for both servers. But, that
> doesn't appear to be the case. What you're saying is that I could
> create a user on both servers, for example MY_WEB_USER. Then, set the
> ASP.NET worker process to run as this account. I would also need to
> give that user the correct permissions (similar to NETWORK SERVICE
> probably). Sound about right?
>
Subscribe to:
Posts (Atom)