Unable to remote connect, SQL Server, Error: 1326

Question

SQL Express running on Server 2003 SP1, not a domain controller - but prior to installing SQL Express, I did dcpromo promote and then demoted it back to a workgroup server.

Connecting with Vista build 5600, Studio express 9.00.2047 with MDAC 6.00.5600.1638. Server 2003 MDAC  is 2.82.1830.

I came across this article on the net:

http://www.developersdex.com/sql/message.asp?p=1867&ID=%3C309C7496-F36B-4398-9C52-322E6CB8DE3B%40microsoft.com%3E

Is my mis-matched versions of MDAC causing me this grief?

Otherwise, I have remote set up for TCP and Named Pipes, I've run sp_configure 'remote admin connections', 1; my login is set to SQL Authentication with everything granted. I've tried running the service as network, local and Machine\Administrator; ports are open per:

http://support.microsoft.com/kb/555585

I wanted to ask before I start replacing the MDAC on either the Vista or Server 2003 machine... If that's the problem, which version(s) do I change? to?

Full error message:

An error has occurred while establishing a connection to the server. While connecting to SQL Server 2005, this failure may be cuased by the fact that under the default settings SQL Server does not allow remote connecitons, (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326)

Thanks, John

 

 

Answer 1

Moving to the Express forum.

Answer 2

It's possible, even likely, that SQL Express is not listening on port 1433. By default, we use dynamic TCP ports, which is why you need SQL Browser in the first place. Check out http://support.microsoft.com/kb/914277 which it a different take on enabling remote connections through the firewall.

Mike

Answer 3

Thanks, this worked straight away.

Sorry for the double post. Note to TechNet, when this thread was moved, it dropped off My Threads list.

 

Answer 4

It's possible, even likely, that SQL Express is not listening on port 1433. By default, we use dynamic TCP ports, which is why you need SQL Browser in the first place. Check out http://support.microsoft.com/kb/914277 which it a different take on enabling remote connections through the firewall.

Mike

I tried it too, but it still giving me the 1326 error, mmm now i'm going to if check the TCP/IP is enabled in the configuration manager...

Answer 5

according to 

http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/20fc7cde-3a05-4a4e-b71b-9c44e7b913ee/

below links will help

http://blogs.msdn.com/b/sql_protocols/archive/2009/09/21/connection-from-a-windows-service-could-be-blocked-by-firewall-even-if-firewall-is-disabled.aspx 

http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx 

http://blogs.msdn.com/b/sql_protocols/archive/2008/04/20/could-not-connect-to-x64-named-instance.aspx 

http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx 

http://blogs.msdn.com/b/sql_protocols/archive/2006/09/30/sql-server-2005-remote-connectivity-issue-troubleshooting.aspx 

http://blogs.msdn.com/b/sql_protocols/archive/2006/04/21/581035.aspx

http://blogs.msdn.com/b/sql_protocols/archive/2005/12/22/506607.aspx  

http://blogs.msdn.com/b/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx 

---

Regards,
Ahmed Ibrahim
SQL Server Setup Team
This posting is provided "AS IS" 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

Can you try the workaround by Luger in below link

http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/ccd60cbf-6ef7-46c9-9b3b-405a73756b3a

---

Regards,
Ahmed Ibrahim
SQL Server Setup Team
This posting is provided "AS IS" 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.