Results 1 to 4 of 4

Thread: new PC and No view any networks on Ubuntu guest

  1. #1
    Join Date
    Mar 2022
    Beans
    5

    new PC and No view any networks on Ubuntu guest

    Hello!

    I have installed a new PC and copied my vmware virtual machine to it.
    Unfortunately I am not able to get any network connections working in the guest OS.


    ifconfig only shows the loopback network.
    I tried both Bridged, NAT and Host-only. I already used the Virtual Network editor to make sure bridged uses the correct adapter on the host.


    But since NAT and Host-only also doesn't work I think something else is wrong, but I have no clue what I could do.


    The host OS is using a WiFi adapter on the motherboard.
    I use VMware Workstation Pro 14.1.7 build-12989993
    My host OS is Windows 10 Pro.
    My guest OS is Ubuntu 18.04.1 LTS


    I would very much appreciate any help.
    Thanks!

  2. #2
    Join Date
    Jul 2008
    Location
    The Left Coast of the USA
    Beans
    Hidden!
    Distro
    Kubuntu

    Re: new PC and No view any networks on Ubuntu guest

    Moved to Virtualisation
    Please read The Forum Rules and The Forum Posting Guidelines

    A thing discovered and kept to oneself must be discovered time and again by others. A thing discovered and shared with others need be discovered only the once.
    This universe is crazy. I'm going back to my own.

  3. #3
    Join Date
    Mar 2022
    Beans
    5

    Re: new PC and No view any networks on Ubuntu guest

    Hi, no any reply about this?

  4. #4
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: new PC and No view any networks on Ubuntu guest

    Since your Host OS is Windows 10 Pro, peope here might be a bit hesitant to answer... Windows has some caveots about 'sharing' network interfaces...

    When doing VM Hosts on Windows, it gets more intricate. Make sure you do a backup to be able to get back to a working configuration. You want to use a "Bridged" connection. Tradtiionally, if you used a bridge connection on Windows to get access between a virtual switch to a real netwrok device on your host network, then that network device is marked as a dedicated device and you lose it as an asset to the host... That is the easy, short, summarized answer.

    There are ways to make a NIC 'shared' between VSwitch and the Host, for both to use... But is includes very detailed configuration setup, that must be followed to the letter. Follow a guide or tutorial somewhere to do it. I would suggest one on MS TechNet or the MS Doc's. The reason I suggest a backup "before" and many screenshots during that(?). I've done this myself, and if you do not do that, it is almost impossible to back off the changes or to remove it without a reinstall. So be warned.

    Easiest and fastest still, is to dedicate a network device to the virtual network. Even if you have a laptop and cannot add an internal NIC,,, get a portable USB NIC, that will be dedicated for your bridge... If that is what you need. Much simpler.

    "Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637
    Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •