[also posted in microsoft.public.sqlserver.setup newsgroup]
I need some more help.

I have uninstalled & reinstalled SQL Server 2005 5 times now and keep
getting stuck at the same point.  During setup I use a Domain User account
for SQL; I choose (this last time) Mixed Mode on authentication and set a
long sa password; I installed the database engine, integration, and the
online books, etc. selection; I do not install a default instance, but DO
install a named instance.

It completes the installation with no errors, same with the configuration
wizards.  I then open up SQL Server Management Studio and attempt to connect
to the datbase engine -- it fails every time.  I've tried Windows
Authentication (which has the Domain Admin's name greyed out - I logged on
with this account to install SQL), and SQL Authentication -- trying the sa
account and the Domain User account I installed SQL under.  All no good.  I
can connect to integration services and the online books, etc (can't
remember the name) just fine.  The error I get is:

===================================

Cannot connect to WCT-SHAREPOINT.

===================================

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) (.Net SqlClient Data Provider)

------------------------------
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&
EvtID=2&LinkId=20476

------------------------------
Error Number: 2
Severity: 20
State: 0

------------------------------
Program Location:

  at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
  at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
  at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo,
SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64
timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean
integratedSecurity, SqlConnection owningObject)
  at
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64
timerExpire, SqlConnection owningObject)
  at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String
host, String newPassword, Boolean redirectedUserInstance, SqlConnection
owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
  at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
  at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
  at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
  at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
owningConnection, DbConnectionPoolGroup poolGroup)
  at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
  at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
  at System.Data.SqlClient.SqlConnection.Open()
  at
Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
ci, IServerType server)
  at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

I've verified that the SQL Server 2005 service is started, and then restart
it for good measure.  Makes no difference.  I've also rebooted, no change.

What did I do wrong?