Hi,
I used this command in the browser url, is it correct?
When I tried in the command prompt it complained it couldn't find telnet.
Peter
Hi,
I'm trying to connect to a Microsoft sql server 2008 that is on the network but not on the same server as the application. I 'm using asp.net
The server name is websql and has an internal ip in the network 10.0.0.39. I can connect to the server though windows explorer and I can ping the server. I have actrivated sql server browsing in services.. This is how my connection strinbg looks like:
-----------------------
<add name="connDB" connectionString="Data Source=websql;Initial Catalog=myDB;User id=username;Password=xxxxx
I've also tried:
<add name="connDB" connectionString="Data Source=10.0.0.39;Initial Catalog=myDB;User id=username;Password=xxxxx
--------------------------
When I do so I get this error:
----------------
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
--------------------------
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
> I used this command in the browser url, is it correct?
> telnet://10.0.0.39 1433/
no, that wouldn't work.
> "Could noit open connection to the host, on port 1433 Connection failded."
this actually tells you that it is impossible to either leave your computer under that port or to enter the other computer under that port. If you use a proxy or an external firewall, it must be configured to allow communication on this port on this subnet, if you use Windows Firewall, disable it temporarily to see if things improve, the same for any other local firewall.
A firewall is the most likely cause. However, you can also go to the 10.0.0.39 machine and try the same command for localhost:
telnet localhost 1433
which should work. If it does not work, SQL server is not correctly configured. If it does work, it will show you what to expect once the ports are configured correctly in the firewalls.
PS: if you are not familiar with firewall principles, it is a good idea to make sure that you disallow connections from outside your domain or subnet mask while you are experimenting with this, otherwise when you're disabling the firewall you might be open to attacks...If you use ADSL or Cable, you can check your settings in the modem.
Did you have SQL Management Studio installed in your appServer? It's better try to resolve the connection problem to SQL Server first and then try to connect your app. You can also try to set an ODBC from your client machine to test if you can connect.
Here you have a check list:
1) Remote connections enabled
2) Protocols TCP/IP and/or Named Pipes enabled
3) TCP/IP port is set to 1433
4) If it is a named instance you need to use machinename\InstanceName as the server name
5) Windows Firewall (create a TCP port 1433 for incoming connections)
After you have resolved the problem with remote connections to that server you can try to check you connection string. Here you a have a link with many examples: http://www.connectionstrin
I think this has to do something with Firewall.
Check following article:
http://blog.sqlauthority.c
Regards,
Pinal
Though I believe you have good points, jaryco, there can be many things that go wrong or are typed incorrectly (see your point 4) when trying to connect through ODBC or the management studio. Using telnet is not meant to solve the problem, but it is a 30 second approach to find out whether there actually is a connection possible.
As we know now, there is no connection on that port. I have received no information yet about the firewall from the OP. And I don't know yet whether it is a home environment where all connections go through a router acting as hub/modem or whether more things are at play.
Bottomline: if comp A wants to talk to comp B then the connection must be establishable (telnet). They can reach each other (ping) but they cannot talk on port 1433. As said earlier, this is likely a firewall problem.
In my original comment I suggested how to check connectivity with the database server. I believe that's a valid answer. Unfortunately, the asker has not gotten back with additional info. Not for the points, but for the PAQ, I believe this question should not be deleted.
With or without points, the way to start troubleshooting this type of problem is in http:#24008463
Business Accounts
Answer for Membership
by: abelPosted on 2009-03-28 at 06:40:55ID: 24008463
Though there can be numerous reasons for this error, let's look at the most obvious: the port. Since you do not specify a port, it should be the default port, which is 1433. To find out whether that port is open on the target computer or on the client computer, try:
telnet 10.0.0.39 1433
from the client computer's command prompt. If it waits for 20 seconds and then says it cannot connect, the port is not open or there's nothing listening on the port on the target server. Check your firewall and open the port and try again. If you immediately get a response from telnet (window goes black and you see some message on the top left of the screen) then you do have the port open and we will proceed from there.