This should work, so check some of the unlikely problems.
- Did you restart the SQLExpress instance after enabling listening on TCP?
That's required.
- Is "OtherComputer\SQLEXPRESS" by any chance installed as another name?
SQLEXPRESS is the default name, but you can name it
"OtherComputer\ACCOUNTING" during installation if you want to.
- Is "OtherComputer\SQLEXPRESS" started? (I know this is a duh... but
sometimes people don't check and that would cause this error.)
- Is the client using TCP? Using the SQL Server Configuration Manager on the
client, make sure TCP is enabled, and move TCP ahead of Named Pipes.
- Can you connect to the other computer by IPAddress,port number, like
123.45.67.245,1433 ? SQL Express listens on a dynamic port by default, so to
get the port number that was dynamically selected, check the error log for a
statement similar to "Server is listening on [ 'any' <ipv4> 1433]"
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "Ralf Kaiser" <rk@lingosmart.de> wrote in message
news:eHivoVnsHHA.4572@TK2MSFTNGP02.phx.gbl...
> "Razvan Socol" <rsocol@gmail.com> schrieb im Newsbeitrag
> news:1182254690.307487.199810@p77g2000hsh.googlegroups.com...
>> Hello, Ralf
>>
>> I guess the firewall at the server is blocking the connections.
>> You need to configure an exception for sqlservr.exe and for
>> sqlbrowser.exe.
>>
>
> No. These both applications are defined in the firewall (both are XP
> computers). Forgot that to mention in my original post. Sorry.
>
"Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> schrieb im
Newsbeitrag news:524508F1-B169-42B0-9C11-7C81033087CF@microsoft.com...
Hello Rick,
[quoted text, click to view] > - Did you restart the SQLExpress instance after enabling listening on TCP?
> That's required.
I have restarted both computers after activating TCP (first only restarted
the services and because that did not work restarted the computers)
[quoted text, click to view] > - Is "OtherComputer\SQLEXPRESS" by any chance installed as another name?
> SQLEXPRESS is the default name, but you can name it
> "OtherComputer\ACCOUNTING" during installation if you want to.
No. The name is correct on "OtherComputer" i connect locally with this name.
[quoted text, click to view] > - Is "OtherComputer\SQLEXPRESS" started? (I know this is a duh... but
> sometimes people don't check and that would cause this error.)
On "OtherComputer" all SQL relevant services are up and running
[quoted text, click to view] > - Is the client using TCP? Using the SQL Server Configuration Manager on
> the client, make sure TCP is enabled, and move TCP ahead of Named Pipes.
Yes. It uses TCP
[quoted text, click to view] > - Can you connect to the other computer by IPAddress,port number, like
> 123.45.67.245,1433 ? SQL Express listens on a dynamic port by default, so
> to get the port number that was dynamically selected, check the error log
> for a statement similar to "Server is listening on [ 'any' <ipv4> 1433]"
That is the only thing i have not tried yet. Currently i have only tried to
connect using the computer names. Will try that today to see if it helps.
Thanks,
Ralf