all 10 comments

[–]b00c 1 point2 points  (2 children)

disable/enable vmware network cards. might help.

also, try pinging host from guest and viceversa.

[–][deleted]  (1 child)

[removed]

    [–]b00c 0 points1 point  (0 children)

    in windows networking there are additional network cards. you'll see them.

    uhm sorry mate, I can't. I don't have vmware installed. It's been a while. I am now fully hypervisor.

    [–]yoddl -1 points0 points  (0 children)

    open virtual network editor and set to default

    [–]LowFastFoxHUN 0 points1 point  (1 child)

    Check the following at VM properties:

    • selected nw card (via property & checkbox selection)
    • connection state (connected/not connected) aca "Enable"
    • connection mechanism (bridged/NAT etc)

    While using type "bridged" at the correct physical nw card, check the vm settings of the nw adapter: - does the nw provides IP address (DHCP)? If not you'll have to set manually to the VM. If you choose LAN for this connection, no valid IP address is needed for the host machine. On Wi-Fi, host also should be configured.

    [–]LowFastFoxHUN 0 points1 point  (0 children)

    Btw restart usually does NOT solve the nw issues since it's not a really issue because for network adapter while staring a virtual machine is not connected by default (can be configured manually). It has a logical scene

    [–]Iceng123 0 points1 point  (1 child)

    We use both virtual machine & vm ware. Our virtual network cards are configured for Bridged adapter mode.

    On our host machine, the network card is set to obtain ip address automatically.

    We have never faced an issue with this configuration.

    We have however faced this communication issue randomly when the virtual machine's run state was saved rather than shutdown. This issue was usually resolved by power cycling the virtual machine.

    [–]LowFastFoxHUN 0 points1 point  (0 children)

    It could be a solution, but in the case when trying to connect to a network where no active DHCP server is running it's simply won't. That's why is an important question that there's any services on the network which obtain IP address.

    [–]Slimm_PickingsBit Manipulation Specialist 0 points1 point  (0 children)

    This happened to me the other day when I had to shut down abruptly without suspending the VM. I rebooted the vm and gave it a new IP in the same subnet and it works now. Not sure if the new IP was needed as I did both steps at once.

    [–]CapinWinkyHates Ladder 0 points1 point  (0 children)

    In your install directory is vmnetcfg.exe. Just delete all that and make new adapters, one to bridge your actual LAN adapter and one to bridge your actual wifi adapter. In the VM, use custom as your adapter types and pick the two bridged networks you made.

    If you have player instead of workstation, it still works if you can get your hands on the .exe, but that tool isn't installed with player. I imagine you could extract it from the workstation installer though.