SQL 2000 Question

Here is my current setup:

Windows 2008 Enterprise (HOST)
Windows 2003 Standard w/SQL 2000 (VIRTUAL MACHINE)
I'm using VMWARE Server for Virtualization

Here's my problem:

I have a SQL database setup on the 2003 virtual server. I'm using boreland BDE on client machines to connect to a custom written application to connect to the SQL database. When I setup the cutom application on client machines, they can't see the SQL server BUT if I install it on the 2003 server the application works fine connecting to the SQL server.

My question is, is there some kind of speical setting on VMWARE or SQL 2000 or maybe the HOST (2008 box) keeping my clients from connecting to the SQL database? I can ping the 2003 server but for some reason they can't recognize it having SQL on it.
LVL 15
wantabe2Asked:
Who is Participating?
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.

za_mkhIT ManagerCommented:
You need to look at your networking configuration. From your VM, can you ping your client PC? Since you can ping the server from your clients, I assume the networking from the VMWare Server side is correct.
But you need to check your firewall settings on your Windows 2003 VM running SQL ... The Firewall could be activated, or the AV (if u have loaded any) in the VM could have it's own firewall hence things not working. Also assume you have configured the SQL Server to allow network connections.
Default SQL Express / MSDE installations don't allow network access unless you configure it to do so.
0
davismisbehavisCommented:
You say that you can ping the windows 2003 VM from outside the Windows 2008 host, i.e. client machines.

What happens when you use Enterprise Manager from a client machine to connect to the SQL Server,  can you see it?

Could it be that the SQL Server has not been configured to allow named pipes?  check out the following which may help http://support.microsoft.com/kb/265808 
0

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
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
VMware

From novice to tech pro — start learning today.