Ubuntu recognises and connects to wifi and ethernet, but says there's no internet [on hold]
This has me stumped.
I have my desktop on a CABLE connected to my laptop, which is bridging my internet to the desktop. I previously used a WiFi adapter, but it stopped working during the summer. I have internet, my laptop and everyone else in the house confirm this, but the only time I can load a site is when I tether my phone and use my data. The second I try to tether my WiFi with my phone, it refuses. EVERY TIME, no matter what version of Ubuntu I'm testing, Firefox says that the server can't be found. I'm still using 14.04, but I'm also testing with 14.04 and 16.04 live disks. I have never seen something like this.
UPDATE: It seems that I can connect to my external hdd downstairs, so internal connections work, but still no internet.
UPDATE: Results of ip route
default via 192.168.1.1 dev eth1 proto static
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.144 metric 1
14.04 16.04 networking internet
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by user68186, karel, Eric Carvalho, Charles Green, Zanna 19 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user68186, karel, Eric Carvalho, Charles Green, Zanna
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
This has me stumped.
I have my desktop on a CABLE connected to my laptop, which is bridging my internet to the desktop. I previously used a WiFi adapter, but it stopped working during the summer. I have internet, my laptop and everyone else in the house confirm this, but the only time I can load a site is when I tether my phone and use my data. The second I try to tether my WiFi with my phone, it refuses. EVERY TIME, no matter what version of Ubuntu I'm testing, Firefox says that the server can't be found. I'm still using 14.04, but I'm also testing with 14.04 and 16.04 live disks. I have never seen something like this.
UPDATE: It seems that I can connect to my external hdd downstairs, so internal connections work, but still no internet.
UPDATE: Results of ip route
default via 192.168.1.1 dev eth1 proto static
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.144 metric 1
14.04 16.04 networking internet
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by user68186, karel, Eric Carvalho, Charles Green, Zanna 19 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user68186, karel, Eric Carvalho, Charles Green, Zanna
If this question can be reworded to fit the rules in the help center, please edit the question.
2
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you canping 8.8.8.8(which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg.ping -c 1 dns.google.com(where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start withpingor ICMP echo requests to work out your problem.ip routecould also be useful.
– guiverc
Dec 27 at 22:11
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
A quick fix is to just to addnameserver 8.8.8.8to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…
– guiverc
Dec 28 at 11:51
add a comment |
This has me stumped.
I have my desktop on a CABLE connected to my laptop, which is bridging my internet to the desktop. I previously used a WiFi adapter, but it stopped working during the summer. I have internet, my laptop and everyone else in the house confirm this, but the only time I can load a site is when I tether my phone and use my data. The second I try to tether my WiFi with my phone, it refuses. EVERY TIME, no matter what version of Ubuntu I'm testing, Firefox says that the server can't be found. I'm still using 14.04, but I'm also testing with 14.04 and 16.04 live disks. I have never seen something like this.
UPDATE: It seems that I can connect to my external hdd downstairs, so internal connections work, but still no internet.
UPDATE: Results of ip route
default via 192.168.1.1 dev eth1 proto static
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.144 metric 1
14.04 16.04 networking internet
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This has me stumped.
I have my desktop on a CABLE connected to my laptop, which is bridging my internet to the desktop. I previously used a WiFi adapter, but it stopped working during the summer. I have internet, my laptop and everyone else in the house confirm this, but the only time I can load a site is when I tether my phone and use my data. The second I try to tether my WiFi with my phone, it refuses. EVERY TIME, no matter what version of Ubuntu I'm testing, Firefox says that the server can't be found. I'm still using 14.04, but I'm also testing with 14.04 and 16.04 live disks. I have never seen something like this.
UPDATE: It seems that I can connect to my external hdd downstairs, so internal connections work, but still no internet.
UPDATE: Results of ip route
default via 192.168.1.1 dev eth1 proto static
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.144 metric 1
14.04 16.04 networking internet
14.04 16.04 networking internet
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Dec 27 at 22:16
asked Dec 27 at 21:27
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 27 at 21:27
VideoWelder
11
asked Dec 27 at 21:27
VideoWelder
11
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
put on hold as off-topic by user68186, karel, Eric Carvalho, Charles Green, Zanna 19 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user68186, karel, Eric Carvalho, Charles Green, Zanna
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by user68186, karel, Eric Carvalho, Charles Green, Zanna 19 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – user68186, karel, Eric Carvalho, Charles Green, Zanna
If this question can be reworded to fit the rules in the help center, please edit the question.
2
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you canping 8.8.8.8(which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg.ping -c 1 dns.google.com(where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start withpingor ICMP echo requests to work out your problem.ip routecould also be useful.
– guiverc
Dec 27 at 22:11
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
A quick fix is to just to addnameserver 8.8.8.8to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…
– guiverc
Dec 28 at 11:51
add a comment |
2
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you canping 8.8.8.8(which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg.ping -c 1 dns.google.com(where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start withpingor ICMP echo requests to work out your problem.ip routecould also be useful.
– guiverc
Dec 27 at 22:11
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
A quick fix is to just to addnameserver 8.8.8.8to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…
– guiverc
Dec 28 at 11:51
2
2
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you can
ping 8.8.8.8 (which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg. ping -c 1 dns.google.com (where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start with ping or ICMP echo requests to work out your problem. ip route could also be useful.– guiverc
Dec 27 at 22:11
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you can
ping 8.8.8.8 (which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg. ping -c 1 dns.google.com (where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start with ping or ICMP echo requests to work out your problem. ip route could also be useful.– guiverc
Dec 27 at 22:11
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
A quick fix is to just to add
nameserver 8.8.8.8 to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…– guiverc
Dec 28 at 11:51
A quick fix is to just to add
nameserver 8.8.8.8 to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…– guiverc
Dec 28 at 11:51
add a comment |
1 Answer
1
active
oldest
votes
Seems to have been resolved now. I haven't made changes, but it now works. Must have been some sort of limit with the network itself, but all's fine now.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Seems to have been resolved now. I haven't made changes, but it now works. Must have been some sort of limit with the network itself, but all's fine now.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
add a comment |
Seems to have been resolved now. I haven't made changes, but it now works. Must have been some sort of limit with the network itself, but all's fine now.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
add a comment |
Seems to have been resolved now. I haven't made changes, but it now works. Must have been some sort of limit with the network itself, but all's fine now.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Seems to have been resolved now. I haven't made changes, but it now works. Must have been some sort of limit with the network itself, but all's fine now.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
VideoWelder
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
VideoWelder
11
answered 2 days ago
VideoWelder
11
11
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
VideoWelder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
add a comment |
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
As the problem went away on its own and cannot be reproduced, please delete the question and the answer.
– user68186
2 days ago
add a comment |
2
Welcome to Ask Ubuntu. To confirm if the machine can access the internet you can
ping 8.8.8.8(which is the address for dns.google.com). If you get replies, your routing is correct and you access the internet fine. My suspicion is you will fail if you ping using a human-name, eg.ping -c 1 dns.google.com(where DNS is your issue; what converts human names to the IP addresses used online). Other reasons could be your network setup; but I'd start withpingor ICMP echo requests to work out your problem.ip routecould also be useful.– guiverc
Dec 27 at 22:11
Yep, pings fine, but Firefox isn't loading anything still. What's weird is that it worked a couple of minutes ago, but it stopped again.
– VideoWelder
Dec 27 at 22:14
A quick fix is to just to add
nameserver 8.8.8.8to your /etc/resolv.conf file but that file is re-created on reboot or certain system functions so is temporary (/etc/resolvconf/resolv.conf.d/head can allow it to become permanent though if you use NetworkManager and prefer gui I'd just add nameservers there). DNS can be mucked up by VPN use as it must alter the DNS settings to be private and some vpn scripts fail to correctly restore DNS afterwards as to cause (guess). Have a look at the following askubuntu.com/questions/346838/…– guiverc
Dec 28 at 11:51