Nmap scan with kali guest and Win10 quests in Win10 Host

Discussions related to using VirtualBox on Windows hosts.
Clawsman
Posts: 16
Joined: 22. May 2022, 18:44

Re: Nmap scan with kali guest and Win10 quests in Win10 Host

Post by Clawsman »

fth0 wrote:You're not trying what scottgus1 (and me) wanted you to try, which would have been using ping 192.168.18.29.

Using nmap -sP is already more sophisticated and consequently can fall into more complex traps. Therefore, I wouldn't start with nmap before the simple ping above doesn't work.
ah..indeed

So it seems the ping finds it

ping 192.168.18.29
PING 192.168.18.29 (192.168.18.29) 56(84) bytes of data.
64 bytes from 192.168.18.29: icmp_seq=1 ttl=128 time=292 ms
64 bytes from 192.168.18.29: icmp_seq=2 ttl=128 time=5.81 ms
64 bytes from 192.168.18.29: icmp_seq=3 ttl=128 time=12.0 ms
64 bytes from 192.168.18.29: icmp_seq=4 ttl=128 time=4.06 ms
64 bytes from 192.168.18.29: icmp_seq=5 ttl=128 time=50.3 ms
64 bytes from 192.168.18.29: icmp_seq=6 ttl=128 time=326 ms
64 bytes from 192.168.18.29: icmp_seq=7 ttl=128 time=31.8 ms
^C
--- 192.168.18.29 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6004ms
rtt min/avg/max/mdev = 4.063/103.133/325.774/131.339 ms

But i cannot give up on nmap :cry: its a powerful most essential tool.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Nmap scan with kali guest and Win10 quests in Win10 Host

Post by fth0 »

Ok, ping works, which means that the VirtualBox networking works in general. Although you seem to be using an unreliable network (probably WiFi), according to the erratic round trip times.

I'll agree that nmap is a powerful tool in the hand of a powerful user. ;) You could try (and get to know?) some of the different nmap scan techniques. And perhaps you have to adjust some of nmap's timeouts, if you want to stay using the unreliable network.
Clawsman
Posts: 16
Joined: 22. May 2022, 18:44

Re: Nmap scan with kali guest and Win10 quests in Win10 Host

Post by Clawsman »

fth0 wrote:Ok, ping works, which means that the VirtualBox networking works in general. Although you seem to be using an unreliable network (probably WiFi), according to the erratic round trip times.

I'll agree that nmap is a powerful tool in the hand of a powerful user. ;) You could try (and get to know?) some of the different nmap scan techniques. And perhaps you have to adjust some of nmap's timeouts, if you want to stay using the unreliable network.
it was great to know that virtualbox is set up correct :)
yes indeed i have understood that it is a powerful tool. but yet my hands are not that powerful :lol: i am in a learning curve when it comes to networking.
so i have nmap as a first priority to learn as much as possible about it. before going ahead to the next steps.
you say unreliable network, you mean unsecure? :shock:
i am connected to an extender which is connected to my router, all wireless.
BillG
Volunteer
Posts: 5102
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: Nmap scan with kali guest and Win10 quests in Win10 Host

Post by BillG »

No, he meant unreliable. Did you look at the round-trip times he mentioned (for the pings)? They are all over the place. On a reliable network they would be very similar. Even your pings to a public IP (8.8.8.8 ) are more reliable.
Bill
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Nmap scan with kali guest and Win10 quests in Win10 Host

Post by fth0 »

Clawsman wrote:you say unreliable network, you mean unsecure?
fth0 wrote:an unreliable network (probably WiFi), according to the erratic round trip times.
Imagine that for one of the nmap scanning modes, nmap would wait 100 ms for an answer, which is quite a long time in a LAN (local area network). Then it would depend on some "luck" if another network device would be detected. If necessary, you can adjust the number of scan packets and the timeouts in nmap.

The round trip times to the Google DNS server are in a typical range (between 10 ms and 100 ms). Their variations already indicated wireless being involved (or another source of disturbance on the path). In a LAN, I'd expect round trip times below 10 ms. In a WLAN, I'd expect round trip times below 100 ms.

Have fun learning nmap! :)
Post Reply