Any MS VirtualPC experts out there?
Discussion
OK, the scenario is as follows:
Laptop running XP. Part of a domain.
Virtual PC running Win 2003 Server hosted on the laptop.
VPC running IIS and SQL Server 2005.
The default network settings are all fine and dandy as long as the laptop is physically connected to the domain (i.e. the VPC behaves exactly as if it were a physical server on the network).
The reason I have the server running on a VPC, though, is to be able to continue development work and run realistic demos to clients when not connected to the domain. In this scenario, the network connection between the laptop and the VPC are lost (as the domain controller cannot be contacted).
Reading the help etc, the answer seems to be to install a Loopback Adapter on the laptop and use this for networking between the physical and virtual PCs, using fixed, non-routable IP addresses for the loopback adapter and the matching network connection on the VPC.
Again, this works okay, but now the VPC can't see the rest of the domain and vice versa.
I've tried fiddling around with multiple adapters in the VPC, but nothing I do seems to give me the best of both worlds, i.e. full domain visibility in both directions when connected and still working when mobile.
Does anybody (a) have a clue what I'm banging on about and (b) have any idea how to go about sorting it?
N.B. The laptop is using a hard-wired network connection to the domain, so the known issues with VPC and wireless networking aren't an issue.
Laptop running XP. Part of a domain.
Virtual PC running Win 2003 Server hosted on the laptop.
VPC running IIS and SQL Server 2005.
The default network settings are all fine and dandy as long as the laptop is physically connected to the domain (i.e. the VPC behaves exactly as if it were a physical server on the network).
The reason I have the server running on a VPC, though, is to be able to continue development work and run realistic demos to clients when not connected to the domain. In this scenario, the network connection between the laptop and the VPC are lost (as the domain controller cannot be contacted).
Reading the help etc, the answer seems to be to install a Loopback Adapter on the laptop and use this for networking between the physical and virtual PCs, using fixed, non-routable IP addresses for the loopback adapter and the matching network connection on the VPC.
Again, this works okay, but now the VPC can't see the rest of the domain and vice versa.
I've tried fiddling around with multiple adapters in the VPC, but nothing I do seems to give me the best of both worlds, i.e. full domain visibility in both directions when connected and still working when mobile.
Does anybody (a) have a clue what I'm banging on about and (b) have any idea how to go about sorting it?
N.B. The laptop is using a hard-wired network connection to the domain, so the known issues with VPC and wireless networking aren't an issue.
That's what I've been experimenting with, but with little proper success so far.
It could, however, be down to the IP settings I'm using on the 2 nics on the VPC; I'm very willing to believe that I've got them all screwed up!
Could anyone give me a brief pointer as to what kind of settings I'd need (e.g. Loopback nic with non-routable IP, other one using DHCP from the domain etc.)?
TIA
It could, however, be down to the IP settings I'm using on the 2 nics on the VPC; I'm very willing to believe that I've got them all screwed up!
Could anyone give me a brief pointer as to what kind of settings I'd need (e.g. Loopback nic with non-routable IP, other one using DHCP from the domain etc.)?
TIA
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff