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