LinuxQuestions.org - Running Fedora 14 as virtual machine on Windows 7 Host/can ping no internet

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Running Fedora 14 as virtual machine on Windows 7 Host/can ping no internet (https://www.linuxquestions.org/questions/linux-newbie-8/running-fedora-14-as-virtual-machine-on-windows-7-host-can-ping-no-internet-860700/)

Running Fedora 14 as virtual machine on Windows 7 Host/can ping no internet

Hello all,
I'm new to Linux (been using Fedora 14 about a week). I have VMware server 2 installed on a Windows 7 laptop and a Fedora 14 virtual machine using NAT. I'm connected to the network and can ping google.com or other websites, but I can not pull it up in the browser. I also am unable to update with "yum install updates". So far I have manually configured /etc/resolv.conf as follows:

# Generated by NetworkManager
63.251.62.33

I have also toggled the disableipv6dns setting in firefox to true. I am also unable to get to websites using the IP. I temporarily disabled selinux just to make sure it wasn't a security policy that was keeping me from doing it. Just to reiterate, I can ping outside hosts and I can hit my network gateway. Any help would be appreciated.

That 63.251.62.33 would be your nameserver?
It should be the same as in your windows config.

Also, I'd expect the directive to be "nameserver 63.251.62.33", rather than just the address, but I'm on CentOS. Also, I'm missing the default search domain. But as you state you can ping websites by name it may be OK. Also, normally you'd use your local DSL gateway address as your nameserver, and I would not expect 63.251.62.33 to be an address on your local lan, as it's not in a private IP range. The address you use is part of InterNAP Network Services's network.

Here's my /etc/resolv.conf:

Code:

$ cat /etc/resolv.conf

; generated by /sbin/dhclient-script

search lan

nameserver 10.10.1.254

10.10.1.254 is my DSL gateway.

What do you mean by 'hit my network gateway'? Can you open its config in your browser? Or just ping it? What's the error you get when trying to browse to google.com? 'not found' or 'not responding'.

You may also want to check out Windows Firewall, or whatever firewall you're using on Windows, to ensure it's not blocking you VM's traffic.

Please post back with specific action details (i.e. not use terms like 'hit') and exact message information.

I changed to that nameserver because the cable modem gateway wasn't allowing me to browse, so I thought I would try a different dns server. I just changed back to gateway for nameserver and I'm getting the same results. I can ping google.com, etc., but I can't browse. I am connected now through my android phone which afaik doesn't have a web management interface, but I will try getting to my router management interface when I get home. What baffles me is that I can ping everything using a host name. I just can't browse. I can ping all virtual interfaces and host interfaces including the gateway (right now my android phone, openwrt linksys router when I'm at home).

Okay, I'm unable to login to the web interface of my router (192.168.1.1) in using firefox, but I can ping it. The error I'm getting is "The connection has timed out".

Hmm, this should work, normally, but it looks like you may be looking at a bug here.
Googling I found this thread from 2009:
http://www.sevenforums.com/virtualiz...t-problem.html
Sounds exactly like your problem, and it's unrelated to Fedora, but all the more to Win7 and/or VMware. Seems that bridging will work. Not sure what versions you're on, but you may want to try the latest if you don't have those yet.

Another thought concerns the interface you're using, wired or wireless.

I use VirtualBox and found that bridging to the wireless LAN causes issues, but to the wired LAN works fine. NAT, on the other hand, has no issues at all. So you may want to check whether a similar issue is at play here.

Good luck and success.
René

I think vmplayer would have been a better choice to try playing with. Has worked perfectly on W7-32 and x64 on all sorts of OS's. I used to use virtualbox and there is still vmlite and vitualpc. All better choices.

Saying all that I think nslookup would be a good choice on both W7 and linux. I can't tell if dns or a proxy deal is the issue right now. I kind of don't think proxy as you can ping.

Remember that NAT in vm's basically has a virtual router. I usually don't use any other setting in nat and never change the name servers. Just let it do it's dhcp and dns as if you were connected to a regular modem or such.