Re: Connection Error

Hi
Most likely the port 1433 is blocked on this SQL Server by Windows Firewall.
So try open TCP port 1433 on the SQL Server machine you cannot telnet to.





"Sherwood" <Sherwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F33D985-1D1F-4140-BDF6-C6E8A1D71E3F@xxxxxxxxxxxxxxxx
Greetings,

I have a newbie question. I just installed SQL Server 2005 (Express
edition) and created a new user "Sherwood" (with an appropriate password).
When I attempt to connect using SQL Server Authentication, however, I
receive
the following error:

"Cannot connect to HOME-PC\SQLEXPRESS.
Additional Information: A connection was successfully established with
the
server, but then an error occurred during the login process. (provider:
Shared Memory Provider, error: 0 - No process is on the other end of the
pipe.) (Microsoft SQL Server, Error: 233)"

Any suggestions?

Thanks in advance!


.

Relevant Pages

  • Connection Error
    ... edition) and created a new user "Sherwood". ... When I attempt to connect using SQL Server Authentication, however, I receive ... but then an error occurred during the login process. ... Shared Memory Provider, error: 0 - No process is on the other end of the ...
    (microsoft.public.sqlserver.security)
  • Re: putting a sql server behind a firewall
    ... that I got it was that sql server was publicly accessable... ... > Server - only IIS is, and it's running on the same physical machine. ... installation of a firewall - software or hardware - will have zero ... You will need to open TCP port 80 for incoming traffic. ...
    (microsoft.public.sqlserver.security)
  • Re: Manage SQL server accross WAN??
    ... I have to move a SQL server into a secure DMZ and ... If I open TCP port 1433 ... > and UDP 1434 will this allow SQL management using Enterprise Manager ... I do think you only need TCP 1433 to work with SQL Server, ...
    (microsoft.public.sqlserver.security)
  • RE: Shared Memory Provider error
    ... "Connection was successfully established with the server, ... (provider: Shared Memory Provider, ... Server 2005 Express Edition and SQL Server 2005 Developer Edition do not ... However, if this issue still persists, let's try LPC for shared memory ...
    (microsoft.public.sqlserver.connect)
  • Re: ASP.NET v2.0 login control issue with SQL Server 2000
    ... I have tested the controls using SQL Express and ... > have now decided to try using a central SQL Server 2000 database. ... > roles and the entrys are present in the SQL Server 2000 database. ... > said why am I having issues with the login process? ...
    (microsoft.public.dotnet.framework.aspnet.security)