| Author |
Topic |
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
 Posted - 2007-10-22 : 12:54:29
|
| I have a sql server 2005 remotely, need to connect from client using sql management studio. I am unable to connect from one of the client machine and able to connect from different machine.The tcp/ip, named pipes and sql browser is enabled in server and windows firewall is off in client. I am getting (provider: sql network interfaces, error 26 - error locating server/instance specified)Please throw your suggestions. |
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-10-22 : 13:17:43
|
Can you ping the SQL Server from the client? Is there possibly another firewall or access list between that client and the server?
Future guru in the making. |
 |
|
|
ratheeshknair
Posting Yak Master
129 Posts |
Posted - 2007-10-22 : 13:40:45
|
| Are u connecting to sql server 2005 express edition?RKNAIR |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-22 : 14:00:35
|
| Follow the troubleshooting steps that I had a previous user go through to fix connectivity issues: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=90787Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-22 : 18:01:11
|
quote:
Originally posted by ratheeshknair
Are u connecting to sql server 2005 express edition?RKNAIR
Nope, am connecting Sql server 2005 |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-10-22 : 22:03:57
|
| Did you try tkizer's steps? |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-23 : 03:16:39
|
| I followed Kizer steps, when navidating through HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo i could see alias Name - 81.27.111.47\SQL2005 ,Type Reg-SZ, Data - DBMSSOCN,81.27.111.47\sql2005When i telnet 81.27.111.47 1433 - Couldn't open connection to the host, on the port 23:connect failed.But i can ping the 81.27.111.47 and from the another client machine the server can be connected using management studio.Thanks in advance. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-23 : 12:04:16
|
| Your alias is not correct. There should be a port in there. Also you shouldn't specify the instance name inside the data portion, only in the alias name.If you can't telnet to the port, then you've got a network or config problem.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-10-23 : 22:31:33
|
| >> Couldn't open connection to the host, on the port 23:connect failedtelnet is disabled on your network. |
|
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-10-23 : 23:21:50
|
Try telnet from the working machine, if it works then it suggests a more restrictive access policy on the problem machine. You would need to find out from your network admins what the differences are. If telnet is blocked on both machines then that test is invalid, you will want your network admin to assist anyway to rule out the firewall.
Future guru in the making. |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-24 : 19:18:25
|
Telnet fails in other machine as well. The client config is given in image inserted.Please let me know if i miss anything in configuration[   |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-24 : 19:25:00
|
| We can't see your images.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-24 : 19:36:05
|
| Sorry, DO you mind reciving the email of the images. Could you email your id to h_zulfi@yahoo.com please, am really stuck |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-24 : 19:43:40
|
| Sorry the image insert is not working i think, i have uploaded images here http://picasaweb.google.com/h.zulfi/SQLClientConfiguration |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-24 : 19:52:29
|
| I'm not sure why you'd want to use what you have for the alias name, but okay. Personally I'd use the hostname of the database server in the alias name rather than the IP address. It's the connection portion where you need the IP address if DNS is resolving hostname to IP.Could you expand the server alias field so that we can see the entire thing. You can't have duplicates in there, but we aren't able to see the entire field in the image.Are you sure that the instance name was installed as SQL2005? Are you sure that the instance is listening on port 1433?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-24 : 19:58:28
|
quote:
Originally posted by tkizer
I'm not sure why you'd want to use what you have for the alias name, but okay. Personally I'd use the hostname of the database server in the alias name rather than the IP address. It's the connection portion where you need the IP address if DNS is resolving hostname to IP.Could you expand the server alias field so that we can see the entire thing. You can't have duplicates in there, but we aren't able to see the entire field in the image.Are you sure that the instance name was installed as SQL2005? Are you sure that the instance is listening on port 1433?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/
The instance name was SQL2005, i can use the sam instance name when antoher machine is getting connected.I added the new image where alias name is visible correctly on http://picasaweb.google.com/h.zulfi/SQLClientConfiguration |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-24 : 20:15:16
|
| Get rid of the second alias. Modify the first alias so that the connection parameter says: 81.27.111.47\SQL2005,1433. Once that is complete, try connecting in SSMS with 81.27.111.47\SQL2005.1433 is typically used for the default instance, so you really should make sure that 1433 is being used for the SQL2005 instance.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-25 : 05:11:09
|
| I removed the first instance only 81.27.111.47\SQL2005,1433 is there and tcp/ip port attribute is 1433.But still no luck. Whether the Config in Named Pipes is right??? http://picasaweb.google.com/h.zulfi/SQLClientConfiguration |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-25 : 11:56:16
|
| I don't think you did what I asked. The alias that had 1433 in its name needs to be removed. The alias name should be 81.27.111.47\SQL2005 and its connection parameter should be 81.27.111.47\SQL2005,1433. 1433 should not appear in the alias name, only inside it.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
h_zulfi@yahoo.com
Starting Member
12 Posts |
Posted - 2007-10-25 : 13:15:46
|
| I have done that and included the image in url.http://picasaweb.google.com/h.zulfi/SQLClientConfigurationThe error is changed from error:26 to error:0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond.)(Microsoft Sql Server,error:10060.) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-25 : 13:28:56
|
| I'd check with your network admins then to figure out what is preventing you from connecting.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
Next Page
|
Connecting sql server remotely