But looking on the interface's Details it reported two IP addresses: a 169.x.x.x - failed DHCP - primary, and my static IP. I then looked at the Windows "Network Connections" for the "VMware Network Adapter VMnet8" interface, I had configured this with a static IP address. So I started with using the vmware's "Virtual Network Editor" to Restore Default and reconfigured my interfaces appropriately with numerous reboot - no improvement. To day it got a lot worse - my wireshark fix was just not doing it. Sometimes its not a problem, but generally I need to use wireshark to 'kick' the VMnet8 interface into operation (ie prior to this I can't ping from my Windows PC to the virtual host no VMnet8 interface). I have been suffering this problem for ages. UPDATING EVE NG WINDOWS 10I'm running Windows 10 Pro (1 Build 19041) with vmware workstation 16.0.0 build-16894299 I might have come across a solution - I hope! Request logs, I will try to provide them as quickly as possible. Restarting any of them does not solve the problem. It has the same problem as the NAT adapter.Ĥ) Windows troubleshooter didn't help at all.ĥ) Didn't find anything related to blocked adapters by OS/Soft.Ħ) Double checked all services related to VMware. UPDATING EVE NG UPDATEFound updates that cannot be removed in any way, including a method with editing update files in notepad or via the command line.Ģ) Attempt to restore default Network settings via VMware WS ( Temp solution).ģ) Attempt to use default Host-only Adapter at least to get access to EVE Web Interface and Bridged adapter to internet access. The manipulations with the defender did not lead to anything. After several days, without any Updates, problems appear again. Checked "updates log", tried to delete all last updates and turned off windows defender. After Windows Updates problem appears again. Even tried to recover much older recovery points. But I noticed that the problem persisted. Recovered the system to the last restore point before Upgrade. UPDATING EVE NG UPGRADEAfter upgrade to 2004 (20H1 build) first encountered this problem when I couldn't access the EVE's web interface. Rest of attempts when I thought I found the nature of the problem:ġ) Blamed on Windows Updates ( most likely version so far). UPDATING EVE NG DRIVERSTemporary solution: 1) !!! _Reboot_!!! the PC 2) Reboot (on/off) VMnet1 Adapter on Host 3) R e-install Drivers through Device Manager 4) Start capturing traffic with Wireshark (rly) Īfter !!! _Shutdown_!!!, boot PC the problem comes back. VMs are able to ping each other and have access to the internet. Screenshots will be attached.***Īfter boot Host is not able to ping both VMs. (Of course, everything works fine ONLY with Bridged adapter). Please, don't suggest using the "Bridged" adapter - that is not my case. *** It is important to note that only this "NAT" adapter is using now and will be used. Both configured with VMnet1 - NAT adapter. Problem: Have two VMs ( EVE-NG, Ubuntu 20.04). Fresh Re-Installed 1909 because I thought it will solve the problem, before was 2004 with July 2020 Update. But I have also tried the other mirrors available in SA.none of them make a difference.Host Hardware: Intel i7-8750H 6/12, 32 GB RAM, 512 GB SSD, Killer E2500 Gigabit Ethernet Controller It also makes no difference if I use a WiFi or network cable connection.Ī speed test (comes out at about 0.9 Mbps down and 0.42 Mbps up (which is a shade under the advertised line speed), I reside in South Africa and use the UCT LEG server. There are no faults on my ADSL line as I have already contacted my ISP to check this. I have also cut down what is in my sources list but this also makes no difference. I have attempted changing which mirror I use but that does not solve the issue. I am running 12.04 AMD64 and have recently started getting an issue that when I update my repos from my connection at home through a terminal, using sudo apt-get update, it takes forever (literally after 2 hours it was at 28%), however when I run from a different location it takes less than 5 minutes to complete. However neither one of them answer my problem. Apt-get update stuck on "Waiting for Headers" when using Windows XP ICS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |