Bobby ` wrote:
One other thing, I can ping from the VM to the PC. The networking in the VM
is set to NAT.
Thanks,
Bobby
-----Original Message-----
From: Bobby Heid [mailto:[EMAIL PROTECTED]
Sent: Monday, March 05, 2007 4:30 PM
To: 'Jamie Furtner'
Subject: RE: [H] SQL Server 2005, IIS, and VPC 2007.
Jamie,
I can not ping the VM. It times out. I can see it in Network Neighborhood.
I turned off both firewalls to see if it was being blocked. What do I do
next?
Thanks,
Bobby
-----Original Message-----
From: Jamie Furtner [mailto:[EMAIL PROTECTED]
Sent: Monday, March 05, 2007 12:58 PM
To: [EMAIL PROTECTED]; The Hardware List
Subject: Re: [H] SQL Server 2005, IIS, and VPC 2007.
Bobby Heid wrote:
Hey,
I have SQL Server 2005 standard installed on my pc. What I want to do
is to install SQL 2005 standard on XP Pro inside of a Virtual PC 2007
VM. And I have done that.
What I have not been able to do is access the SQL Server from my PC
when the VM is running. I have turned on named pipes, TCP/IP, and one
other one (can't remember at the moment what it is). I have also
installed IIS onto the VM also and was not able to access a Web
Service from my machine.
What else do I need to do to allow my machine to see SQL Server and
IIS in the VM?
Thanks,
Bobby
Is the Windows Firewall turned on? If so, it'll block remote access. Try
pinging the remote machine, and if that works telnet to port 1433 - you
should get gibberish back, but that'll confirm that the connection works.
If the two machines are not a member of the same domain, you'll also
have to use SQL authentication - you won't be able to use Windows
authentication as that expects both machines to be in the same domain.
This is something you can change through the server properties dialog
(right click on the server node in SQL Management studio, properties,
Security tab, change the server authentication type).
Jamie
I think the way that Virtual PC virtualizes the NAT adapter screws up
connectivity from the host to the guest - guest to host works fine. I've
worked around this before by setting up a Loopback adapter, bridging the
VM to the loopback interface, and configuring ICS on the host (or
manually configuring IP addresses of host and guest). Take a look at
http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx for
details on how to do this, beginning to end.
The other way to deal with this (assuming you can) is to bridge the VM
to the physical adapter, so it appears on your network. If you do that
then the issue goes away, but it does require that you can actually
connect to a network, and it does expose the virtual machine to the
outside world.
Jamie
