Arch Linux

charles_houston

Member

Registered: 2015-05-17

Posts: 11

Ping 8.8.8.8 works but not www.google.com-Initial installation.

I am trying to install Arch on my new t420 thinkpad and am running into difficulties connecting to the internet for my installation. In the past for my Arch installation I have always used a wired connection but this time I am away from the house and all I have is a WPA2 network to connect on. Now I can connect to the network but when I try to ping google I do not receive any packets back. However, when I ping 8.8.8.8 it works just fine. It does not seem to be a resolv.conf problem as the correct nameservers are present. I realized that I never got to installing wpa_supplicant because I could not connect to the internet. Could this be the problem even though I get a connection to the network but not the internet? I am curious because I will be back home soon to do a wired install and would like to know if there is a more significant issue with my wireless that I need to be made aware of.  Let me know if you need any file or terminal information. I have to reboot my bootable to access it otherwise I would put it in the post.

Last edited by charles_houston (2016-07-18 02:53:57)

mpan

Member

Registered: 2012-08-01

Posts: 1,375

Website

Re: Ping 8.8.8.8 works but not www.google.com-Initial installation.

And what’s the result of doing `ping www.google.com`?

Probably you don’t have your DNS configured, but without the basic info, which you have “forget” to provide, we can only guess.

---

Sometimes I seem a bit harsh — don’t get offended too easily!

insideable

Member

Registered: 2016-07-18

Posts: 7

Re: Ping 8.8.8.8 works but not www.google.com-Initial installation.

Can you dump your /etc/resolv.conf and /etc/resolvconf.conf here?

Last edited by insideable (2016-07-18 06:29:46)

charles_houston

Member

Registered: 2015-05-17

Posts: 11

Re: Ping 8.8.8.8 works but not www.google.com-Initial installation.

I got it to work after doing a Ethernet  net install. I believe it was somehow related to the dhcpcd service because after disabling the multi-target-user-wants file the wireless connection was able to establish a working internet connection.