My machine is an AMD 6 core 64bit system. 8 GB RAM, 1 TB HD. I can connect to my local netowrk, ping network resources and such, however, I can't connect to the internet. I have a manual IPv4 address and have configured DNS to 207.69.188.185. That is the same as other machines on my network, and they work fine.

The other machines on my network run LinuxMint 17.1

Anyone have any ideas?

Thanks.

Do you have default gateway set? How did you set the DNS, by putting it in resolv.conf?

If you can access your router via browser interface, try checking out the settings it has acquired from the ISP and copying those. Like subnet gateway and all that rot.

I'm not sure if this is the right video, but one of the youtube vids about setting a static ip in Ubuntu was helpful to me:
https://www.youtube.com/watch?v=o9fJWDoX4nE

It might also be useful for Mint with a little imagaination.

OK. To the two helpful people above, I manually set the IP address throught the GUI to 192.168.0.57, netmask of 255.255.255.0 with a gateway of 192.168.0.1, DNS to 207.69.188.185 PRIOR to my posting my issue.

To repeat, I CAN get to my LAN resources. Since my other systems are within the same LAN and using the same gateway/router with the sme IP address for it, and I can get those resources on a wrie that works for other sytems (laptops I've connected to make sure the wire works properly in all cases) there is something else in play.

For some reason, while I CAN get to my LAN on this box, I cannot get to the Internet.

Another complication, I also cannot display the localhost, even though the localhost is clearly defined in the /etc/hosts file.

So, I'd appreciate other thoughts.

Oh, I also ran route -n on the box in question and one of the working systems. Here are the results of that command on both:

New box
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.16.0.1 0.0.0.0 UG 100 0 0 enp3s0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 enp3s0
192.16.0.1 0.0.0.0 255.255.255.255 UH 100 0 0 enp3s0
192.168.0.0 0.0.0.0 255.255.255.0 U 100 0 0 enp3s0

LinuxMint (working in all phases) box
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0


The biggest difference between the two is the extra two lines (lines 2 and 3) in the rssponse one new box and the other difference is in the metric.

I have no idea why they would make a diffeence, but maybe they do.

Mark

Sadly, I'm not a very advanced network troubleshooter. I searched a bit and found a pretty lengthy troubleshooting post on the linux mint forums that might have some helpful techniques.

Am I correct in thinking that you want a static IP address of 196.168.0.57 or would a dynamically-allocated address be OK? I would point out that every machine on your LAN needs a unique local ip address -- make sure no other machine is trying to use that exact same ip address. Also, have you tried letting your router assign this mint box an IP address via DHCP? I've had problems on my LAN where devices somehow try to claim the same IP and behavior is unpredictable and weird.

Also, would you say that everything on the LAN is behaving fine, you just can't get to the internet? Can other devices besides this mint box connect just fine to the internet or do they also have trouble? Are you connecting with an ethernet cable or wirelessly?

You do see that it says .16 and NOT .168 in there, right?

Also, enp3s0 is a weird-looking ethernet interface name.

enp3s0 is the result of the new (un)predictable naming convention. It gets real funny with USB wireless adapters, every time you happen to plug it into a different USB port it gets a different name.

OK. I've resolved the issue. One keen eyed person notedd the gateway address was wrong. It shows as 192.16.0.1 when it should be 192.168.0.1.

I fixed that and the connection to the internet worked. I just needed a second, unjaundiced, pair of eyes to see it and tell me.

I agree with the person about the new naming. I would prefer the old naming conventions of ethx and wifi. But, I didn't make the change and it's not likely the people who did are going back to it.

Thanks for all the help.

Mark

You can have old names back, just add net.ifnames=0 to your kernel command line and your eth and wlan will be back.