Hi Guys...  I have a new SQL 2005 box, and a new IIS 6.0 site pointing to a directory with the Install files for 4.5.5 unzipped.  I have configured the folder w/permissions for the NETWORK SERVICE user, and have altered web.config connection strings.  I've doublechecked, and it does seem that my server, database, uid, and pwd are correct.  I have the server name as the named instance on my sql server, the database as the blank db i created today, the user and pwd correct.  However, I'm still getting this:

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: 2
Message: 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)

All computers are on a local Intranet and are on the same domain.  Any ideas where to start on this one?

Oh, by the way, I can get through the file permissions check screen of the install wizard.  I cannot get past the Test Database Connection page.  That's where I get this error.  The application event viewer on the web server produces the exact same message.

Ian,

Thanks for the help... I'm so new that I have problems with even the most basic terminology.  When I log into management studio on the SQL 2005 box, I just click <CONNECT> on the window that pops up when I load the program.  It says 

Server type: Database Engine; 
Server Name: CDCSQL_DEV\SQLDEV1; 
Authentication: Windows Authentication. 

I click <CONNECT> button and I'm in like Flynn.  So, all that to say, I'm not even sure how to "manually log in."  I figured that's what I was doing.  But again, I'm waaayyy new to this whole SQL thing, and to .NET.

In my connection string, I figured I would use the CDCSQL_DEV as the name of the server.  Should I use the whole thing CDCSQL_DEV\SQLDEV1 for the server name, or just the instance name maybe?