Prev: ANN: Database Workbench 4.0.3, the multi-DBMS IDE now available!
Next: Did this ever get resolved?
From: SAFEKOM on 13 Jul 2010 13:00
Problem:
How can I access SQL server on WAN????????????????????????????????
-----------------------------------------------------------
Error:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
------------------------------------------------------------------------
Information:
Windows Sever 2008 (64bit OS) Service Pack 2
Microsoft SQL 2008 Server Management Studio (10.0)(64bit)
Microsoft .Net Frame work 3.5 SP1
------------------------------------------------------------------------------

Additional Information:
IIS 7 installed
In TCP/IP properties TCP Dynamic ports : 49157
All services are running except SQL Server Agent(instance name), and their
start mode is automatic.
There is not any Alies configure that have problem .
------------------------------------------------------------------
What I already done:
1) SQL SERVER is up and the instance connect is running.
2) All required ports on Firewall is open/ also try to disable Firewall but
no success.
3) TCP/IP protocol is ENABLE. SQL SERVER port is by Default 1433.
4) Also try this:
the probelm is the Instance name from the client is not resolved, to do that
follow the below shown steps.
1. navigate to C:\Windows\System32\drivers\etc
2. Open hosts file in notepad
3. add the entry at the end of line, as i did for example
213.165.131.65 KSSQLSRVR
213.165.131.65 KSSQLSRVR\SPDEV01
those were my instances i am tried to connect remotely
5) In Server Name I tried IP address of Server (also with port number like
213.165.131.65,1433 )and also server name and instance name.
I m pulling out my hairs becoz of ANNOYING error. KINDLY HELP ME OUT OF THIS.

M Nasir.

From: Dan on 14 Jul 2010 05:29
How about changing the client protocol order? The error states that Named
Pipes is being used and cannot open a connection, which implies that TCP/IP
isn't being used. This might help:

http://msdn.microsoft.com/en-us/library/ms190425.aspx


Which driver are you using?

Dan



"SAFEKOM" <u61982(a)uwe> wrote in message news:aaf272a1d8d91(a)uwe...
> Problem:
> How can I access SQL server on WAN????????????????????????????????
> -----------------------------------------------------------
> Error:
> (provider: Named Pipes Provider, error: 40 - Could not open a connection
> to
> SQL Server) (Microsoft SQL Server, Error: 53)
> ------------------------------------------------------------------------
> Information:
> Windows Sever 2008 (64bit OS) Service Pack 2
> Microsoft SQL 2008 Server Management Studio (10.0)(64bit)
> Microsoft .Net Frame work 3.5 SP1
> ------------------------------------------------------------------------------
>
> Additional Information:
> IIS 7 installed
> In TCP/IP properties TCP Dynamic ports : 49157
> All services are running except SQL Server Agent(instance name), and their
> start mode is automatic.
> There is not any Alies configure that have problem .
> ------------------------------------------------------------------
> What I already done:
> 1) SQL SERVER is up and the instance connect is running.
> 2) All required ports on Firewall is open/ also try to disable Firewall
> but
> no success.
> 3) TCP/IP protocol is ENABLE. SQL SERVER port is by Default 1433.
> 4) Also try this:
> the probelm is the Instance name from the client is not resolved, to do
> that
> follow the below shown steps.
> 1. navigate to C:\Windows\System32\drivers\etc
> 2. Open hosts file in notepad
> 3. add the entry at the end of line, as i did for example
> 213.165.131.65 KSSQLSRVR
> 213.165.131.65 KSSQLSRVR\SPDEV01
> those were my instances i am tried to connect remotely
> 5) In Server Name I tried IP address of Server (also with port number like
> 213.165.131.65,1433 )and also server name and instance name.
> I m pulling out my hairs becoz of ANNOYING error. KINDLY HELP ME OUT OF
> THIS.
>
> M Nasir.
>



From: SAFEKOM via SQLMonster.com on 14 Jul 2010 12:23
I am using TCP/IP protocol, do i need to disable all the other protocol
except TCP/IP???

How to fix the error of Name Pipes is being used?

Could you please advice me which protocol do i use and how to configure it
properly, let me tell you agian i want to connect my SQLEXPRESS database over
Internet.

i Telnet the server ip with port 1433, but it did not connect with it.



Dan wrote:
>How about changing the client protocol order? The error states that Named
>Pipes is being used and cannot open a connection, which implies that TCP/IP
>isn't being used. This might help:
>
>http://msdn.microsoft.com/en-us/library/ms190425.aspx
>
>Which driver are you using?
>
>Dan

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/201007/1

From: SAFEKOM via SQLMonster.com on 14 Jul 2010 14:34
Is there any other way to connect SQL server over internet remotely?

SAFEKOM wrote:
>I am using TCP/IP protocol, do i need to disable all the other protocol
>except TCP/IP???
>
>How to fix the error of Name Pipes is being used?
>
>Could you please advice me which protocol do i use and how to configure it
>properly, let me tell you agian i want to connect my SQLEXPRESS database over
>Internet.
>
>i Telnet the server ip with port 1433, but it did not connect with it.
>
>>How about changing the client protocol order? The error states that Named
>>Pipes is being used and cannot open a connection, which implies that TCP/IP
>[quoted text clipped - 5 lines]
>>
>>Dan

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/201007/1

From: Fred on 15 Jul 2010 01:14


"SAFEKOM" <u61982(a)uwe> a écrit dans le message de groupe de discussion :
aaf272a1d8d91(a)uwe...
> Problem:
> How can I access SQL server on WAN????????????????????????????????
> -----------------------------------------------------------
> Error:
> (provider: Named Pipes Provider, error: 40 - Could not open a
> connection to
> SQL Server) (Microsoft SQL Server, Error: 53)

> In TCP/IP properties TCP Dynamic ports : 49157

With SqlServer Configuration Manager, you must set a fixed port, and not
use dynamic port.
TCP Dynamic Ports : (erase and leave blank)
TCP Port : 1433 (or another one)


--
Fred
foleide(a)free.fr

 |  Next  |  Last
Pages: 1 2 3
Prev: ANN: Database Workbench 4.0.3, the multi-DBMS IDE now available!
Next: Did this ever get resolved?