IIS7, Windows Web Server 2008 Web Edition and Remote SQL Server Database connection
I have been trying to setup my IIS7 on my windows web server 2008 web edition to connect to my remote sql server 2000 database.
Is this version, web server 2008 web edition, going to allow connection to a remote sql server database, considering it does not have Active Directory?
I have tried every possible configuration and can't get a connection, whether windows authentication or sql server authentication.
So am I spinning my wheels trying to get it to work, when it requires Active Directory?
Would Microsoft really sell a product for web servers that does not allow a remote sql server database connection?
Please let me know if you have done this with a web server edition. Please please please!
I just don't think there are that many people who have even used IIS7 to know an answer, because I've asked tons of questions and just dont' find any answers.
thanks.
Is this version, web server 2008 web edition, going to allow connection to a remote sql server database, considering it does not have Active Directory?
I have tried every possible configuration and can't get a connection, whether windows authentication or sql server authentication.
So am I spinning my wheels trying to get it to work, when it requires Active Directory?
Would Microsoft really sell a product for web servers that does not allow a remote sql server database connection?
Please let me know if you have done this with a web server edition. Please please please!
I just don't think there are that many people who have even used IIS7 to know an answer, because I've asked tons of questions and just dont' find any answers.
thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also, please, I have written numerous detailed posts on this on what I have tried and what to try.
In this post I have written a specific question if it's doable. So please respond if you know for a fact if it is or not, BY EXPERIENCE.
Not a hunch or guess or what you think it's supposed to be. I need to know if someone has indeed ever gotten it to work. Because otherwise, I'll have to buy the standard edition and move on. I've already wasted enough time on this and time is money. I could have purchased the standard edition with the time I've wasted on this.
In this post I have written a specific question if it's doable. So please respond if you know for a fact if it is or not, BY EXPERIENCE.
Not a hunch or guess or what you think it's supposed to be. I need to know if someone has indeed ever gotten it to work. Because otherwise, I'll have to buy the standard edition and move on. I've already wasted enough time on this and time is money. I could have purchased the standard edition with the time I've wasted on this.
Hi,
In a previous role we had Windows 2003 Server Web Edition running in a DMZ. It connected to databases in the internal lan using SQL Authentication.
I installed the OS on this machine, and migrated the existing web-sites there.
I installed SSL on two web-sites, which required additional IP's to be mapped from the WAN to the DMZ.
I will admit to not having done this with IIS 7.
Is down-grading to IIS6 an option?
Cheers
David
In a previous role we had Windows 2003 Server Web Edition running in a DMZ. It connected to databases in the internal lan using SQL Authentication.
I installed the OS on this machine, and migrated the existing web-sites there.
I installed SSL on two web-sites, which required additional IP's to be mapped from the WAN to the DMZ.
I will admit to not having done this with IIS 7.
Is down-grading to IIS6 an option?
Cheers
David
ASKER
dtodd,
I thought you meant sql authentication in the connection string. That never worked for me.
But when I was pulling out my hair trying to setup a sql server 2000 security user, I noticed a radio button for sql server authentication and tried it.
That works. So Step#5 below, use sql server authentication instead of windows authentication, but still use windows authentication in the connection string in the web config.
(i)Add the Windows account to SQL Server:
1.
Start Enterprise Manager.
2.
Expand Microsoft SQL Server, and then expand SQL Server Group.
3.
Expand your server, and then expand Security.
4.
Right-click Logins, and then click New Login.
5.
In the SQL Server Login Properties dialog box, enter the Windows account name in the Name box. In the Domain list, select the domain that the Windows account is a member of.
6.
Click the Database Access tab, set the appropriate permissions for the client, and then click OK.
thanks!
I thought you meant sql authentication in the connection string. That never worked for me.
But when I was pulling out my hair trying to setup a sql server 2000 security user, I noticed a radio button for sql server authentication and tried it.
That works. So Step#5 below, use sql server authentication instead of windows authentication, but still use windows authentication in the connection string in the web config.
(i)Add the Windows account to SQL Server:
1.
Start Enterprise Manager.
2.
Expand Microsoft SQL Server, and then expand SQL Server Group.
3.
Expand your server, and then expand Security.
4.
Right-click Logins, and then click New Login.
5.
In the SQL Server Login Properties dialog box, enter the Windows account name in the Name box. In the Domain list, select the domain that the Windows account is a member of.
6.
Click the Database Access tab, set the appropriate permissions for the client, and then click OK.
thanks!
ASKER
oh, btw, I did not have to open the firewall.
I just used the local IP address for the web.config connection string, instead of the remote IP.
I just used the local IP address for the web.config connection string, instead of the remote IP.
ASKER
(As I said, quote: I have tried every possible configuration and can't get a connection, whether windows authentication or sql server authentication.)