March 30, 2009 at 12:14 am
Hi,
I have online server with Valid IP address and I have installed SQL 2000 enterprise with SP4 and Installed SQL 2005 enterprise edition too, with different instance name , on windows 2003 Standard with SP2.
Now tow sql server up and running but I have a problem:
I can connect to SQL2000 database's from remote client but I can't connect to SQL 2005 from remote clients, what should I do to can connect to SQL2000 and 2005 from remote client?
Thanks
March 30, 2009 at 1:15 am
for connect to SQL 2005 I do this steps :
- open SQL managment studion that instaled on my PC
- type this in server name texbox (server IP\SQL new instance name)
- select SQL server autentication from combobox
- type SA or other created user and pass
and then it give me this error:
Cannot connect to Server IP\sql2005.
------------------------------
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: TCP Provider, 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 has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
March 30, 2009 at 1:48 am
Please check ..
1) Some protocol is enabled on remote server TCP/IP or Named Pipes.
2) Remote Connection is enabled.
3) No firewall blockage between remote location and your computer.
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 30, 2009 at 2:05 am
Thanks for your replay
I checked :
1- Name Pipe and TCP/IP from SQL Server Configuration Manager tools and it show me tow protocol are enabled
2- Surface Area Configuration... show me Remote connection configured on (Local and remote connections ----> Using both TCP/IP and named pipes)
3- about firewall you should know that I have installed SQL2000 on this server now, and I don't have problem with it , and I know default port (1433) is open in firewall , you should know, server firewall is off now, but still I can't connect to SQL2005 only
March 30, 2009 at 2:12 am
Services are running? No issue in SQL Server starting up? Check the SQL Server Management logs to see what port it is on; since you have SQL 2000 on that server also it will get a different port then 1433.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 30, 2009 at 2:16 am
Hmm try this...
Look in the SQL Server 2005 Configuration Manager.
Under Network configuration, Protocols for (instance name).
Look at the properties for TCP\IP and look on the IPAddresses tab.
If TCP Dynamic Ports is set to 0, then set this to 1.
Then in TCP Port underneath specify a high level port not in use by your server.
Your 2005 instance will now always use this port, instead of dynamically assigning one - so punch a hole in your firewall to allow this.
March 30, 2009 at 3:01 am
Thanks for your replay
- now at the properties for TCP\IP and IP Addresses tab
in IP 1 part I set TCP Dynamic Ports to 1 and insert a static port number value in TCP Port for example (1010) and make allow rule for TCP.
Do I should change IP2 and IP3 and IPAll too?
and where I should set new port number to SQL2005 in my PC I mean is in Managment studio
March 30, 2009 at 3:35 am
I think you need to set this for whichever IP Address SQL Server is actually using.
Looking at the configuration I have in front of me on my PC, I just have IP1 (which is the IP Address of my NIC) and IP2 (which is the loopback address).
You may have more, in which case choose whichever address is the appropriate one for SQL Server.
If you PING the server name from the command prompt, take a look at which IP address you get a response from.
As for configuring ports on the clients - you won't need to do anything on them BUT you do need to ensure that the "SQL Server Browser" service is running on the SQL Server in question. This is what is responsible for broking connections between clients and multiple instances of SQL Server (and is why you won't need to specify a port on the client).
Hope that helps!
March 31, 2009 at 11:50 am
Hello
-IP1 is my default server IP and I add new port on this part,
-SQL Browser is UP and runing
But Ican't connect to SQL 2005 from remote client it give me this error:
Cannot connect to server IP\sql2005.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
April 1, 2009 at 9:58 am
Hmm ok so on your firewall you are allowing TCP 1433, and TCP xxxx (the high level port you manually assigned to your non-default instance).
Can you try allowing UDP 1434 as well and try that please?
April 1, 2009 at 12:21 pm
Hi,
I have opened 1434UDP befor open this topic
Now I have opened this ports for SQL2005:
1 - 1434UDP
2- 1433 TCP
3 - 1911 TCP (new port )
4- I have allowed sqlbrowser.exe from installed SQL2005 path
5- I have allowed sqlservr.exe from installed SQL2005 path
but I can't connect to sql2005
April 2, 2009 at 3:40 am
That's puzzling, I thought that would be all you would need to do.
So after restarting the server, if you look in the SQL Server log for the named instance, you see something like "Server is listening on 1911" ?
As far as I know, if the firewall is configured to allow those ports mentioned, and your server is configured as you previously described, then you should be able to connect.
April 3, 2009 at 7:07 am
Hi, I have exactly the same problem... so I follow this thread .... If you help out, at least you help two of us...
April 3, 2009 at 7:18 am
Hi again, one of my collegues has solved it. Look in registry ; HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\LastConnect
Delete the entry for the server and try again. It worked for us..... (Look for your server or IP in registry, maybe this is not the right entry above so be careful...)
/Petter
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply