| Author |
Topic |
|
robc
Yak Posting Veteran
60 Posts |
 Posted - 2008-10-09 : 18:36:15
|
| For some odd reason, I cannot seem to connect via Management Studio to my 2008 server. I have not changed any settings on my box nor have i changed anything via MS. I Don't think it's a firewall issue because i turned the firewall off and still couldn't connect. Here is my 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) (.Net SqlClient Data Provider)Thanksrc |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 18:43:04
|
| If its MS SQL 20051. Enable remote connections in the surface area scan.2. Enable TCP/IPIn 2008 MS SQL, enable TCP/IP in MS SQL configuration manager |
 |
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 18:56:35
|
| Thanks for your response.TCP/IP is enabled. Yet still it will not connect. It is sql2008.The error number I got was 1231[url]http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=1231[/url]this is what microsoft pointed me to. But i don't quite understand. |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 19:00:43
|
| How are you trying to connect ?management studio ? use IPAddress,port number(1433)usernamepassword |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 19:03:29
|
| From that error, I would ask. did you create an account to login and assign the appropriate permissions ? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 19:11:25
|
| Yes, I'm connecting via mangement studio.Everything has been working fine up until this morning when I woke up and tried to login. I tried adding the port number, but it still wouldn't connect. :(What could have randomly happened while I was asleep? Strange. |
|
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 19:15:37
|
quote:
Originally posted by tkizer
Try connecting with ServerName,PortNumber. Let us know how that goes.
Tara, i tried that and it didn't work either. I also tried;ip,1433\servername |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-10-09 : 19:20:11
|
| I don't understand what you mean by ip,1433\servername. That isn't a proper way to connect. Are you sure it is listening on 1433 as that's just the default? We don't use 1433. To verify if you've lost connectivity due to some network issue, telnet to the SQL Server over the port that it is listening on. You must do this on the machine where you are receiving the error and not on the database server.Here's an example: telnet Server1 28999Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 19:22:56
|
| Tara,I tried to Telenet in and I got a "Could not open connection to host on port 1433 : connect failed" |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 19:23:37
|
| use this ip,1433instead of ip,1433\servername |
|
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 19:24:14
|
quote:
Originally posted by afrika
use this ip,1433instead of ip,1433\servername
Hey Afrika,tried that and it also didn't work :( |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 19:25:06
|
| Try what Tkizer said, telnet and see if you get a response.If not, then your server is not listening on that port |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2008-10-09 : 19:40:38
|
quote:
Originally posted by tkizer
quote:
Originally posted by afrika
Try what Tkizer said, telnet and see if you get a response.If not, then your server is not listening on that port
Well that's not the only reason why telnet wouldn't work. There are lots of reasons why. We need to eliminate things.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog
Ok.I setup MS SQL 2008 last month. Setup was smooth. Still trying to get a hang of the changes |
|
|
|
robc
Yak Posting Veteran
60 Posts |
Posted - 2008-10-09 : 23:16:44
|
| Well, turns out my hosting provider blocked ports 1433,1434. Took them long enough to respond to me :(Thank you everyone for your help. It is now working on a different port. :) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
helpme
Posting Yak Master
141 Posts |
Posted - 2009-02-18 : 14:32:10
|
| Is there a way to tell what ports are available? I'm having the same issue when trying to telnet using port 1433. |
|
|
|
|
Suddenly can't connect remotely to server