Cannot connect SQL 2005 with OLE DB Provider for SQL Server

Cannot connect SQL 2005 with OLE DB Provider for SQL Server

MSSQL 2000 Utilities & MSDE was uninstalled.
After installation SQL 2005 Standard Full all connections was OK (tested).
Aftert restarting the computer I cannot connect to MSSQL with OLE DB Provider for SQL Server.
I try to connect from Delphi 5 SP2 (ADOConnection) and from MS Access 2003 SP2.

Error "SQL Server denied or does not exists or access denied"

Versions:
Windows Xp Pro SP 2
ADO/MDAC: 2.81.1117.0 (xpsp_sp2_rtm.040803-2158)
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Connection sting:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=pwd;Data Source=GMSAlexHome;Initial Catalog=GMSSample;Application Name="GMS Office Tools Service Pack"

Question: how to connect to SQL 2005 with SQL DB Provider.
All old applications does not work.

On local machine when ServerName = 'localhost' or '.' - all OK.
When using SQL server name - error.
Before rebooting all was OK.

Thanks in advance.

If you try to connect from the local PC and it works fine, but does not work from the network then most likely SQL Server is not enabled to accept external network requests. Also if your server name contains instance name, then it also suppose to be specified in your connection string, like servername\instancename|||

On local computer connection avaible only as <localhost> and <.>.

There is no instance name and other sql servers.

SQLSRV Works more than 3 times slower than MSDE 2000 on small test DB (about 100 mb).

VERY many bugs in tools and very slow.... $(((

What comps in MS? I have P4 3MHz 1 Gb SATA - VERY slow.

Sory for digression.

|||

Do you compare performance based on exact same data and structure? If your indexes are not the same as in MSDE 2000 then you cannot compare performance.

About bugs. If you have any, you could report them here. If you do this and they really exist, I believe, it will help to improve product

|||

As Val mentioned, please double check using "SQL Server Configuration Manager" tool that your SQL instance has remote TCP and/or Named Pipe support enabled.

Also, please make sure that the Windows Firewall is not blocking the ports used by SQL Server. You can explicitly add TCP port 1433 to the exception list or you can add Sqlservr.exe program to the exception list (to ensure both TCP and Named Pipes are not blocked).

Jimmy Wu