|
Question : Virtual PC doesn't connect to network
|
|
I have a VPC 2007 running Vista on a Vista host. This is on a laptop connected wirelessly to my home network. The host connects fine and gets its IP dynamically. The VPC is set to NAT for the network configuration and also gets its IP dynamically. The VPC says that it is connected but it can't surf.
The VPC can ping itself, router, and host. The host can't ping the VPC. It gets timeouts.
Here are the IPs: gateway/router: 192.168.1.1 host: 192.168.1.65 VPC: 192.168.131.65
I imagine the problem is the VPC's IP. I don't know why it grabs that address. The router is setup to allocated a certain block of IPs. There aren't any in 192.168.131.xxx.
I have tried configuring the VPC to use the host's network card. That didn't work and it gets the same IP. I have another Vista box running Vista on VPC 2007. The VPCs setup on that box connect fine and also get the 192.168.131.xxx IPs. Any suggestions what's wrong with this VPC?
|
Answer : Virtual PC doesn't connect to network
|
|
Your IP configuration is correct. Virtual PC has a built-in dhcp server that gives out addresses in the range: 192.168.131.x for x from 1 to 253, when you use shared networking.
I suggest you capture network traffic off your wireless card to get more info:
https://www.microsoft.com/downloads/details.aspx?familyid=18B1D59D-F4D8-4213-8D17-2F6DDE7D7AAC&displaylang=en
Vista has an outbound firewall, so you might want to check those settings also.
|
|
|