Help-me with this error

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?Prod...33&LinkId=20476
BUTTONS:
OK
--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?Prod...33&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>|||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
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?Prod...33&LinkId=20476
BUTTONS:
OK
--|||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:
[vbcol=seagreen]
> 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:
>|||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.4
932@.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 Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 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 N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col 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> 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?Prod...33&LinkId=20476
BUTTONS:
OK
--|||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.4
932@.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 Configurati
on tool (in Start | Programs | Microsoft SQL Server 2005 | Configuration Too
ls) or in the "SQL Server 2005 Network Configuration" section of the SQL Ser
ver Configuration Manager tool (also in Start | Programs | Microsoft SQL Ser
ver 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 N
ative Client Configuration" section of the SQL Server Configuration Manager
on the client machine (ie. protocol priority) or by specifying the TCP proto
col 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> 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?Prod...33&LinkId=20476
BUTTONS:
OK
--|||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:
[vbcol=seagreen]
> 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:
>|||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:
[vbcol=seagreen]
> 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:
>|||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.