whois google.com connect: Network is unreachable

I am new to Linux, I tried to use whois, but whatever address I gave always get Network is unreachable, I am using kali on VirtualBox. Tried using NAT, NAT Network, Bridge Adapter, my internet connection is fine.

I think there is a problem in port 43, how to solve please, [Update: I called my ISP; they said, port 43 is being used for game server; and I don't have a public ipv4 address; BUT my friend who use same isp, have not face any problem using whois]

[Update 2: i have found a solution, whois working fine using vpn, but still not working without vpn]

You may find these useful :
https://www.whatismyip.com/
https://opensource.com/article/18/5/...-address-linux

Google your problem: Network is unreachable, I am using kali on VirtualBox
(IDK but for stealth, Kali is probably set up to hide)

Look for the sticky that says: kali is appropriate only for Relevant experts. Try Ubuntu or my favorite MX.
apt install the tools you want to study one at a time.

Or continue with kali, but prepared to have 'thick skin' when people get annoyed when you violate http://www.catb.org/~esr/faqs/smart-questions.html
Personally, I'm happy for a chance to write something, so I say: welcome to LQ! (giving you the 'fish', instead of teaching you to 'fish', would be a disservice to you!)

Please post the solution, so future searchers can find it!

In your VirtualBox settings from this VM (Settings-->Network), what is the selected network type and adapter for this VM?

It's a shot in the dark, but if there is a selected network adapter and you have several choices of adapters, you might try cycling through those choices. You will need to restart the VM to test the new choice.

I've found that VirtualBox generally selects the correct adapter, but I've occasionally had to cycle through the choices myself to find the right one.

Tried using NAT, ..., Bridge Adapter, my [...]net connection is fine.

I bet OP can ping 10.0.2.2 ok.
I bet `ip r` will show the gw = default route is missing, for some (kali?) reason.

Or maybe OP booted with Bridged networking and the Gateway is still 192.168.x.y

Originally Posted by frankbell In your VirtualBox settings from this VM (Settings-->Network), what is the selected network type and adapter for this VM? It's a shot in the dark, but if there is a selected network adapter and you have several choices of adapters, you might try cycling through those choices. You will need to restart the VM to test the new choice. I've found that VirtualBox generally selects the correct adapter, but I've occasionally had to cycle through the choices myself to find the right one.

the network type is natnetwork, and the adapter type is intel pro/1000 MT desktop(82540EM) promiscuous mode: deny, cable connected: not selected

I tried to use whois

Please post the whole output with the whole input line....

Also from the VM:

ping -c2 8.8.8.8

ping -c2 google.com

ip a

Did you read the page at the link below to the Kali site which indicates that no 'externally listening services are enabled by default'? How to configure is explained.

https://www.kali.org/docs/policy/kal...ervice-policy/

Originally Posted by raselantor ... cable connected: not selected

Try: ping 10.0.2.2

Post the output of the command: ip r

Originally Posted by Sauerland Please post the whole output with the whole input line.... Also from the VM: ping -c2 8.8.8.8 ping -c2 google.com ip a

ping -c2 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=33.5 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=34.6 ms

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 33.463/34.049/34.636/0.586 ms

┌──(kali㉿kali)-[~]
└─$ ping -c2 google.com
PING google.com (142.250.193.174) 56(84) bytes of data.
64 bytes from maa05s26-in-f14.1e100.net (142.250.193.174): icmp_seq=1 ttl=54 time=34.8 ms
64 bytes from maa05s26-in-f14.1e100.net (142.250.193.174): icmp_seq=2 ttl=54 time=36.7 ms

--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 34.834/35.754/36.675/0.920 ms

┌──(kali㉿kali)-[~]
└─$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:3a:6c:4a brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic noprefixroute eth0
valid_lft 548sec preferred_lft 548sec
inet6 fe80::f22b:77bb:5f1d:7199/64 scope link noprefixroute
valid_lft forever preferred_lft forever

┌──(kali㉿kali)-[~]
└─$ ip r
default via 10.0.2.1 dev eth0 proto dhcp src 10.0.2.15 metric 100
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 100

Originally Posted by GentleThotSeaMonkey Try: ping 10.0.2.2 Post the output of the command: ip r

$ ip r
default via 10.0.2.1 dev eth0 proto dhcp src 10.0.2.15 metric 100
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 100

Looks like basic internet access is working okay (now/always?).
(I was off by one on the default gateway: it appears to be 10.0.2.1)

Does the whois program still fail with the same error? IF your host OS is M$Win, the quickest way to check might be to: try running the windows version of whois:
https://learn.microsoft.com/en-us/sy...ownloads/whois

Linux also has advanced Network tracing tools like tcpdump, wireshark

Here is some information about using code tags, to make posting of output clearer: https://www.linuxquestions.org/quest...-output-38639/
http://termbin.com/sq68 has the output from my: strace ... 2>&1 | grep -w 43

OP has *only* ipv6 address (no ipv4 address) from ISP. IDK ... (over & out)

https://www.linode.com/community/que...m-ipv6-address (probably not the same issue, but the only thing I found with that title)

Anybody?

@OP: you will get better response if you try (check it with) a distro other than kali, like Ubuntu/MX/Debian.
(it takes only a few minutes to try a .vdi from OSboxes.org/virtualbox
Or try Slackware and half of LQ will love you

One more idea: telnet ... 43
https://stackoverflow.com/questions/...-not-accessibl
https://superuser.com/questions/9600...outgoing-ports

Ask the ISP what exactly is the difference between your friend's account which can, and your account which can't. Do they have an IPv6 only?

The whois command is missing....

Originally Posted by Sauerland The whois command is missing....

└─$ whois google.com
connect: Network is unreachable