Hi

created a web app using the asp:Login component in machine A. SQL and VS2005
is also in machine A. I copied the entire project source to machine B and
modified
the machine B's web.config into

<connectionStrings>
<remove name="LocalSqlServer"/>
<add name="SQLConn" connectionString="data source=machineA;Initial
Catalog=automobile;User ID=sa;Password=secret"
providerName="System.Data.SqlClient"/>
</connectionStrings>

after runnning the project at machine B and logging in, i get this sql error:


[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]

any ideas??

"ChiWhiteSox" <(E-Mail Removed)> wrote in message
news:C69C012F-38EB-4F0C-9824-(E-Mail Removed)...
> Hi
>
> created a web app using the asp:Login component in machine A. SQL and
> VS2005
> is also in machine A. I copied the entire project source to machine B and
> modified
> the machine B's web.config into
>
> <connectionStrings>
> <remove name="LocalSqlServer"/>
> <add name="SQLConn" connectionString="data source=machineA;Initial
> Catalog=automobile;User ID=sa;Password=secret"
> providerName="System.Data.SqlClient"/>
> </connectionStrings>
>
> after runnning the project at machine B and logging in, i get this sql
> error:
>
>
> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> Error Locating Server/Instance Specified)]
>
> any ideas??

Make sure you have allowed remote connections in the SQL Server Surface Area
Configuration Manager on Machine A (Start / (All) Programs / Microsoft SQL
Server 2005 / Configuration Tools / SQL Server Surface Area Confuguration),
and also that the SQL Server port (1433?) is open in Machine A's firewall.

I had to:
give the asp.net user read access to the database
when i had the problem on an Intranet site.




"Leon Mayne" <(E-Mail Removed)> wrote in message
news:E706A18D-CEEA-4C03-AAC9-(E-Mail Removed)...
> "ChiWhiteSox" <(E-Mail Removed)> wrote in message
> news:C69C012F-38EB-4F0C-9824-(E-Mail Removed)...
>> Hi
>>
>> created a web app using the asp:Login component in machine A. SQL and
>> VS2005
>> is also in machine A. I copied the entire project source to machine B and
>> modified
>> the machine B's web.config into
>>
>> <connectionStrings>
>> <remove name="LocalSqlServer"/>
>> <add name="SQLConn" connectionString="data source=machineA;Initial
>> Catalog=automobile;User ID=sa;Password=secret"
>> providerName="System.Data.SqlClient"/>
>> </connectionStrings>
>>
>> after runnning the project at machine B and logging in, i get this sql
>> error:
>>
>>
>> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
>> Error Locating Server/Instance Specified)]
>>
>> any ideas??
>
> Make sure you have allowed remote connections in the SQL Server Surface
> Area Configuration Manager on Machine A (Start / (All) Programs /
> Microsoft SQL Server 2005 / Configuration Tools / SQL Server Surface Area
> Confuguration), and also that the SQL Server port (1433?) is open in
> Machine A's firewall.

so is the user at machine B using the windows authen at sql machine A ?

am i suppose to create that login at mahine A? do i need ADS at machine A ?

thanks

"Marcin Wiszowaty" wrote:

> I had to:
> give the asp.net user read access to the database
> when i had the problem on an Intranet site.
>
>
>
>
> "Leon Mayne" <(E-Mail Removed)> wrote in message
> news:E706A18D-CEEA-4C03-AAC9-(E-Mail Removed)...
> > "ChiWhiteSox" <(E-Mail Removed)> wrote in message
> > news:C69C012F-38EB-4F0C-9824-(E-Mail Removed)...
> >> Hi
> >>
> >> created a web app using the asp:Login component in machine A. SQL and
> >> VS2005
> >> is also in machine A. I copied the entire project source to machine B and
> >> modified
> >> the machine B's web.config into
> >>
> >> <connectionStrings>
> >> <remove name="LocalSqlServer"/>
> >> <add name="SQLConn" connectionString="data source=machineA;Initial
> >> Catalog=automobile;User ID=sa;Password=secret"
> >> providerName="System.Data.SqlClient"/>
> >> </connectionStrings>
> >>
> >> after runnning the project at machine B and logging in, i get this sql
> >> error:
> >>
> >>
> >> [SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 -
> >> Error Locating Server/Instance Specified)]
> >>
> >> any ideas??
> >
> > Make sure you have allowed remote connections in the SQL Server Surface
> > Area Configuration Manager on Machine A (Start / (All) Programs /
> > Microsoft SQL Server 2005 / Configuration Tools / SQL Server Surface Area
> > Confuguration), and also that the SQL Server port (1433?) is open in
> > Machine A's firewall.
>
>
>

"ChiWhiteSox" <(E-Mail Removed)> wrote in message
news:C4FE99CD-A203-4C3F-8326-(E-Mail Removed)...
> so is the user at machine B using the windows authen at sql machine A ?
>
> am i suppose to create that login at mahine A? do i need ADS at machine A
> ?

No, because you arn't using Windows authentication, you are using SQL
authentication. From your connection string:
User ID=sa;Password=secret

If you instead used:
Integrated Security=SSPI
then you would have create an application pool on machine B for the asp.net
application, and switch its identity to a domain account and then grant this
domain account access in machine A's SQL Server instance.