Small update:
Currently i use the VM in Bridged mode. For a big part of the work i need to do with the VM it work out well. But that doesn't mean i don't have any issues...
A few issues i noticed so far while using bridged mode:
- Last time i wrote:
@jbwinkel wrote:
If i use Host only network:
ping results here (somehow i can't quote code...)
This workout well too.
Today i noticed that when I'm in bridged mode the host only connection don't work.
- Also i had issue that i was unable to ping while Nmap was able to ping the VM
@jbwinkel wrote:
And now the most strange part... If i let Nmap do a ping scan i get the following result(s):
Nmap results here
So all Nmap detects all the (expected) IP-addresses. I'm unable to ping the same addresses and i'm unable to go to the VM's domain.
Basically i don't have any clue anymore where to find a solution.
Now i have basically the reversed issue.
I can't ping from VM to host but Nmap is able to ping:
C:\Users\Administrator>ping 192.168.1.33
Pinging 192.168.1.33 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
and
Starting Nmap 7.93 ( https://nmap.org ) at 2022-12-30 17:01 GMT
Nmap scan report for router-name (192.168.1.1)
Host is up (0.0020s latency).
MAC Address: 28:FF:3E:20:C5:01 (router-brand)
Nmap scan report for 192.168.1.2
Host is up (0.065s latency).
MAC Address: 48:A9:1C:CF:86:64 (PC-brand1)
Nmap scan report for 192.168.1.31
Host is up (0.037s latency).
MAC Address: 88:66:5A:23:2D:FC (PC-brand2)
Nmap scan report for 192.168.1.33 (192.168.1.33)
Host is up (0.0027s latency).
MAC Address: 38:7A:0E:A3:4D:C8 (PC-brand3)
Nmap scan report for VM-name (192.168.1.43)
Host is up.
Nmap done: 256 IP addresses (5 hosts up) scanned in 2.15 seconds
So basically still no clue what and why i have these issues... Every tip or idea is welcome
