Cannot open a connection with SQL Server 2005 Developer Edition.

I have installed on one computer Sql Server 2005 Developer Edition (CTP Version) together with a Visual Studio 2005 Beta Edition (July Version) and after configuration some properties by example the Network access, I had a lot of errors from the SQL Server Management Studio received(The most of them are a Connection timeout error but others errors too).
In the same time I have made a test program to test the new SQL Server 2005 using DB Library or ATL OLE DB Consumer Templates.
The Both test programs are not running because I cannot open a connection on the SQL Server.
I've tried using the Windows Authentification and the SQL Server Authentification too. The both methods are not able to connect with the SQL Server.
The Programs are written in Visual C++ under the Visual Studio 2005.
I need help to my problems!
First why I cannot connect to the Sql Server. With DB Library example I was able to do it with a Beta Version from SQL Server 2005 but not any more with the CTP Version.
Why I cannot connect with the ATL OLE DB Consumer Templates ?
I want to hear some experiences from others developers with this CTP Version from SQL Server 2005.
It is really so buggy or it is not compatible with Window Server 2003 or it is because after installing the SQL Server 2005 I have made an update of the Visual Studio 2005 to be able to create Projects in Visual C++ and run some examples ?
The problem was that with the Visual Studio that it is coming with the SQL Server I was not able to create any Project under Visual C++ because I was receiving an error that the Template for the Visual C++ failed.
I need help !

For the detailed information about the Versions please read the next list:

Microsoft SQL Server Management Studio - Version 9.0.1187.
MDAC - Version 2000.086.1830.00(srv03_sp1_rtm.050324_1447)
Microsoft .Net Framework - Version 2.0.50712.6.
Microsoft Visual Studio 2005 - Version 8.0.50712.6(lab23df.050712-0600)

The Operating System it is an Windows Server 2003 Professional Version with SP1.
What are the specific errors you are seeing when you try to connect to SQL Server. Could you please post your sample code
SQL Server projects are only available in Visual Studio pro. SKU and above. What SKU of Visual Studio are you using. Are you able to get C# and VB.NET SQL Server projects working?

Thanks,
-Vineet.|||So first what you've asked:
The Visual Studio Version it is :
Team Edition for Software Architects. Version 8.0.50712.6(lab23df.050712-0600)
It is installed from MSDN Team Suite DVD Beta 2 Version.
The Windows it is Windows 2003 Server Enterprise Edition(first time I was wrong, it was no Profesional version) with SP1.
The c# or VB.Net projects are working just fine. Only the connection to Sql Server it is not working.
The Sample code I will send you in the project on your email address:vineetr@.microsoft.com. The project it is imported from Visual Studio 6.0 Samples and coverted to Visual Studio 2005. It is writed in unmanaged code in Visual c++. Please don't forget to copy the db library files that are included in the archive on C:\ or to change the path for include in the code.
In the Sample I am using two tables here it is the SQL code to create the tables:

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[TestTable]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

drop table [dbo].[TestTable]

GO

CREATE TABLE [dbo].[TestTable] (

[Id] uniqueidentifier ROWGUIDCOL NOT NULL ,

[Text1] [varchar] (10) COLLATE Latin1_General_CI_AS NOT NULL ,

[Text2] [char] (10) COLLATE Latin1_General_CI_AS NOT NULL ,

[Int1] [int] NOT NULL ,

[Float1] [float] NOT NULL ,

[Short1] [smallint] NOT NULL

) ON [PRIMARY]

GO

CREATE CLUSTERED INDEX [index_clustered] ON [dbo].[TestTable]([Id] DESC ) ON [PRIMARY]

GO

CREATE INDEX [index_mixt] ON [dbo].[TestTable]([Int1] DESC , [Short1] DESC ) ON [PRIMARY]

GO

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[TestTable2]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)

drop table [dbo].[TestTable2]

GO

CREATE TABLE [dbo].[TestTable2] (

[autoid] [int] IDENTITY (1, 1) NOT NULL ,

[value1] [int] NULL ,

[value2] [int] NULL

) ON [PRIMARY]

GO

ALTER TABLE [dbo].[TestTable2] WITH NOCHECK ADD

CONSTRAINT [PK_TestTable2] PRIMARY KEY CLUSTERED

(

[autoid]

) ON [PRIMARY]

GO

In the mean time I have made some more research trying to find where the problem it is located. In the Sql Server components or in the library components that I am using in my code example (DB Library and ATL OLE DB Comsumer Templates library) and I found the next problem:
In the Microsoft Management Studio I have made the next four steps:
1. Create the tables ruuning the upper script. After this you will find in the database two sample tables TestTable and TestTable2.
2.Run the Query : Select * from TestTable2. No result but no error too.
3.Run the Query :Insert into testTable2 values (1,1). No I get allready the timeout Error and the query it is making the insert in the Table (Unexpected behavior).
4.Run the Query again: Select * from TestTable2. To check and see if the insert it is made. Now we can see in the table one row with the just inserted result. I got an error and the query it it succesfully executed.
Please see the archive that I will send you in there you will find the print screens.

So my opinion it is that the problem it is in the SQL Server itself.
This Timeout error I got it in the Microsoft Management Studio when I try to update some properties from Databases, Updating properties from the Server itself or Scripting a table etc...

I my head it stays one modification that I have made in the timeout value for the connections in the SQL Server properties. I have seted the value to 6000 and after a while again to 0(no limit). And after this modification I've retarted the computer (all the SQL server services should read again the settings after restart).

This can be one reason. The second reason can be: I have made some modification for the protocolls to access the SQL Server from another remote computer. I have read that default it cannot be accesed remote.
Anyhow I have undone all the modification and still the SQL it not reacting normally (when I access the Sql Server locally- or just from the Microsoft Management Studio ).

So please read your email to get the sample code and the print screen with th errors. I f you need more print screen with other error please tell me.
I wait for your help.

Thanks,
Vasile.|||I want help.
Do you need more infos ?
Have you found something ?
Can somebody help ?
Maybe I should wait for the release version.