--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
--
BUTTONS:
OK
--This is a multi-part message in MIME format.
--050904010205030506090301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
>TITLE: Connect to Database Engine
>--
>Cannot connect to VEGAS-W-DV-02.
>--
>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: Named Pipes Provider, error: 40 - Could not open a connection to
>SQL Server) (Microsoft SQL Server, Error: 233)
>For help, click:
>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>
--050904010205030506090301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl" type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</body>
</html>
--050904010205030506090301--|||This is a multi-part message in MIME format.
--=_NextPart_000_0010_01C672E4.16296780
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0010_01C672E4.16296780
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0010_01C672E4.16296780--|||This is a multi-part message in MIME format.
--030303010405060404030702
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I'm guessing that your server is not listening on any named pipes. You
can change the network protocols in the SQL Server 2005 Surface Area
Configuration tool (in Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools) or in the "SQL Server 2005 Network Configuration"
section of the SQL Server Configuration Manager tool (also in Start |
Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named Pipes
in the "SQL Native Client Configuration" section of the SQL Server
Configuration Manager on the client machine (ie. protocol priority) or
by specifying the TCP protocol in the client connection when connecting
to the SQL instance (either in an alias or by explicitly specifying
"tcp:servername,portnum" for the server name in the connection strings)).
--
*mike hodgson*
http://sqlnerd.blogspot.com
retf wrote:
> yes
> no, how I do this?
> I dont know
> yes
> yes
> Thanks to all...
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
> Can you ping the box?
> Have you tried a different protocol, like TCP for instance?
> Is your server even listening on named pipes?
> Are you on the same subnet as the server?
> Can you establish a client connection from the server itself?
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>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: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--030303010405060404030702
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I'm guessing that your server is not listening on any named pipes.
You can change the network protocols in the SQL Server 2005 Surface
Area Configuration tool (in Start | Programs | Microsoft SQL Server
2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--030303010405060404030702--|||This is a multi-part message in MIME format.
--=_NextPart_000_0008_01C6736D.DFE53D90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | =Configuration Tools) or in the "SQL Server 2005 Network Configuration" =section of the SQL Server Configuration Manager tool (also in Start | =Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than =1433, make sure named pipes is turned off and always use TCP to connect =to the SQL instance (either by moving the TCP protocol above Named Pipes =in the "SQL Native Client Configuration" section of the SQL Server =Configuration Manager on the client machine (ie. protocol priority) or =by specifying the TCP protocol in the client connection when connecting =to the SQL instance (either in an alias or by explicitly specifying ="tcp:servername,portnum" for the server name in the connection =strings)).
--
mike hodgson
http://sqlnerd.blogspot.com=20
retf wrote: yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0008_01C6736D.DFE53D90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi,
Thanks for help.
How I change the port 1433 to 1436 (ex)?
Thanks
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
=
--=_NextPart_000_0008_01C6736D.DFE53D90--|||This is a multi-part message in MIME format.
--=_NextPart_000_0015_01C6736E.0C39CFF0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Other thing , If I have firewall (basic firewam of windows 2003) I need =open this port, ane any else more?
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
I'm guessing that your server is not listening on any named pipes. =You can change the network protocols in the SQL Server 2005 Surface Area =Configuration tool (in Start | Programs | Microsoft SQL Server 2005 | =Configuration Tools) or in the "SQL Server 2005 Network Configuration" =section of the SQL Server Configuration Manager tool (also in Start | =Programs | Microsoft SQL Server 2005 | Configuration Tools).
Personally, I would turn on TCP, set the port to something other than =1433, make sure named pipes is turned off and always use TCP to connect =to the SQL instance (either by moving the TCP protocol above Named Pipes =in the "SQL Native Client Configuration" section of the SQL Server =Configuration Manager on the client machine (ie. protocol priority) or =by specifying the TCP protocol in the client connection when connecting =to the SQL instance (either in an alias or by explicitly specifying ="tcp:servername,portnum" for the server name in the connection =strings)).
--
mike hodgson
http://sqlnerd.blogspot.com=20
retf wrote: yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson" <e1minst3r@.gmail.com> escreveu na mensagem =news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
Can you ping the box?
Have you tried a different protocol, like TCP for instance?
Is your server even listening on named pipes?
Are you on the same subnet as the server?
Can you establish a client connection from the server itself?
--
mike hodgson
http://sqlnerd.blogspot.com=20
Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DM=
SSQLServer&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
--=_NextPart_000_0015_01C6736E.0C39CFF0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Other thing , If I have firewall (basic =firewam of windows 2003) I need open this port, ane any else =more?
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com retf wrote:
yes
no, how I do this?
I dont know
yes
yes
Thanks to all...
"Mike Hodgson"
--mike =hodgsonhttp://sqlnerd.blogspot.com Retf wrote: TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection =to SQL Server) (Microsoft SQL Server, Error: 233)
For help, click: http://go.micr=osoft.com/fwlink?ProdName=3DMicrosoft+SQL+Server&EvtSrc=3DMSSQLServer=&EvtID=3D233&LinkId=3D20476
--
BUTTONS:
OK
--
=
--=_NextPart_000_0015_01C6736E.0C39CFF0--|||This is a multi-part message in MIME format.
--020209000101090301080006
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Use the SQL Server Configuration Manager mentioned in my previous reply
(SQL Server 2005 Network Configuration section).
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
> Hi,
> Thanks for help.
> How I change the port 1433 to 1436 (ex)?
> Thanks
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>> yes
>> no, how I do this?
>> I dont know
>> yes
>> yes
>> Thanks to all...
>> "Mike Hodgson" <e1minst3r@.gmail.com
>> <mailto:e1minst3r@.gmail.com>> escreveu na mensagem
>> news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
>> Can you ping the box?
>> Have you tried a different protocol, like TCP for instance?
>> Is your server even listening on named pipes?
>> Are you on the same subnet as the server?
>> Can you establish a client connection from the server itself?
>> --
>> *mike hodgson*
>> http://sqlnerd.blogspot.com
>>
>> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>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: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--020209000101090301080006
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Use the SQL Server Configuration Manager mentioned in my previous
reply (SQL Server 2005 Network Configuration section).</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="midO6VlMZ4cGHA.3712@.TK2MSFTNGP03.phx.gbl" type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<div><font face="Arial" size="2">Hi,</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks for help.</font></div>
<div> </div>
<div><font face="Arial" size="2">How I change the port <font
face="Courier New" size="3">1433 to 1436 (ex)?</font></font></div>
<div> </div>
<div><font face="Courier New">Thanks</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl">news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl</a>...</div>
<tt>I'm guessing that your server is not listening on any named
pipes. You can change the network protocols in the SQL Server 2005
Surface Area Configuration tool (in Start | Programs | Microsoft SQL
Server 2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl"
type="cite">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--020209000101090301080006--|||This is a multi-part message in MIME format.
--060104020209090202010800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
That's the only incoming port you'll need to open (assuming you don't
need the SQL Server Browser service, which you shouldn't - you may as
well disable that browser service as you won't need it). SQL Server
opens an outgoing connection back to the client, I think, using a high
port but most firewalls allow all outgoing connections by default. And,
in fact, I think the Windows firewall only deals with incoming traffic
so I don't think there's even an option to mess around with outbound ports.
--
*mike hodgson*
http://sqlnerd.blogspot.com
Retf wrote:
> Other thing , If I have firewall (basic firewam of windows 2003) I
> need open this port, ane any else more?
>
> "Mike Hodgson" <e1minst3r@.gmail.com <mailto:e1minst3r@.gmail.com>>
> escreveu na mensagem news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl...
> I'm guessing that your server is not listening on any named
> pipes. You can change the network protocols in the SQL Server
> 2005 Surface Area Configuration tool (in Start | Programs |
> Microsoft SQL Server 2005 | Configuration Tools) or in the "SQL
> Server 2005 Network Configuration" section of the SQL Server
> Configuration Manager tool (also in Start | Programs | Microsoft
> SQL Server 2005 | Configuration Tools).
> Personally, I would turn on TCP, set the port to something other
> than 1433, make sure named pipes is turned off and always use TCP
> to connect to the SQL instance (either by moving the TCP protocol
> above Named Pipes in the "SQL Native Client Configuration" section
> of the SQL Server Configuration Manager on the client machine (ie.
> protocol priority) or by specifying the TCP protocol in the client
> connection when connecting to the SQL instance (either in an alias
> or by explicitly specifying "tcp:servername,portnum" for the
> server name in the connection strings)).
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> retf wrote:
>> yes
>> no, how I do this?
>> I dont know
>> yes
>> yes
>> Thanks to all...
>> "Mike Hodgson" <e1minst3r@.gmail.com
>> <mailto:e1minst3r@.gmail.com>> escreveu na mensagem
>> news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl...
>> Can you ping the box?
>> Have you tried a different protocol, like TCP for instance?
>> Is your server even listening on named pipes?
>> Are you on the same subnet as the server?
>> Can you establish a client connection from the server itself?
>> --
>> *mike hodgson*
>> http://sqlnerd.blogspot.com
>>
>> Retf wrote:
>>TITLE: Connect to Database Engine
>>--
>>Cannot connect to VEGAS-W-DV-02.
>>--
>>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: Named Pipes Provider, error: 40 - Could not open a connection to
>>SQL Server) (Microsoft SQL Server, Error: 233)
>>For help, click:
>>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
>>--
>>BUTTONS:
>>OK
>>--
>>
>>
--060104020209090202010800
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>That's the only incoming port you'll need to open (assuming you
don't need the SQL Server Browser service, which you shouldn't - you
may as well disable that browser service as you won't need it). SQL
Server opens an outgoing connection back to the client, I think, using
a high port but most firewalls allow all outgoing connections by
default. And, in fact, I think the Windows firewall only deals with
incoming traffic so I don't think there's even an option to mess around
with outbound ports.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mid%23Fc74Z4cGHA.2456@.TK2MSFTNGP04.phx.gbl"
type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<div><font face="Arial" size="2">Other thing , If I have firewall
(basic firewam of windows 2003) I need open this port, ane any else
more?</font></div>
<div> </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl">news:u86$LbwcGHA.4932@.TK2MSFTNGP03.phx.gbl</a>...</div>
<tt>I'm guessing that your server is not listening on any named
pipes. You can change the network protocols in the SQL Server 2005
Surface Area Configuration tool (in Start | Programs | Microsoft SQL
Server 2005 | Configuration Tools) or in the "SQL Server 2005 Network
Configuration" section of the SQL Server Configuration Manager tool
(also in </tt><tt>Start | Programs | Microsoft SQL Server 2005 |
Configuration Tools</tt><tt>).<br>
<br>
Personally, I would turn on TCP, set the port to something other than
1433, make sure named pipes is turned off and always use TCP to connect
to the SQL instance (either by moving the TCP protocol above Named
Pipes in the "SQL Native Client Configuration" section of the SQL
Server Configuration Manager on the client machine (ie. protocol
priority) or by specifying the TCP protocol in the client connection
when connecting to the SQL instance (either in an alias or by
explicitly specifying "tcp:servername,portnum" for the server name in
the connection strings)).<br>
</tt>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
retf wrote:
<blockquote cite="mide2u6CyvcGHA.4108@.TK2MSFTNGP03.phx.gbl"
type="cite">
<meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">no, how I do this?</font></div>
<div><font face="Arial" size="2">I dont know</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div><font face="Arial" size="2">yes</font></div>
<div> </div>
<div><font face="Arial" size="2">Thanks to all...</font></div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div>"Mike Hodgson" <<a href="http://links.10026.com/?link=mailto:e1minst3r@.gmail.com">e1minst3r@.gmail.com</a>>
escreveu na mensagem <a
href="http://links.10026.com/?link=news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl">news:%23OJa$NvcGHA.3908@.TK2MSFTNGP04.phx.gbl</a>...</div>
<tt>Can you ping the box?<br>
Have you tried a different protocol, like TCP for instance?<br>
Is your server even listening on named pipes?<br>
Are you on the same subnet as the server?<br>
Can you establish a client connection from the server itself?</tt><br>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Retf wrote:
<blockquote cite="mideDkSG6tcGHA.3344@.TK2MSFTNGP03.phx.gbl"
type="cite">
<pre wrap="">TITLE: Connect to Database Engine
--
Cannot connect to VEGAS-W-DV-02.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 233)
For help, click:
<a class="moz-txt-link-freetext"
href="http://links.10026.com/?link=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476">http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a>
--
BUTTONS:
OK
--
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--060104020209090202010800--|||Hi,
You may also want to check on client machine to make sure both TCPIP and
named pipes are enabled via client network utility or configuration
manager. Port configuration is only valid for TCPIP protocol. Named pipies
is usually based on netbios connection via port 135/138/139 etc.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment