Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1076
  • Last Modified:

Unable to connect to SQL server 2008 R2 over the network

Server Config
-----------------
Server 2008 R2
SQL Server 2008 R2
SQL Server Configuration  Manager:
1) Protocols for MSSQLSERVER (TCP/IP Enabled)
2) IP10: IP Address 127.0.0.1, TCP PORT 1433
3) IP ALL: TCP PORT 1433

Firewall: MSSQL is listed 2 times:
1) Local: Any - 3306, Remote: 200.101.47.0/24
1) Local: Any - 1433, 1434, Remote: 200.101.47.0/24

ServerIP: svrParts-01 (Hostname), 192.168.1.5, 255.255.255.0, 192.168.1.1(Gateway), 192.168.1.2(DNS)

My System IP: systemo5 (Hostname),  192.168.1.34, 255.255.255.0, 192.168.1.1(Gateway), 192.168.1.2(DNS)

Hi,

I am trying to connect to a SQL Server 2008 R2 DB from my local system on the same network but not able to.  I can log into the SQL server using windows authentication or SQL Server Authentication (sa account ) no problem.  I

I tried to connect to my the server using SQL using a db connection in Visual studio but no luck:
Data source: Microsoft SQL Server (SQL Cliet)
Server Name: svrParts-01 or 192.168.1.5:1433
Use SQL Authetication: sa and password
connect to database: dbParts
Test Connection message: The server was not found or was not accessible. Verify instance name is correct and that SQL server is configured to allow remote connections. (provider: SQL Network Interfaces, error 25 - Connection string is not valid).

or

An error has occurred while establishing a connection to the server when connecting to SQL server 2005, this failure may be caused by the fact that under default settings SQL server does not allow remote connection. ( provider: Named Pipes Provider, error: 40 – could not open a connection to SQL server. )

Thanks in advance!
0
cesemj
Asked:
cesemj
  • 3
1 Solution
 
Aaron TomoskyTechnology ConsultantCommented:
The firewall looks odd. Turn off the firewall just to test. If that works, put the right ip addresses in there.
0
 
cesemjAuthor Commented:
You were right but how do I find which error is causing the problem,
0
 
cesemjAuthor Commented:
I'm sorry, how do  I find which rule is causing the error
0
 
cesemjAuthor Commented:
Thanks for your help, I found the location where to change the ip.  :)
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now