Connecting to SQL 2005

I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
connect to the server within the same box. When I try to connect to the 2005
SQL server from an other desktop using SQL Server Management studio, I get a
timeout error. Can you please help me to fix this.
This is waht I get when I connect to the SQL server from another computer...
===================================
Cannot connect to CWXPTDVZPT62.
===================================
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
Server Name: CWXPTDVZPT62
Error Number: -2
Severity: 11
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
stateObj, UInt32 error, Boolean freePacket)
at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
enlistOK)
at
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
connectionOptions, Object providerInfo, String newPassword, SqlConnection
owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
Hi Mahesh,
Starting with the June CTP version, remote access to an instance of SQL
Server 2005 is off by default. You can enable remote access by using the
Surface Area Configuration (SAC) tool.
On the local server:
1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
Configuration Tools | SQL Server Surface Area Configuration
2. From the SAC tool, select Surface Area Configuration for Services and
Connections
3. Under Database Engine, select Remote Connections and then select the
Local and Remote Connections and one of the options under that.
4. Click Apply.
5. You'll need to stop and start the MSSQLSERVER service. You can do that
from the SAC as well. Just click Service under Database Engine and
stop/start the service.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>I have insatlled SQL 2005 June CTP on a Windows XP Machine and I am able to
> connect to the server within the same box. When I try to connect to the
> 2005
> SQL server from an other desktop using SQL Server Management studio, I get
> a
> timeout error. Can you please help me to fix this.
> This is waht I get when I connect to the SQL server from another
> computer...
> ===================================
> Cannot connect to CWXPTDVZPT62.
> ===================================
> Timeout expired. The timeout period elapsed prior to completion of the
> operation or the server is not responding. (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
> --
> Server Name: CWXPTDVZPT62
> Error Number: -2
> Severity: 11
> State: 0
>
> --
> Program Location:
> at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
> stateObj)
> at
> System.Data.SqlClient.TdsParserStateObject.ReadSni Error(TdsParserStateObject
> stateObj, UInt32 error, Boolean freePacket)
> at System.Data.SqlClient.TdsParserStateObject.ReadSni (DbAsyncResult
> asyncResult, TdsParserStateObject stateObj)
> at System.Data.SqlClient.TdsParserStateObject.ReadPac ket(Int32
> bytesExpected)
> at System.Data.SqlClient.TdsParserStateObject.ReadBuf fer()
> at System.Data.SqlClient.TdsParserStateObject.ReadByt e()
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlInternalConnectionTds.Com pleteLogin(Boolean
> enlistOK)
> at
> System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(SqlConnection
> owningObject, SqlConnectionString connectionOptions, String newPassword,
> Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlInternalConnectionTds..ct or(SqlConnectionString
> connectionOptions, Object providerInfo, String newPassword, SqlConnection
> owningObject, Boolean redirectedUserInstance)
> at
> System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions
> options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection
> owningConnection, DbConnectionPoolGroup poolGroup)
> at
> System.Data.ProviderBase.DbConnectionFactory.GetCo nnection(DbConnection
> owningConnection)
> at
> System.Data.ProviderBase.DbConnectionClosed.OpenCo nnection(DbConnection
> outerConnection, DbConnectionFactory connectionFactory)
> at System.Data.SqlClient.SqlConnection.Open()
> at
> Microsoft.SqlServer.Management.UI.VSIntegration.Ob jectExplorer.ObjectExplorer.ValidateConnection(UIC onnectionInfo
> ci, IServerType server)
> at
> Microsoft.SqlServer.Management.UI.ConnectionDlg.Co nnector.ConnectionThreadUser()
>
|||Gail
Thank you for the answer, I checked the Surface area configuration and set
the option to “Local and Remote connections” and select the option to “use
both TCP/IP and named Pipes”.
I tried again to register the 2005 SQL server from Management studio of
another computer. I was able to register/connect only when I selected the
option “Named Pipes” in Connect properties for Network Protocol. When Network
Protocol option was set to “default” I got Timeout errors.
Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
Native client, I was able to view the Databases, but when I tested the
connection I got a timeout error.
I can connect to the 2005 server using query analyzer or thro creating an
ODBC.
Please advice.
Thanks again for all your help
Mahesh
"Gail Erickson [MS]" wrote:

> Hi Mahesh,
> Starting with the June CTP version, remote access to an instance of SQL
> Server 2005 is off by default. You can enable remote access by using the
> Surface Area Configuration (SAC) tool.
> On the local server:
> 1. Point to Start | All Programs | Microsoft SQL Server 2005 CTP |
> Configuration Tools | SQL Server Surface Area Configuration
> 2. From the SAC tool, select Surface Area Configuration for Services and
> Connections
> 3. Under Database Engine, select Remote Connections and then select the
> Local and Remote Connections and one of the options under that.
> 4. Click Apply.
> 5. You'll need to stop and start the MSSQLSERVER service. You can do that
> from the SAC as well. Just click Service under Database Engine and
> stop/start the service.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> "Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
> news:1157ADD8-F678-429F-AB6F-AA22DB1977CD@.microsoft.com...
>
>
|||Hi Mahesh,
Your follow-up questions are a bit out of area of experience. Please post
your questions to the Setup and DTS newsgroups at this link:
http://communities.microsoft.com/new...=sqlserver2005
They should be able to give you some advice.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Mahesh" <Mahesh@.discussions.microsoft.com> wrote in message
news:8DC49354-F7FC-4979-94A9-3DB20CF6B71E@.microsoft.com...[vbcol=seagreen]
> Gail
> Thank you for the answer, I checked the Surface area configuration and set
> the option to "Local and Remote connections" and select the option to "use
> both TCP/IP and named Pipes".
> I tried again to register the 2005 SQL server from Management studio of
> another computer. I was able to register/connect only when I selected the
> option "Named Pipes" in Connect properties for Network Protocol. When
> Network
> Protocol option was set to "default" I got Timeout errors.
> Also, when I tried to connect to this 2005 SQL server thro SSIS using SQL
> Native client, I was able to view the Databases, but when I tested the
> connection I got a timeout error.
> I can connect to the 2005 server using query analyzer or thro creating an
> ODBC.
> Please advice.
> Thanks again for all your help
> Mahesh
> "Gail Erickson [MS]" wrote: