December 11, 2008 at 4:42 am
Hello,
We have a windows SBS 2003 SP2 machine, which has a public IP address. SQL server 2005 is installed on this machine. This machine also has a Visual Studio Source Safe (VSS) installed. We need to access this so we configured the VPN (Routing and Remote Access) on it. We can connect remotely to this server through the VPN and access the VSS. Please note that VPN (Routing and Remote Access) is not blocking anything, while configuring a VPN server, an option appears with a check box which says:
"Enable security on the selected interface by setting up static packet filters"
I did not check (select) it.
Now we want to access the SQL server remotely. So we enabled remote connections for SQL Server 2005 and also enabled the SQL Server Browser service. (How to configure SQL Server 2005 to allow remote connections http://support.microsoft.com/kb/914277)
Since VPN (Routing and Remote Access) is configured on this server the default firewall is disabled. So there is no need to create an exception for SQL Server 2005 in Windows Firewall.
I can ping this server from a remote machine on its public IP. But when we connect to it (http://www.aquesthosting.com/HowTo/Sql2005/connect.aspx) an error occurs:
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)
Please let me know how to fix it.
Regards
December 11, 2008 at 7:04 am
1- if the SQL Server is not using default port then u have to create an alias for it using fully qualified name
like "servername@domain.com".
in both ways try to create an alias.
2- connect using the server IP or its fully qualified name.
..>>..
MobashA
December 12, 2008 at 4:41 am
Hi,
Thanks for the reply. The problem is the it fails when I Test it while registering a new server. I specify the Server name (IP address only), Authentication (SQL Server Authentication), the login and the passowrd. In the Connection Properties Tab: Connect to database (the name of the db), TCP/IP as the Network protocol.
It raises the same error message.
December 12, 2008 at 5:37 am
Dear:
this error "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)"
may be coused by a million of things and it have nothing to do with SQL Server does not allow remote connections.
please could u answer my questions:
1- dose this server use a port other than the default one?
2- can u connect to this server throw Management Studio?
3- can u create an ODBC for the SQL Server?
4- is it default or named instance?
5- are the machines u r using on the same domain or one of the is on a work group?
..>>..
MobashA
December 15, 2008 at 9:46 pm
Hi,
Once again thanks for the reply:
You asked 5 questions, my answers are below them:
1- dose this server use a port other than the default one?
NO
2- can u connect to this server throw Management Studio?
NO, and this is the problem, I want to connect using Management Studio
3- can u create an ODBC for the SQL Server?
YES, but all I want is connection through the Management Studio
4- is it default or named instance?
DEFAULT
5- are the machines u r using on the same domain or one of the is on a work group?
It's on a domain, and mixed authentication mode, I try to access it with SA. Locally it works fine, the management studio connects to it but when we try it remotely, we get this error message.
Regards
December 15, 2008 at 10:55 pm
hay thanks for ur answers.
i think the solution is to create an alias for the server on the client PC u r using.
1- start--->run--->cliconfg
2- Alias--->Add.
3- from the network libraries choose TCP/IP.
4- on the connection parameters the server name should be a domain name.
..>>..
MobashA
December 16, 2008 at 12:51 am
Hi,
Thank you so much for helping me.
I added the alias as you suggested but what should I do now?
I explain the complete setup:
The machine on which SQL server is running has two network cards, one has a non routable private IP (192.168.1.1) and the other one has a public IP (193.x.x.x). This machine is a domain controller (Windows SBS 2003 SP2) also.
The problem is if any machine in the same domain and on the local area network tries to connect through management studio it works fine. for example I've another machine whose IP is 192.168.1.2, and it is on the same physical local area network. This machine can connect to it.
If we access this SQL server from some remote machine (not in the same physical Local Area Network), we need to connect through its public IP (193.x.x.x).
From a remote machine I can ping it (193.x.x.x) and there is no firewall enabled, a routing and remote access service was configured without packet filtering, that too I've removed. still no luck.
I'm trying to connect through the SA
Regards
December 16, 2008 at 1:52 am
try to connect using the alisa name.
any way i will check this with our network administrator he may have some solutions for us.
..>>..
MobashA
December 16, 2008 at 1:59 am
sure, I'll try.
Thank you so much for your support.
Regards
December 16, 2008 at 2:02 am
rajoo.sharma (12/16/2008)
Hi,Thank you so much for helping me.
I added the alias as you suggested but what should I do now?
I explain the complete setup:
The machine on which SQL server is running has two network cards, one has a non routable private IP (192.168.1.1) and the other one has a public IP (193.x.x.x). This machine is a domain controller (Windows SBS 2003 SP2) also.
The problem is if any machine in the same domain and on the local area network tries to connect through management studio it works fine. for example I've another machine whose IP is 192.168.1.2, and it is on the same physical local area network. This machine can connect to it.
If we access this SQL server from some remote machine (not in the same physical Local Area Network), we need to connect through its public IP (193.x.x.x).
From a remote machine I can ping it (193.x.x.x) and there is no firewall enabled, a routing and remote access service was configured without packet filtering, that too I've removed. still no luck.
I'm trying to connect through the SA
Regards
you can enable SQL Server options through "SQL Server Surface Area Configruation", for more info see SQL BOL.
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply