ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:0c:29:e1:f3:6b brd ff:ff:ff:ff:ff:ff
I'm at a complete loss . . . this is the first time that you have mentioned anything about a customized VMnet8 setting ! ! !
This has been far from straightforward, particularly with unearthing relevant and consistent technical information in an effort to seek a solution. At every turn there have been unearthed surprises, including obscured, obfuscated, or removed information, making diagnoses somewhat tricky.
It appears that you may have a slightly bespoke setup, and that changes made to overcome perceived problems may have resulted in creating knock on effects. Unless you can put the setup back to a known good, then I would suggest getting another PC/laptop, set it up with a default install of VMware, and start over.
Just to start with, its a tad default to diagnose a network problems with limited redacted information, such as the local IP address and default gateway. I appreciate that in some cases this is prudent, but it does make diagnostics somewhat tricky.
However, with this in mind, this obfuscation would suggest that perhaps some of the Red Hat VM has been configured with some none NAT'ing settings.
So, make sure that the network configuration on the Red Hat VM is setup as NAT and within the same subnet as defined within your Virtual Network Editor. Ping and Traceroute are useful tools to see how far along the network you are getting.
As an aside, does the NAT setup work for other VMs ?
[root@et]# ip route | grep default default via 192.168.200.2 dev ens33
My VM machines are configured with NAT but I tested 3 VMs Linux machines and still no internet access, I need to use Yum command and cannot do it. In my first Post, I attached the virtual network definition VM8 and the VMs machines are configured with the VM8 Nat.
I've been trying to simulate what I believe is your scenario, but without any success, can you to tell me what distros and versions of Linux you have in your VMs.
Also, from the Red Hat VM could you ping '8.8.4.4' or '8.8.8.8' or '172.217.16.238'
The forum 'spoiler tag' is just a way to display and manage long lists of information (logs, command outputs, etc.), making it a bit easer for the reader to distinguish between the relevant description and any lengthy included data. But be selective to help the reader, so they don't have to thumb through pages of info just to get to the relevant bits, for instance if its only a few of lines then its not really required. . . but up to you.
When submitting, select the '...' on the toolbar, then position the cursor at an appropriate relevant location below the written text where you wish to locate it, then select the '' from the tool bar, and paste the output text into the opened box.
i will try to answer to your question, hope the spoiler tag is OK as I try to understand it!
I assume that the Win [version unknown] PC/laptop has access to the internet and is working ? WINDOWS 10 PRO no problem for internet access and I can ping the Linux and Windows VM machines. OK - Are the 3 Linux VMs independent installs or clones ? 3 independants no clone machines. - Do you have any other types of operating system VMs that either work or exhibit the same issue ? Yes, I have also Windows 2016 and Windows 2019 server. I can have access to internet and working fine. - That there is no VPN in operation on the Win PC/laptop ? NO VPN activ on the PC/Laptop - could you run ipconfig /all on the Win PC/laptop, and post (preferably in a forum 'spoiler tag')
See Tags hope it works fine?
THanks for your help and support.
Best Regards
root@etwsvm102t 10]# hostnamectl Static hostname: etwsvm102t.ch.pbk Icon name: computer-vm Chassis: vm Machine ID: 0d3815750d8a464dbcef67c9420aca8b Boot ID: ae297428bf114c08bfee6cb297544b19 Virtualization: vmware Operating System: Red Hat Enterprise Linux CPE OS Name: cpe:/o:redhat:enterprise_linux:7.8:GA:server Kernel: Linux 3.10.0-1127.el7.x86_64 Architecture: x86-64
[root@RHEL73F ~]# hostnamectl Static hostname: RHEL73F Icon name: computer-vm Chassis: vm Machine ID: a1b8d154ddcf4a7fb6306c0d69ae982b Boot ID: 18667a20bb064da3b246c3b888d39822 Virtualization: vmware Operating System: Red Hat Enterprise Linux CPE OS Name: cpe:/o:redhat:enterprise_linux:7.8:GA:server Kernel: Linux 3.10.0-1127.el7.x86_64 Architecture: x86-64
. . . for clarity, I notice that there are a number of VMnet interfaces shown within the Virtual Network Editor (subnet addresses obscured), therefore:
- Are the 'Win 10', 'Win 2016' and 'Win 2019' server VMs set to NAT [VMnet8], if so compare the allocated IPs and subnet against the ones allocated to the Linux VMs.
- could you confirm that virtual network interface for each of the Linux VMs are set to NAT [VMnet8] and have default settings (LAN segment, Advanced), again compare with the WIn settings.
- when pinging between the Linux, Windows Host and VMs, is that by name or IP ?
- Are all of the IPs unique between each of the VMs.
Could you provide a screen capture, unmodified, of the 'Virtual Machine Settings' for the Red Hat VM in question with the Network Adapter highlighted.
Ordinarily as part of this type investigation, I would have suggested switching the virtual network setting from NAT (VMnet8) to Bridged (VMnet0) but noted that it's been modified [Custom]. As such, as it is not default decided against this as it could possibly open up another whole can of worms.
Its an important part of any investigation to break things down into meaningful and manageable 'chunks', checking each in turn, then progressively verifying and confirming them together. In addition, it is important to peel away any complexity, and starting with the simplest implementation then moving on from there, adding required features and services after testing each in turn. Also ensure a known baseline before starting. Comparisons are also beneficial, such as comparing a working implementation with one that is not, even though they may be differing operating systems but supported by the same underling services. One other frequently overlooked approach is that if a generic error message is produced, then make a change in the relevant area to produce a modified error message, thus confirming the area where the issue may reside. And finally if hitting a brick wall, then try a tangent approach, such as installing a different unrelated popular distro to the one that is at issue, if you have other operating systems VMs that work, this helps with identifying where the issue may reside, and also helps trigger any thought as to what the issue is.
With your setup, all three of the Rad Hat VMs appear to have the same or a similar issue, so there is something common between them. I have many Red Hat VMs, versions, with and without GUI, etc., and have not had any network issues. The only slight irritation, is that in v8.1 with GUI installed, the user interface overrides the /etc config files, such as resolv.conf, but as most corporations don't use the GUI its not really an issue, just worth being aware of and using the network config in the GUI rather then editing the file.
I'm at a complete loss . . . this is the first time that you have mentioned anything about a customized VMnet8 setting ! ! !
This has been far from straightforward, particularly with unearthing relevant and consistent technical information in an effort to seek a solution. At every turn there have been unearthed surprises, including obscured, obfuscated, or removed information, making diagnoses somewhat tricky.
It appears that you may have a slightly bespoke setup, and that changes made to overcome perceived problems may have resulted in creating knock on effects. Unless you can put the setup back to a known good, then I would suggest getting another PC/laptop, set it up with a default install of VMware, and start over.
