How to restore internet connectivity to U 16.04.5 desktop?











up vote
0
down vote

favorite
1












All of a sudden, the desktop cannot access the internet either wired or wireless. It can see other machines on the local network, can read/write files on other devices, which can read/write files on the affected desktop. Other machines happily cruise c-space, but my desktop remains chained to the dock. I suspect a corrupt file, but can't fix it without internet access. Tried the repair option from the grub launcher without success. Don't like the option of reinstalling from a live CD. Am I missing something?




Output of command sudo lshw -C network



 *-network               

       description: Ethernet interface

       product: Ethernet Connection I217-V

       vendor: Intel Corporation

       physical id: 19

       bus info: pci@0000:00:19.0

       logical name: eth0

       version: 05

       serial: 74:d4:35:12:3f:67

       size: 1Gbit/s

       capacity: 1Gbit/s

       width: 32 bits

       clock: 33MHz

       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.144 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s

       resources: irq:25 memory:f0400000-f041ffff memory:f043d000-f043dfff ioport:f080(size=32)


output of command ip link



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff


output of command ip addr



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

    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 pfifo_fast state UP group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic eth0

       valid_lft 86230sec preferred_lft 86230sec

    inet6 fd82:76e3:b254:0:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 7032sec preferred_lft 3432sec

    inet6 2605:a000:110e:230c:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 604632sec preferred_lft 604632sec

    inet6 fe80::76d4:35ff:fe12:3f67/64 scope link 

       valid_lft forever preferred_lft forever


output of command ping 192.168.1.1



PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.606 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.522 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.565 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.548 ms

^C

--- 192.168.1.1 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 5998ms

rtt min/avg/max/mdev = 0.521/0.562/0.608/0.045 ms


output of command ping 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=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=24.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=22.9 ms

^C

--- 8.8.8.8 ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 9011ms

rtt min/avg/max/mdev = 22.250/23.126/24.826/0.679 ms





networking grub2 system-installation internet







share|improve this question
























  • Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
    – guiverc
    Nov 7 at 3:20










  • Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
    – Ted Saker
    Nov 7 at 13:30










  • Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
    – guiverc
    Nov 7 at 22:33










  • I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
    – Ted Saker
    Nov 8 at 12:16










  • Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
    – guiverc
    Nov 8 at 12:32















up vote
0
down vote

favorite
1












All of a sudden, the desktop cannot access the internet either wired or wireless. It can see other machines on the local network, can read/write files on other devices, which can read/write files on the affected desktop. Other machines happily cruise c-space, but my desktop remains chained to the dock. I suspect a corrupt file, but can't fix it without internet access. Tried the repair option from the grub launcher without success. Don't like the option of reinstalling from a live CD. Am I missing something?




Output of command sudo lshw -C network



 *-network               

       description: Ethernet interface

       product: Ethernet Connection I217-V

       vendor: Intel Corporation

       physical id: 19

       bus info: pci@0000:00:19.0

       logical name: eth0

       version: 05

       serial: 74:d4:35:12:3f:67

       size: 1Gbit/s

       capacity: 1Gbit/s

       width: 32 bits

       clock: 33MHz

       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.144 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s

       resources: irq:25 memory:f0400000-f041ffff memory:f043d000-f043dfff ioport:f080(size=32)


output of command ip link



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff


output of command ip addr



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

    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 pfifo_fast state UP group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic eth0

       valid_lft 86230sec preferred_lft 86230sec

    inet6 fd82:76e3:b254:0:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 7032sec preferred_lft 3432sec

    inet6 2605:a000:110e:230c:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 604632sec preferred_lft 604632sec

    inet6 fe80::76d4:35ff:fe12:3f67/64 scope link 

       valid_lft forever preferred_lft forever


output of command ping 192.168.1.1



PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.606 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.522 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.565 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.548 ms

^C

--- 192.168.1.1 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 5998ms

rtt min/avg/max/mdev = 0.521/0.562/0.608/0.045 ms


output of command ping 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=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=24.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=22.9 ms

^C

--- 8.8.8.8 ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 9011ms

rtt min/avg/max/mdev = 22.250/23.126/24.826/0.679 ms





networking grub2 system-installation internet







share|improve this question
























  • Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
    – guiverc
    Nov 7 at 3:20










  • Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
    – Ted Saker
    Nov 7 at 13:30










  • Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
    – guiverc
    Nov 7 at 22:33










  • I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
    – Ted Saker
    Nov 8 at 12:16










  • Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
    – guiverc
    Nov 8 at 12:32













up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





All of a sudden, the desktop cannot access the internet either wired or wireless. It can see other machines on the local network, can read/write files on other devices, which can read/write files on the affected desktop. Other machines happily cruise c-space, but my desktop remains chained to the dock. I suspect a corrupt file, but can't fix it without internet access. Tried the repair option from the grub launcher without success. Don't like the option of reinstalling from a live CD. Am I missing something?




Output of command sudo lshw -C network



 *-network               

       description: Ethernet interface

       product: Ethernet Connection I217-V

       vendor: Intel Corporation

       physical id: 19

       bus info: pci@0000:00:19.0

       logical name: eth0

       version: 05

       serial: 74:d4:35:12:3f:67

       size: 1Gbit/s

       capacity: 1Gbit/s

       width: 32 bits

       clock: 33MHz

       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.144 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s

       resources: irq:25 memory:f0400000-f041ffff memory:f043d000-f043dfff ioport:f080(size=32)


output of command ip link



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff


output of command ip addr



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

    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 pfifo_fast state UP group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic eth0

       valid_lft 86230sec preferred_lft 86230sec

    inet6 fd82:76e3:b254:0:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 7032sec preferred_lft 3432sec

    inet6 2605:a000:110e:230c:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 604632sec preferred_lft 604632sec

    inet6 fe80::76d4:35ff:fe12:3f67/64 scope link 

       valid_lft forever preferred_lft forever


output of command ping 192.168.1.1



PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.606 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.522 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.565 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.548 ms

^C

--- 192.168.1.1 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 5998ms

rtt min/avg/max/mdev = 0.521/0.562/0.608/0.045 ms


output of command ping 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=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=24.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=22.9 ms

^C

--- 8.8.8.8 ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 9011ms

rtt min/avg/max/mdev = 22.250/23.126/24.826/0.679 ms





networking grub2 system-installation internet







share|improve this question















All of a sudden, the desktop cannot access the internet either wired or wireless. It can see other machines on the local network, can read/write files on other devices, which can read/write files on the affected desktop. Other machines happily cruise c-space, but my desktop remains chained to the dock. I suspect a corrupt file, but can't fix it without internet access. Tried the repair option from the grub launcher without success. Don't like the option of reinstalling from a live CD. Am I missing something?




Output of command sudo lshw -C network



 *-network               

       description: Ethernet interface

       product: Ethernet Connection I217-V

       vendor: Intel Corporation

       physical id: 19

       bus info: pci@0000:00:19.0

       logical name: eth0

       version: 05

       serial: 74:d4:35:12:3f:67

       size: 1Gbit/s

       capacity: 1Gbit/s

       width: 32 bits

       clock: 33MHz

       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.144 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s

       resources: irq:25 memory:f0400000-f041ffff memory:f043d000-f043dfff ioport:f080(size=32)


output of command ip link



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff


output of command ip addr



1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

    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 pfifo_fast state UP group default qlen 1000

    link/ether 74:d4:35:12:3f:67 brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.144/24 brd 192.168.1.255 scope global dynamic eth0

       valid_lft 86230sec preferred_lft 86230sec

    inet6 fd82:76e3:b254:0:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 7032sec preferred_lft 3432sec

    inet6 2605:a000:110e:230c:76d4:35ff:fe12:3f67/64 scope global noprefixroute dynamic 

       valid_lft 604632sec preferred_lft 604632sec

    inet6 fe80::76d4:35ff:fe12:3f67/64 scope link 

       valid_lft forever preferred_lft forever


output of command ping 192.168.1.1



PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.606 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.522 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.565 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.548 ms

^C

--- 192.168.1.1 ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 5998ms

rtt min/avg/max/mdev = 0.521/0.562/0.608/0.045 ms


output of command ping 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=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=24.8 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=23.3 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=22.9 ms

^C

--- 8.8.8.8 ping statistics ---

6 packets transmitted, 6 received, 0% packet loss, time 9011ms

rtt min/avg/max/mdev = 22.250/23.126/24.826/0.679 ms





networking grub2 system-installation internet




networking grub2 system-installation internet






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 at 21:13









guiverc

3,87811522




3,87811522










asked Nov 7 at 2:55









Ted Saker

12




12












  • Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
    – guiverc
    Nov 7 at 3:20










  • Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
    – Ted Saker
    Nov 7 at 13:30










  • Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
    – guiverc
    Nov 7 at 22:33










  • I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
    – Ted Saker
    Nov 8 at 12:16










  • Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
    – guiverc
    Nov 8 at 12:32


















  • Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
    – guiverc
    Nov 7 at 3:20










  • Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
    – Ted Saker
    Nov 7 at 13:30










  • Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
    – guiverc
    Nov 7 at 22:33










  • I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
    – Ted Saker
    Nov 8 at 12:16










  • Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
    – guiverc
    Nov 8 at 12:32
















Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
– guiverc
Nov 7 at 3:20




Welcome to Ask Ubuntu. If it were me I'd stick to basics (and I use commands, so it's where I'd look). Is your networking recognized by system (sudo lshw -C network) though I suspect this is fine. I'd next ip link to display some network info, ip addr to see if IP address has been obtained. If you already know your access point address, I'd ping it, eg. ping 10.10.30.1 (if that address was it), then I'd ping google-dns using address (and not name) ping 8.8.8.8. It maybe these all work (networking is good), but DNS fails, if so ping google.com will fail when 8.8.8.8 works
– guiverc
Nov 7 at 3:20












Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
– Ted Saker
Nov 7 at 13:30




Thanks for the comment, guiverc. I tried your suggestions and everything looked OK except it's still not seeing the net.
– Ted Saker
Nov 7 at 13:30












Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
– guiverc
Nov 7 at 22:33




Were you able to ping your access point? Were you able to ping google via address (8.8.8.8)? If as you say everything looked OK then you are on the internet. I suspected those would work, but when you used a human-name instead of IP address (eg. the google.com) it could fail (as users rely on DNS to convert names to internet addresses) - but if that's okay as you say from comment, you have most likely a problem with your browser. Copying & pasting the responses you have would have provided me more detail, but I cannot help without detail (add info to your question please, not comments)
– guiverc
Nov 7 at 22:33












I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
– Ted Saker
Nov 8 at 12:16




I took screen shots of the output from the commands. I'll try to upload them. Despite everything looking good, three different browsers cannot retrieve anything over the net.
– Ted Saker
Nov 8 at 12:16












Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
– guiverc
Nov 8 at 12:32




Please don't upload photos of text, copy the text to a file, and copy (scp or walk) the file to a working machine & upload the text adding it to your question. Three browsers tells me nothing; it's best to start from the bottom (ie. (1) network connection, (2) can connect to access point, (3) can connect from ap to web, (4..) before you try testing DNS & protocols that use the connections previously tested. Browsers tell you one (or more) part isn't working but not which part. The order I've given tests one piece at a time (and test fails mean something IF prior passed)
– guiverc
Nov 8 at 12:32















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1090668%2fhow-to-restore-internet-connectivity-to-u-16-04-5-desktop%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1090668%2fhow-to-restore-internet-connectivity-to-u-16-04-5-desktop%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

數位音樂下載

Image
數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
Read more

When can things happen in Etherscan, such as the picture below?

Image
2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
Read more

格利澤436b

Image
格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
Read more