Attempting to set up Fedora 10 on VMware Workstation - v5.5.3 build 34685 - running on WinXP. This is at work - an ISP HelpDesk - so that we can troubleshoot the growing number of Linux users we've got...AND so that I can preach the Good GNU's to my fellow HelpDeskians. It installs fine off the media but, once installed, can't browse or update. Ping - and DNS - work fine...just can't do anything other than ping. Had installed with VMware set to "Bridge" so tried "shared" and "NAT": still didn't work.

The Win98 and Win2k systems installed under VMware, here, work fine...so what gives? Tried installing from a KDE Live CD: same result with all networking types.

Then I tried just "booting" the guest OS onto the Live CD: could ping - and DNS still worked - but couldn't do anything else. Googled and found many "install VMware on Linux..." but nothing to help me with this. Looked for a HOWTO: no dice (but I know who'll be doing one just as soon as I figure this out...namely, me). To paraphrase Ill Will: "What do I do, oh Gurus of computer wisdom?"

One of the things, and you as "HelpDeskian" should understand that from a diagnostics point of view, is that "can't ping, can't browse, can't update, didn't work" type of replies offer almost zero clues while posting (diffs of) actual configuration and shown errors will. If you want to show others how well GNU/Linux behaves you should be familiar with basic networking troubleshooting like knowing the network configuration locations and using tools like ifconfig, route, ip and such. Saying "same result with all networking types" to me conveys you should read up on VMware networking. Think of "Bridged" as having another physical machine (so LAN DHCPd provides IP address) and NAT as a "hidden" machine as it uses the VMware host network specs.

So. Show us your GNU/Linux-fu! Choose your network type for the VMguest, run us through the relevant network configuration, tool output from ifconfig, route, iptables and any client or host-side logged errors.

unSpawn SAID:
> One of the things, and you ... should understand ... is that [general
> symptom listings] offer almost zero clues....
SOP here is that if a customer describes general symptoms that 90% match a very specific cause, we skip ahead and check that. If that doesn't work, then we come back to the top of the checklist and take things in order. I was hoping someone would say, "Oh! I had the same issue...try this first".

unSpawn [also] SAID:
> Show us your GNU/Linux-fu!...
Actual, I don't have much network linux-fu anymore: I haven't had network issues w/ linux since the 1990's. Good news/bad news - in this case - I guess.

Please find attached the diagnostics I ran: I could find logged errors neither in the guest OS nor in VMware itself. And, yes...I know that the host-only SHOULDN'T let me out. I include it here for completeness. That's also SOP in our HelpDesk: we include EVERYTHING that might POSSIBLY point toward a solution and let others do the filtering. Here you go...

bridged_diags.txt

host-only_diags.txt

NAT_diags.txt

Oh, crap.
Oh-h-h-h-h-h-h #$@%#$&*$&*!

...okay...

...apparently the NAT and host-only diagnostics I ran in the VMware guest-OS didn't save to the thumb-drive.

I'll post them tomorrow.
(sigh...oh crap)

Oh! I had the same problem. CAN ping by name. can NOT browsr or update.
I don't know if it's a router issue, but I had that same issue at home, but it worked fine at school. this issue is a fedora issue as far as I can tell.
You have to change the "nameserver" line in /etc/resolv.conf.
go here:
http://dnsserverlist.org/

and replace the line in /etc/resolv.conf with a different ip address from that list (somewhere close preferably)

and if you can make resolv.conf read only so networkmanager doesn't over write it, with the command line, give me a hint.

As far as sop goes, people often skip ahead around here then gradually work their way back to "are you connected to the lan?" when often a simple (linux)question like "what is the output of ping -c 3 yahoo.com" would have shed more light than intricate conjecture. just my two cents.

from my n810.
hardly

! SOLVED !

This stems, it turns out, from a known issue w/ Fedora and Arch. 'Hardly', here at LinuxQuestions.org pointed me to the right path...
> Oh! I had the same problem. CAN ping by name. can NOT browsr or update... is a fedora issue as far as I can tell.
> You have to change the "nameserver" line in /etc/resolv.conf.
> and replace the line in /etc/resolv.conf with a different IP address from that list (somewhere close preferably)
> and if you can make resolv.conf read only so networkmanager doesn't over write it, with the command line, give me a hint.
> ...
> from my n810.
> hardly

I checked out the article and found what he'd said: networkmanager kept overwriting the 'resolv.conf' no matter what I did. Got it working, finally, though after a bit more reading on this track. The two articles from which I culled the solution were...
- http://bbs.archlinux.org/viewtopic.php?id=63580
- http://bbs.archlinux.org/viewtopic.php?id=45394
and the solution was provided by 'finferflu': a LinuxQuestions.org forum moderator from Pomezia in Roma, IT.

> Put a script like this in /etc/Networkmanager/dispatcher.d/ and don't forget to make it executable:
> #!/bin/bash
> #
> # Override /etc/resolv.conf and tell
> # NetworkManagerDispatcher to go pluck itself.
> #
> # scripts in the /etc/NetworkManager/dispatcher.d/ directory
> # are called alphabetically and are passed two parameters:
> # $1 is the interface name, and $2 is "up" or "down" as the
> # case may be.
> # Here, no matter what interface or state, override the
> # created resolver config with my config.
> cp -f /etc/resolv.conf.myDNSoverride /etc/resolv.conf
>
> Then create a file with the nameservers (in my case opendns ones), according to what you specified on the script
> (in my case /etc/resolv.conf.myDNSoverride):
> nameserver 208.67.222.222
> nameserver 208.67.220.220
>
> Of course you'll have to start the daemon networkmanager-dispatcher.

Where he mentions making the file 'executable' using the 'chmod' command as in:
chmod 111 11-dnsOverride

where '11-dnsOverride' is the script name from the '/etc/NetoworkManager/dispatcher.d' directory.


Works like a charm! Thanks all...let's call this one SOLVED!

Glad to see that you got it sorted. :-) Thanks for posting back and updating + totally rocking with the extra info.