[clue-tech] VMServer 1.0 Host/Guest Internet problems

[Eric Beale]

Ok, so I'm at the network configuration piece in the 
vmware-config.pl...vmnet0 is bridged to eth0, vmnet2 is bridged to 
vmnet1...where/how do I set NAT?

Eric

Russell Glissmann wrote:
> No, re-running the vmware-config will not affect your virtual machines.
>
> On 12/19/06, *Eric Beale* <ebeale at releaseteam.com 
> <mailto:ebeale at releaseteam.com>> wrote:
>
>     Dave,
>
>     If I rerun the vmware-config.pl, is that going to wipe out all the
>     vm's
>     I've setup? Say it ain't so...if that's what it'll take, I'll do it,
>     cause I'll tell ya, I'm stump-ed.
>
>     Eric
>
>     David L. Willson wrote:
>     > 1. That's odd.  I've never been asked for the NIC driver by any
>     Windows guest, and I've
>     > built several of them.
>     > 2. You are probably going to want to re-run
>     /usr/bin/vmware-config.pl or equivalent.  It
>     > looks like you didn't configure NAT for your guests.
>     > 3. If this is all too much, I know a guy who works for beer, and
>     can probably fix it.   :-)
>     >
>     > On Mon, 18 Dec 2006 16:08:13 -0700, Eric Beale wrote
>     >
>     >> Yeah, that #2 didn't work...grumblegrumble...The WinXP vm
>     detects the
>     >> 'new' hardware, but I am unable to update drivers for it, ergo,
>     it does
>     >> not 'install'. Recommends that I connect to the internet to get the
>     >> latest drivers, which, ironically enough, is exactly what I'm
>     trying to do.
>     >>
>     >> In your #1 suggestion, you say change the host vm settings to
>     NAT. My
>     >> host settings have no option for that in the VMWare Server console-
>     >> where is this setting?
>     >>
>     >> David L. Willson wrote:
>     >>
>     >>> Dave means IP and DNS, not IP and DHCP.  DHCP ~is~ the
>     automatically...
>     >>>
>     >>> Here's an easy way to make it all happen right.
>     >>>
>     >>> 1. From the host, in the VM settings, set the network adapter
>     to NAT,
>     >>> not bridged or host-only.
>     >>> 2. In the guest, in Device Manger, remove any and all devices
>     in the
>     >>> Network Adapters class.
>     >>> 3. Reboot the guest.  (Yes, reboot).  When it comes up, it
>     should detect
>     >>> and configure the Lance adapter that VMware provides to guests.
>     >>>
>     >>> NOTE:  The actual host adapter doesn't matter a bit to the
>     guest.  The
>     >>> only thing that matters to the guest is, if you've set it for
>     bridged,
>     >>> that you have configured vmware-bridging on the host adapter
>     that's
>     >>> connected.  With dial-up host, that probably won't work.  I
>     dearly hope
>     >>> that you did setup NAT networking when you ran the VMware config
>     >>> scripts.  If not, rego them.
>     >>>
>     >>> On Mon, 2006-12-18 at 12:59 -0700, David L. Anselmi wrote:
>     >>>
>     >>>
>     >>>> Eric Beale wrote:
>     >>>>
>     >>>>
>     >>>>> Fellas,
>     >>>>>
>     >>>>> Does the VM setting need to be configured with it's own IP
>     address? Or
>     >>>>> does it pick up the IP address, which can be either an
>     'external' IP-
>     >>>>> 72.16.x.x- or 'internal'- 192.168.x.x....
>     >>>>>
>     >>>>>
>     >>>> Yes, the VM needs to have its own IP and it has to be "internal",
>     >>>> assuming that your Internet connection stuff supports more
>     than one
>     >>>> device on your LAN.
>     >>>>
>     >>>> The easiest way to get that is probably to switch the VM from
>     bridged to
>     >>>> NAT, with the guest set to auto for IP and DHCP.  Try it.
>     >>>>
>     >>>> Dave
>     >>>> _______________________________________________
>     >>>> clue-tech mailing list
>     >>>> clue-tech at cluedenver.org <mailto:clue-tech at cluedenver.org>
>     >>>> http://www.cluedenver.org/mailman/listinfo/clue-tech
>     <http://www.cluedenver.org/mailman/listinfo/clue-tech>
>     >>>>
>     >>>>
>     >>> _______________________________________________
>     >>> clue-tech mailing list
>     >>> clue-tech at cluedenver.org <mailto:clue-tech at cluedenver.org>
>     >>> http://www.cluedenver.org/mailman/listinfo/clue-tech
>     >>>
>     >>>
>     >>>
>     >> _______________________________________________
>     >> clue-tech mailing list
>     >> clue-tech at cluedenver.org <mailto:clue-tech at cluedenver.org>
>     >> http://www.cluedenver.org/mailman/listinfo/clue-tech
>     <http://www.cluedenver.org/mailman/listinfo/clue-tech>
>     >>
>     >
>     >
>     > David L. Willson
>     > Trainer/Engineer/Consultant
>     > MCT, MCSE, Linux+
>     > (720) 333-LANS
>     >
>     > _______________________________________________
>     > clue-tech mailing list
>     > clue-tech at cluedenver.org <mailto:clue-tech at cluedenver.org>
>     > http://www.cluedenver.org/mailman/listinfo/clue-tech
>     >
>     >
>     _______________________________________________
>     clue-tech mailing list
>     clue-tech at cluedenver.org <mailto:clue-tech at cluedenver.org>
>     http://www.cluedenver.org/mailman/listinfo/clue-tech
>     <http://www.cluedenver.org/mailman/listinfo/clue-tech>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> clue-tech mailing list
> clue-tech at cluedenver.org
> http://www.cluedenver.org/mailman/listinfo/clue-tech