Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
getrex
Starting Member
1 Post |
 Posted - 2009-08-18 : 14:37:51
|
| This is the message: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: 2)My dedicated admin connection port is 51780My default port is 49161The things I did:1. I installed SQL Service Pack 3, but it's important to say that my SQL Server has never worked.2. I enabled TCP/IP connections in the Surface Area Configuration.3. In the Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\SuperSocketNetLib\Tcp\IPX I changed the TcpPort to my default port (49161)4. The same as step 3 a changed to my default port the port number in the Configuration Manager of my instance.5. I switched off my firewall (hehe).6. I created an alias and it doesn't work.Other details are:Can not connect using localhost, I just can connect using ServerName\InstanceName and the alias I created.In the network databases I don't see all of them and the ones I see I can't connect to them.Don't know if it's a security issue and/or compability issue? |
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2009-08-18 : 16:53:19
|
| You say that the SQL Server has never worked.What do you mean? - Is the service running?- Are there any errors in the errorlog? |
 |
|
|
amrosalah
Starting Member
6 Posts |
Posted - 2009-08-19 : 18:02:08
|
| Can you allow me to take a look at your machine ? I am willing to assist you in this .http://www.freesqltools.info |
|
|
|
|
|
|
Cannot connect SQL remotelly in W2K8