Wierd VMWare behavior

[Jerry Feldman]

On Thu, 13 Sep 2007 09:15:50 -0400
Matthew Gillen <me-5yx05kfkO/aqeI1yJSURBw at public.gmane.org> wrote:

> Jerry Feldman wrote:
> > On Thu, 13 Sep 2007 08:18:23 -0400
> > "Kristian Erik Hermansen" <kristian.hermansen-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
> >=20
> >> If you place the virtual interfaces into NAT mode, DHCP shall always
> >> work, because it is a locally running service...
> >=20
> > It's in NAT mode. This is why it is hard to track. The only difference
> > is the specific network. At home, I have 192.168.0. and at work it is a
> > 10.=20
> > But, I don't see why the network would have any affect in being able to
> > load the VM.=20
>=20
> IIRC, when setting up NAT mode, VMware probes for an unused network to us=
e for
> the "internal" addresses.  Could whatever it picked at home be colliding =
with
> the work subnet?
>=20
> As to why it won't load the VM: perhaps at work VMware detects that the
> guest's subnet is currently in use on the host, and it bombs out?

But that should not prevent me from opening the VM. It should just
prevent it from communicating.=20
--=20
Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9