Connectivity Error(Sqlserver 2005 in Operating System Windows Server 2003)
-
Hi, I had Intalled Sqlserver 2005 for Dotnet 2.0 in PC on the Operating System Windows Server 2003 I had Installed Sqlserver2005 in Mixedmode Authentication, When I make the Connectivity, It Showing Error i.e Login Failed for user NT Authority\Network Server When I installed Sqlserver 2005 in same in WindowsXP it working well, But in WindowsServer2003 only it showning this Error I used Normal Connection Sting "server;uid;pwd;database;integrated security;" Give me reply as soon as possible.. when u know this info.. Thanking for you Balu
-
Hi, I had Intalled Sqlserver 2005 for Dotnet 2.0 in PC on the Operating System Windows Server 2003 I had Installed Sqlserver2005 in Mixedmode Authentication, When I make the Connectivity, It Showing Error i.e Login Failed for user NT Authority\Network Server When I installed Sqlserver 2005 in same in WindowsXP it working well, But in WindowsServer2003 only it showning this Error I used Normal Connection Sting "server;uid;pwd;database;integrated security;" Give me reply as soon as possible.. when u know this info.. Thanking for you Balu
I'm guessing that you're trying to make an ASP.NET website. Integrated Security uses the credentials of the thread making the call to authenticate with the database. Under Windows XP, IIS 5.1 knows nothing about ASP.NET. The ASP.NET runtime itself starts an ASPNET_WP.EXE worker process, which by default runs under the machine-name\ASPNET account. You can change this by editing the <processModel> element in machine.config. IIS 6.0 on Windows Server 2003 recognises ASP.NET natively, and uses a standard W3WP.EXE worker process. The worker processes use the identity configured in the Application Pool for the application, which by default is the NETWORK SERVICE account. You have three choices: - Create a database server login for the NETWORK SERVICE account; - Change the application pool's identity to a different account that already has a SQL Server login; - Use SQL Server authentication and pass a username and password in the connection string. Stability. What an interesting concept. -- Chris Maunder
-
Hi, I had Intalled Sqlserver 2005 for Dotnet 2.0 in PC on the Operating System Windows Server 2003 I had Installed Sqlserver2005 in Mixedmode Authentication, When I make the Connectivity, It Showing Error i.e Login Failed for user NT Authority\Network Server When I installed Sqlserver 2005 in same in WindowsXP it working well, But in WindowsServer2003 only it showning this Error I used Normal Connection Sting "server;uid;pwd;database;integrated security;" Give me reply as soon as possible.. when u know this info.. Thanking for you Balu
NT Authority\Network Server is anonyous user for ASP.NET 2.0 websites (in 1.1x it was called IUSER_MACHINENAME which is run under a protected thread by ASP.NET. If you change your IIS to Windows authenication it will pick up your current Windows authenication and pass this to SQL server. If you require anonyous access web internet then you need to provide an authenicated user to SQL 2005 either via SQL user connection or use impersonation via your web.config using the indentity
<indentity impresonate="true" userName="username" password="password">
Look where you want to go not where you don't want to crash. Bikers Bible
-- modified at 18:59 Friday 21st July, 2006
-
I'm guessing that you're trying to make an ASP.NET website. Integrated Security uses the credentials of the thread making the call to authenticate with the database. Under Windows XP, IIS 5.1 knows nothing about ASP.NET. The ASP.NET runtime itself starts an ASPNET_WP.EXE worker process, which by default runs under the machine-name\ASPNET account. You can change this by editing the <processModel> element in machine.config. IIS 6.0 on Windows Server 2003 recognises ASP.NET natively, and uses a standard W3WP.EXE worker process. The worker processes use the identity configured in the Application Pool for the application, which by default is the NETWORK SERVICE account. You have three choices: - Create a database server login for the NETWORK SERVICE account; - Change the application pool's identity to a different account that already has a SQL Server login; - Use SQL Server authentication and pass a username and password in the connection string. Stability. What an interesting concept. -- Chris Maunder
hi, Thnak u for your reply, I got that connectivity..