Vista - VPC and SQL Connectivity

I have created a windows 2003 server
as a Virtual (guest) Machine, using Virtual PC.
I have Windows XP as the host OS.
I have installed SQL Server 2000 on the
Win 2000 server. I have installed SQL Client utilities on the
host machine. I created a loopback adapter
on the host, and I am able to ping the guest
from the Host and the host from the guest.
Using the SQL client configuration utility, I have
added the guests ip and sql port address on the host.
I have windows firewall turned off on both guest and host machines.
But I am not able to query the SQL database on the guest from the host
I get a message that I am unable to connect to SQL Server.
Any suggestions on how to get SQL Query Analyser to "See"
the SQL installation on the guest.

Thanks in advance...Ed

"Ed" <abcde@xxxxxx> wrote in message
news:1CFA8446-2B63-47E9-92E3-D096938CACC9@xxxxxxBeing able to PING is not enough. Can you copy files in either (preferably
both) directions? Can you see shared drives on both? You really need to
have full networking going between the host and guest. The loopback
adapter may not be enough, or it may be wired incorrectly.

Is this a single machine, not on network? If it is on a network already,
then just establish normal networking between host and guest.

Is the SQL service actually running on the guest? Can you do queries on
the guest?

I tried creating shares on both host and guest.
I can copy from the host to the guest, but not from
the quest to the host. When copying from the host to the guest,
authentication is required. When copying from the guest to the
host, I try to authenticate, but it keeps disabling the account.
I have tried resetting the password a lot of times but it does not help.
Caps Lock and Num Lock are off when I type the password.

You ask "Is this a single machine, not on a network". Do you mean
the company LAN, or a virtual network between the host and guest?
This computer can be connected to the company LAN., But I do not want the
guest machine to be visible on the company LAN. So far it is not. I want the
host to "see" the guest. But I do not want other clients on the company
LAN to see the guest.

Thank in advance...Ed



--
Ed


"Bob Campbell" wrote:

"Ed" <abcde@xxxxxx> wrote in message
news:7A8F6DA9-FD2D-4EAF-9DC5-3006B72F178F@xxxxxxIf the host machine is on the company LAN, are you a Local Admin on the
machine? Are you allowed to create your own accounts?
Then you should use the Shared Networking (NAT) networking option for the
guest, connect the host to the LAN and forget the Loopback adapter. This
will make the guest invisible to the LAN, but visible to the host. The
guest will still be able see the LAN, however, and (for example) get
Internet access thru the LAN if your host machine has it. But as far as
the LAN is concerned, all network packets will coming from/going to the host
machine.

FWIW, I do this everyday. I have Server 2003 with SQL Server 2005 running
in VPC on this Vista box. I am not using the NAT networking however,
because I need other machines on the LAN to see the SQL Server.

What is the excat error message you are getting? Is the error being caused by an ip addres, named pipes, etc?

I tried just changing to Shared Networking (NAT), and now I can no longer ping
the quest. Should the guest's ip address change now? And if Yes to what?


Ed


"Bob Campbell" wrote:

Shared Networking (NAT) does not support guest to host networking. It
does give the guest access to the physical network.

The IP address of the guest should change. Shared networking is very
similar to ICS and the guest should get its network config from a DHCP-style
allocator in the host (if it is set to get an IP automatically).

"Ed" <abcde@xxxxxx> wrote in message
news:34BEED52-4CE1-4371-9430-3C696A84D0E6@xxxxxx