SQL Server does not exist or access denied

I am stumped on this problem. I cannot get my application to connect to the local SQL Server.  

The application was written in VB6 and I am using mixed mode. I also have the MS firewall turned off. I am using the ADO and it works fine on my old developer computer but not the new one. I cannot even connect to the SQL Server on my old developer computer from the new computer. It is got to be something on the new computer, maybe I forget to install something. EM and ODBC connects to the SQL Server just fine on the new computer using the mixed mode.

What am I missing?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Post your connetion string here
Sorry, I know it sounds like an 'Is it plugged in' question, but I always like to check the basics first.
lunchbyteAuthor Commented:
Driver={SQL Server};Server=Dianelapm90,1433;Database=nkdata;Uid=nk_user;Pwd=XXXX;

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Version of MDAC?
Any other software (such as Zone Alarm)?
Can you ping the other server?
lunchbyteAuthor Commented:
Driver={SQL Server};Server=,1433;Database=nkdata;Uid=nk_user;Pwd=XXXX;

did not work as well
lunchbyteAuthor Commented:
I mean did not work as well.
lunchbyteAuthor Commented:
how do you ping a port? I can ping the localhost and the other computer just fine.
SQL Server version?
lunchbyteAuthor Commented:
can you telnet onto the port?
telnet Dianelapm90 1433
lunchbyteAuthor Commented:
it says could not open connection to the host, on port 1433. connect failed.
Sorry - had to step away. If that is the case, SQL Server is not running on port 1433 - check that you have enabled TCP on the server and that named pipes is enabled (right click in EM, properties, Network Configuration).

To confirm whether it is actually access denied, you could run a SQL Profiler trace and view the attempted connections. If you see traffic in the trace in profiler, then you know that at least the connection is getting to SQL Server and then being rejected.
lunchbyteAuthor Commented:
Both TCP and named pipes are enabled. Nothing shows up on profile when I try to connect using the VB6 application. The port is set to 1433.
So it's being blocked before it connects to SQL, or can't find the server. Are you sure of the SQL instance name? Definitely Dianelapm90and not Dianelapm90\INSTANCENAME
lunchbyteAuthor Commented:
OK, I got it to work by doing this.

Driver={SQL Server};Server=DIANELAPM90;Database=nkdata;Uid=nk_user;Pwd=XXXX;

,1433 was removed from the connection string. Any idea why? I got the firewall turned off.
Is your SQL Server installed with a binary or case sensitive collation setting?
lunchbyteAuthor Commented:
I am not aware of that but under General tab I see "SQL_Latin1_General_CPS_CI_AS" for Server collation:

Dany BalianCTOCommented:
first of all, are you sure that u installed sql server as a default instance?? or a new instance?

if it's the default instance, and still u cannot connect to it, then this reminds me of a problem that occured once on my windows xp professional sp2 machine...
i searched everywhere for a solution, and found nothing..

i dont know if this is an option in your case...
but i uninstalled sql server and reinstalled it, and everything worked perfectly...

p.s. the computer is able to connect to a remove sql server successfully but not to the local... and reinstalling (repairing) sql server did not solve the problem!!

hope this helps,


The collation is general, not case sensitive. Perhaps you are not actually running on TCP, or perhaps it is being blocked. Most likely, removing the 1433 allowed it to connect on Named Pipes.

Suggest you check the SQL Server logs to see if there were any errors trying to listen on that port. You could also run TCP View from www.sysinternals.com to see what is running on which port on the PC.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lunchbyteAuthor Commented:
Using TCP View, 1433 is not on the list.
lunchbyteAuthor Commented:
mrdany - I am using the default instance. I will try to uninstall and reinstall as last resort.
If 1433 is not in the list, then SQL Server is not actually listening on that port. Restart SQL Server, and then look at the SQL Server logs (from EM) - you will see the TCP Port it is listening on (or trying to, and any error) in there after startup.
lunchbyteAuthor Commented:
Fixed. I installed SP3 for SQL Server and rebooted the computer and now I can connect.
jkaiosIT DirectorCommented:
By the way, the latest version of SQL 2000 is SP4 and can be downloaded from Microsoft.com
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.