VM cannot conect to the Internet through NAT (VPC 2007)

Hello,

I cannot connect to the interent using NAT on my VM. However when changing the networking settings on the VM to use my host computers network adapter everything works fine.

Host: Windows 7 Enterprise
Guest: Windows Server 2003 R2 Enterprise SP2
VPC 2007 SP1

I've also tried pointing to the DNS server 192.168.131.254 as I read in some other blogs that this may be the problem but still nothing. Not sure what I'm doing wrong.

Thanks in advance for the help!
RayRay13Asked:
Who is Participating?
 
Svet PaperovIT ManagerCommented:
I’ve just read this blog. Obviously Windows Server 2003 doesn’t work with the default configuration “by design”. You were right to set manually the DNS to 192.168.131.254.

Try the following command from the virtual machine:
nslookup www.yahoo.com 192.168.131.254 

Open in new window

You should receive a non-authoritative answer.

In your question you said you were using VPC 2007 SP1. VPC is officially not supported on Windows 7. On Windows 7, Microsoft has replaced VPC by Windows Virtual PC that is installed with Windows XP mode. You can get it from here: http://www.microsoft.com/windows/virtual-pc/ 
0
 
spiderwilk007Commented:
I have always had problems with VPC correctly networking, I think I had to use the bridged option to get it to work. Use VMware Server it's free and way better.

0
 
RayRay13Author Commented:
Bridged option? Not sure what you mean.

I was under the impression that the VMWare player was free but I'd need a paid version to actualy create and modify VMs. Is that not the case?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Svet PaperovIT ManagerCommented:
You need to leave all settings of the TCP/IP in the VM in automatic mode (DHCP). In that case your DNS will be the DNS of the host when you are using the Shared NAT mode. However, using the physical adapted (a.k.a. “bridged mode”) is much better and your VM will appear as a host in the local network.
0
 
RayRay13Author Commented:
It works fine when I'm using my hosts computer's network adapter but even when I leave have all TCP/IP setting in the VM set to default (see screen shot) NAT does not allow me to connect to the internet which is what I'm trying to fix.  TCP/IP settings
0
 
Svet PaperovIT ManagerCommented:
What is the output of ipconfig /all command in the virtual machine?
0
 
RayRay13Author Commented:
Windows IP Configuration

   Host Name . . . . . . . . . . . . :
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Generic)
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 192.168.131.65
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.131.254
   DHCP Server . . . . . . . . . . . : 192.168.131.254
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   Lease Obtained. . . . . . . . . . : Tuesday, April 26, 2011 11:29:50 PM
   Lease Expires . . . . . . . . . . : Sunday, April 30, 2028 6:18:21 PM
0
 
RayRay13Author Commented:
Thanks for the help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.