TITLE: Connect to Server ------------------------------ Cannot connect to PETE. ------------------------------ ADDITIONAL INFORMATION: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was n

Question

I cannot connect to the remote SQL Server instance.

The error is:

TITLE: Connect to Server
------------------------------

Cannot connect to PETE.

------------------------------
ADDITIONAL INFORMATION:

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) (Microsoft SQL Server, Error: 1398)

Thanks,

---

Tom Childers, Radio Amateur N5GE, Licensed since 1976, QCWA Member 35102, ARRL Life Member

Answer 1

Hi,

Follow the article below regarding sql server config manager:

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

Run an odbcping. Go to run command and type odbcad32. Go through the wizard and see if you have a successful connection. Try it remotely and then locally on the server.

---

A SQL Server MVP or MSFT Eng should be replying soon as well. Hope this helps. Frank Garcia *** Please select "Vote As Helpful" if the information provided was helpful to you. If an answer to your issue solved the problem then please mark it as "Propose As Answer" located at the bottom. Thank you. ***

Answer 2

Hello,

I would suggest you to have a look at http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/e03993c0-a5f5-40c1-8124-c99b7866b933 ( one of the first sticky threads of this forum )

More generally, i would suggest to have a look at http://blogs.msdn.com/b/sql_protocols/ where you will find several articles about your problem , for example

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/16/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error-xxx.aspx

Have a nice day

---

Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

Answer 3

There are many reasons of SQL server connectivity issue. Refer checklist to find out the real cause of connectivity issue.

1. Check SQL services are running

2. Check SQL Browser service is running

3. Check remote connections are enabled

4. Network connectivity between database & application servers by TRACERT command

5. Check TCP/IP protocol enabled at SQL server

6. Check talent connectivity – telnet <IP address> <port no on SQL server running>

7. Check UDP port 1434 is open or not on SQL Server

8. Check firewall is running or not Check

9. If firewall running, SQL Server & UDP port must be added in exception in firewall

10. Run SQL Discovery report on machine SQL server installed, to check you are using correct instance name to connect( default \named) -http://mssqlfun.com/2013/02/26/sql-server-discovery-report/

http://mssqlfun.com/2012/09/28/check-list-for-sql-server-connectivity-issue/

---

Regards,
Rohit Garg
(My Blog)
This posting is provided with no warranties and confers no rights.
Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

Answer 4

Rohit,

Thank you for you answer.

Here are the settings I have changed and the results:

Firewall off: Instant connection.

Domain Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

Private Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

Public Profile: Inbound connections changed from Block to Allow. (No results) Time Out at 15 seconds

All three of the above set to Allow (No Results) Time Out at 15 seconds

IPSec Settings: All computers on the domain added to Only Allow Exceptions. (No results) Time Out at 15 seconds

IPSec Settings: Added Domain Admins to Only Allow Authorized list.

Are there any other firewall settings I can try resetting?

---

Tom Childers, Radio Amateur N5GE, Licensed since 1976, QCWA Member 35102, ARRL Life Member

Answer 5

Hi Tom,

Please connect to SQL Server with SQLCMD on the server and check whether the issue occurs. Additionally, please ping the server on the client side, and increase the SQL Server “connection timeout” value and check the result again. There is a similar issue on the following link, you can also refer to it:

http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f2d4ab2b-02d2-4751-9dbe-f243f1a27d0a/

If you have any feedback on our support, please click here.

---

Allen Li
TechNet Community Support

Answer 6

Rohit,

Thank you very much.

Adding UDP port 1434 solved the problem.

Thanks for all you do my friend.

---

Tom Childers, Radio Amateur N5GE, Licensed since 1976, QCWA Member 35102, ARRL Life Member