| Author |
 Topic  |
|
|
StephenD
Senior Member
Australia
1044 Posts |
 Posted - 30 January 2006 : 21:57:32
|
My host recently moved my sites and dbs across to a new Win 2003 Server and SQL 2005 server. I can no longer use EM to connect to my dbs. I have upgraded my home pc to SQL 2005 Standard Edition which comes with SQL Server Management Studio.
Couple of queries as I have exhausted google and books online:
1. My previous Server Alises appear in SQL Server Configuration Manager but when I open up SQL Server Management Studio (SSMS) I can't seem to call those aliases in any of the connection property dialogs.
2. In SSMS if I try to connect to one of my host's dbs by specifying the dns or IP address and login credentials I get the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to 203.84.233.54.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not 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
I've checked with my host and they say there are no settings that need changing at their end. My static IP address is allowed through their firewall.
Anyone got any ideas? |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 31 January 2006 : 05:06:41
|
| Not sure about it, since just started using SQL Server 2005, but the default installation settings does not install the TCP/IP network library, so check your own installation to make sure the library is installed. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
StephenD
Senior Member
Australia
1044 Posts |
Posted - 31 January 2006 : 06:24:16
|
| I've checked and tried to modify the install but it says I've already installed everything - database, management tools, connectivity. |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 31 January 2006 : 06:34:18
|
Get to SQL Server Configuration Manager, on the left choose SQL Server Network Configuration -> Protocols for MS SQL Server, and then on the right enable TCP / IP.
I should have wrote that it is disabled by default, not that it is not installed. Maybe your host has the same problem... |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
StephenD
Senior Member
Australia
1044 Posts |
Posted - 31 January 2006 : 06:39:20
|
| Ok, it was enabled when I looked now, i think I might have enabled it yesterday when I was trying to get it working. I've also enabled named pipes and VIA. I'll check with my host to see if it is enabled at his end. Thanks Rui |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 31 January 2006 : 17:45:47
|
| I've been trying to get acquainted with this new SQL Server version, and I think I may have found a setting that may be related to your situation. By right clicking the server in SQL Server Management Studio and choosing properties, you'll get a window with the different properties. One of those is connections. Clicking it will show several properties, including a check box to allow remote connections to the server. This was checked by default on my installation (a SQL Server Developer Edition). Maybe your host have not enabled this option for their server...Probably worth checking. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
StephenD
Senior Member
Australia
1044 Posts |
Posted - 02 February 2006 : 05:53:19
|
quote:
Originally posted by ruirib
I've been trying to get acquainted with this new SQL Server version, and I think I may have found a setting that may be related to your situation. By right clicking the server in SQL Server Management Studio and choosing properties, you'll get a window with the different properties. One of those is connections. Clicking it will show several properties, including a check box to allow remote connections to the server. This was checked by default on my installation (a SQL Server Developer Edition). Maybe your host have not enabled this option for their server...Probably worth checking.
Thanks Rui, I forwarded your information to my host and they say they made this change but I still cannot connect. Does anyone have a temporary SQL 2005 db I can try connect to so I can rule out my installation?
Cheers |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 02 February 2006 : 06:14:55
|
| Stephen, I believe those settings changes only become effective after the server has been restarted. Likely your host didn't do that (the fact that they needed my info to allow remote connections makes me think that is the most likely situation). |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
StephenD
Senior Member
Australia
1044 Posts |
Posted - 02 February 2006 : 06:22:49
|
| Ok, Rui, I've fired off an email to them and I'll wait for the outcome. Wouldn't mind trying to connect to another remote db in the meantime... |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
| |
Topic |
|
Topic Locked
