Connecting to Sql Server 2k5 Enterprise

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.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Connecting to Sql Server 2k5 Enterprise

Author

Topic

rudesyle
Posting Yak Master

110 Posts

Posted - 2007-05-17 : 14:59:26

Hi All,

Just installed this on a server at work. From home (outside of our network), I cannot connect to this instance from Management Studio, as I'm getting the following error :

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 connection to a SQL Server)

However, if I try from Sql 2000 Enterprise Manager on another box in my house, I have no probem connecting.

And yes, the Server at work is configured to accept remote connections.

Any help would be much appreciated.

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-05-17 : 15:00:50

try enabling tcp/ip connections on the server

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-17 : 15:08:00

Try connecting via SqlServerName,PortNumber. Also tcp:SqlServerName,PortNumber. If those work, then a an alias can be added so that you don't have to remember the port.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

rudesyle
Posting Yak Master

110 Posts

Posted - 2007-05-17 : 15:11:35

[quote]Originally posted by spirit1

try enabling tcp/ip connections on the server

_______________________________________________
They are. Again, I can connect to this box, via 2000 QA on another box in my home. I can also ping the box no problem from the problematic box. It's just when I connect via Management Studio from the problematic box.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-17 : 15:29:26

Did you see my post?

Tara Kizer
http://weblogs.sqlteam.com/tarad/

rudesyle
Posting Yak Master

110 Posts

Posted - 2007-05-17 : 15:32:11

quote:
Originally posted by tkizer

Did you see my post?

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Yep, no dice on both.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-17 : 15:34:28

Could you show us exactly what you tried? Are you sure you used the correct port number?

Tara Kizer
http://weblogs.sqlteam.com/tarad/

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-05-17 : 15:34:45

this may be a silly question... but do you maybe have windows firewall enabled on your problem box?

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp

rudesyle
Posting Yak Master

110 Posts

Posted - 2007-05-17 : 15:41:32

quote:
Originally posted by tkizer

Could you show us exactly what you tried? Are you sure you used the correct port number?

Tara Kizer
http://weblogs.sqlteam.com/tarad/

AHHHH ... that did it. I was typing in the wrong port number. I was able to connect by entering tcp:sqlbox.server.com,1433

You guys are awesome, thanks!

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-05-17 : 15:46:36

So now we can add an alias so that you don't have to type that whole thing in.

Open up SQL Server Configuration Manager. Expand SQL Native Client Configuration. Right click on aliases, select new alias. In the alias name field, type in the name that you want to use. People typically use HostName or HostName\InstanceName for the SQL Server. In Port No, put 1433. In protocol, select TCP/IP. In server, put sqlbox.server.com.

You should now be able to connect to the alias in SSMS.

Tara Kizer
http://weblogs.sqlteam.com/tarad/

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources