sqlstate 08001 Error 53

Question

I am having a connectivity issue which I believe is more related to the machine trying to connect than the SQL server itself. In my environment I have 3 windows 2012 server that connect to SQL 2008 R2 using Native client 10 driver. 2 servers never have a problem, but one develops a connection problem in an almost random manner. When trying to connect I get the unable to connect via named pipes error when using Access DSN's or SQL Server Management studio. After rebooting the machine the error goes away for awhile only to show up later at some other random time. All machines in the equation are Windows server 2012 guest VM's hosted on Windows Server 2012 Hyper-V. Since all machines are Guest VM on the same host, it should not be a network related issue. Also the 3 machines accessing SQL server are running as Terminal Servers. I really have no idea how to track this down. We ran this same environment under 2008R2 with no issues. I would appreciate any help I can get here, I would not even know which MS group to call for support if needed.

---

Lee

Answer 1

this is the error show by SQL Server manager, the error now no longer goes away when the machine is rebooted.

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

Cannot connect to xxxxxx.

------------------------------
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: 53)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

------------------------------
BUTTONS:

OK
-----------------------------

Could the issue be related to domain controller connectivity?

---

Lee

Answer 2

Although, There are many reasons of SQL server connectivity issue. Small checklist that helps 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

Refer Link  : 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 3

Sorry but that does not apply in this situation, i.e. the problem is random. Other machines ARE able to access the database.

---

Lee

Answer 4

It seems the problem is some how related to domain controller connectivity. When I run "gpupdate /force" ion the failing machine, the problem goes away.

---

Lee

Answer 5

Include someone from AD & windows team to look into the 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 6

Check the Windows logs on that server? anything red flagging?

Check the through put?  Are you slamming it?

Answer 7

The logs show that its a Kerberos authentication problem which is why I am leaning towards a PDC issue not a SQL server one, so I will continue my discussions with active directory. Also if I login using SQL server authentication, not windows, it works.

---

Lee