Things to check:
1. Make sure your database engine is configured to accept remote connections
Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
Click on Surface Area Configuration for Services and Connections
Select the instance that is having a problem > Database Engine > Remote Connections
Enable local and remote connections
Restart instance
2. Check the SQL Server service account
If you are not using a domain account as a service account (for example if you are using NETWORK SERVICE), you may want to switch this
first before proceeding.
3. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings in your ASweb P.NET application
Usually the format needed to specify the database server is machinename\instancename
Check your connection string as well.
Integrated Security=SSPI;Min Pool Size=5;Max Pool Size=60;Connect Timeout=30? providerName=System.Data.SqlClient/>
4.You may need to create an exception on the firewall for the SQL Server instance and port you are using
Start > Run > Firewall.cpl
Click on exceptions tab
Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Binn), and port (default is 1433)
Check your connection string as well.
5. If you are using a named SQL Server instance, make sure you are using that instance name in your connection strings.
6. Check SQLBrowser; check that it is running. You may also need to create an exception in your firewall for SQLBrowser.
7. Check that you have connectivity to the SQL Server. Note what you are using to connect: machine name, domain name or IP address? Use
this when checking connectivity. For example if you are using myserver
Start > Run > cmd
netstat -ano| findstr 1433
telnet myserver 1433
ping -a myserver