unable to connect to domain sql server

Question

1.00/5 (1 vote)

See more:

SQL-Server-2008R2

hi guys,

i'm not able to the domain network.

when i'm trying to connect, i'm getting 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)

i have created new rule in windows fire wall for port 1433.

and enabled TCP/IP.

but still i'm not able to connect..

please help me guys.

Thanks.

Posted 25-Jan-15 6:16am

abdul subhan mohammed

Updated 25-Jan-15 6:17am

v2

Add a Solution

Comments

MT_ 25-Jan-15 12:50pm

Check if comments at http://blogs.msdn.com/b/sqlexpress/archive/2005/05/05/415084.aspx helps...Milind

Kornfeld Eliyahu Peter 25-Jan-15 14:13pm

Can you ping the server by name and or IP?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_Asif_ · Answer 1 · 2015-01-25T20:10:00

Solution 2

Try doing a telnet <ip> 1433 and see if its get connected or not. If its not that means you have not correctly created rules for firewall.

Posted 25-Jan-15 20:10pm

_Asif_

Updated 25-Jan-15 21:09pm

v2

Comments

abdul subhan mohammed 26-Jan-15 3:03am

i haved added win features for telnet, run cmd. in which i have typed 'telnet'
n its run. now to check with telnet 1433??

abdul subhan mohammed 26-Jan-15 3:09am

i have typed 'telnet ip port#' n i get blank screen which means the connection connected successfully! but still i'm unable to connect to remote database.

_Asif_ 26-Jan-15 3:10am

Do Telnet IP 1433 like Telnet 127.0.0.1 1433 and see whether its connected to the remote port or not

_Asif_ 26-Jan-15 3:17am

If you are connected that means there is no network issue at all and problem is in your application, check your connection string, server name, instance name.

Wendelius · Answer 2 · 2015-01-25T18:08:00

Few things to check:

Is TCP/IP enabled for the SQL Server
Is the port 1433 in use or has it been changed (easiest to check from errorlog)
Is the instance a named instance and have you provided the name in connection string
Are all the firewalls allowed to pass through the conversation to the correct port, including the server computer firewall