Error connecting to SQL Server 2005 - ... does not allow remote connections?

I have an ASP.NET 2.0 Website that in the connection string does not connect
to the local SQL Server but tries to connect to another SQL Server 2005
Server in another State. When I run the application from Visual Studio 2005
it connects just fine. When I published the website to the Live Server I
receive the below 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.
Any ideas?
Peace in Christ
Marco Napoli
http://www.ourlovingmother.orgCheck this url for troubleshooting:
http://blogs.msdn.com/sql_protocols.../22/506607.aspx
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Marco Napoli" <marco@.avantitecnospam.com> wrote in message
news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> I have an ASP.NET 2.0 Website that in the connection string does not
connect
> to the local SQL Server but tries to connect to another SQL Server 2005
> Server in another State. When I run the application from Visual Studio
2005
> it connects just fine. When I published the website to the Live Server I
> receive the below 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.
> Any ideas?
> --
> Peace in Christ
> Marco Napoli
> http://www.ourlovingmother.org
>
>|||Thank you.
Marco
"Jack Vamvas" <delete_this_bit_jack@.ciquery.com_delete> wrote in message
news:euqdnWInVNe2O8zZRVnyjg@.bt.com...
> Check this url for troubleshooting:
> http://blogs.msdn.com/sql_protocols.../22/506607.aspx
> --
> Jack Vamvas
> ___________________________________
> Receive free SQL tips - www.ciquery.com/sqlserver.htm
> ___________________________________
>
> "Marco Napoli" <marco@.avantitecnospam.com> wrote in message
> news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> connect
> 2005
>

Error connecting to remote connections...

That's what appears at my client site. I have virtually the exact same
configuration on a handful of servers using the SQL Reporting Services and
the RDLC which is working great. Except this one server has:
"An error has occurred when establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by teh fact that
under the default settings SQL Server does not allow remote connections.
Named Pipes provider, error: 40 - Could not open a connection to the SQL
Server).
I think the IT admin used SQL permissions when he installed. Could that be
the problem?
Thanks in Advance.
ChrisThis link might help,
http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
daw
"Chris Marsh" wrote:
> That's what appears at my client site. I have virtually the exact same
> configuration on a handful of servers using the SQL Reporting Services and
> the RDLC which is working great. Except this one server has:
> "An error has occurred when establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by teh fact that
> under the default settings SQL Server does not allow remote connections.
> Named Pipes provider, error: 40 - Could not open a connection to the SQL
> Server).
> I think the IT admin used SQL permissions when he installed. Could that be
> the problem?
> Thanks in Advance.
> Chris
>
>|||Sorry, I should have specified this earlier but the SQL DB is SQL 2000 not
2005 which is what is strange. Again, works on multiple other configurations
but not this one.
"daw" <daw@.discussions.microsoft.com> wrote in message
news:D05FF90C-2A0D-43B9-83B4-D348859995E9@.microsoft.com...
> This link might help,
> http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
> daw
> "Chris Marsh" wrote:
>> That's what appears at my client site. I have virtually the exact same
>> configuration on a handful of servers using the SQL Reporting Services
>> and
>> the RDLC which is working great. Except this one server has:
>> "An error has occurred when establishing a connection to the server. When
>> connecting to SQL Server 2005, this failure may be caused by teh fact
>> that
>> under the default settings SQL Server does not allow remote connections.
>> Named Pipes provider, error: 40 - Could not open a connection to the SQL
>> Server).
>> I think the IT admin used SQL permissions when he installed. Could that
>> be
>> the problem?
>> Thanks in Advance.
>> Chris
>>