Solved

WebServer cannot access SQL 2008 server

Posted on 2011-09-02
3
357 Views
Last Modified: 2012-05-12
I am upgrading my application from using SQL 2000 to SQL 2008. The db server's IP address is 1.1.1.1.
When I installed SQL 2008, because SQL 2000 has the default instance name, I make SQL 2008 instance as 1.1.1.1/SQL2008.
My application on the db server can access 1.1.1.1/SQL2008 perfectly.
However, my asp.net web server in DMZ that cannot access the new SQL 2008 databae.
I configure the web.confg to put the server name as 1.1.1.1/SQL2008 but the connection does not work.
Then I added a new IP address, 1.1.1.2 on my db server and configured as a new SQL 2008's IP address in server configuration tool.
I could use ODBC to connect to 1.1.1.2 from my web server and establish an ODBC connection successfully. Thus, I know the firewall is not blocking the ports.
However, I still cannot confgiure my web.config to connect to the 2008 database by using 1.1.1.2 because SQL2000  is answering all the request before SQL 2008.
How can I make SQL 2000 to ignore all request that goes to 1.1.1.2 from my web server?
0
Comment
Question by:atlasdev
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 6

Expert Comment

by:c1nmo
ID: 36476564
Should be a backslash between server and instance name?

Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;
0
 

Author Comment

by:atlasdev
ID: 36476586
It was my typo in this issue. I did backslash.
Can Web.Config use DSN to connect to the db server?
0
 
LVL 6

Accepted Solution

by:
c1nmo earned 500 total points
ID: 36477116
Here's an example I use in web.config:

  <connectionStrings>
            <add name="dbCENConnectionString" connectionString="Data Source=S153\SQLEXPRESS;Initial Catalog=dbCEN;Integrated Security=True;Connect Timeout=200; pooling='true'; Max Pool Size=200" providerName="System.Data.SqlClient" />
    </connectionStrings>

0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

I was asked about the differences between classic ASP and ASP.NET, so let me put them down here, for reference: Let's make the introductions... Classic ASP was launched by Microsoft in 1998 and dynamically generate web pages upon user interact…
Hi all, It is important and often overlooked to understand “Database properties”. Often we see questions about "log files" or "where is the database" and one of the easiest ways to get general information about your database is to use “Database p…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question