ah..indeedfth0 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.
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 its a powerful most essential tool.