mintoreo wrote:Are you implying that the machine I bought 3 years ago for $150 isn't top notch? (I've been waiting for a hardware problem to pop up)
I'm currently using whatever is built into the laptop, but may have a USB wifi device around somewhere. I'll definitely start carrying one around for next time it goes on the fritz. Great suggestion, thanks!
$ inxi -Nn
Network: Card-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965
IF: wlan1 state: up mac: 00:1d:e0:02:f2:15
Card-2: Intel 82566MM Gigabit Network Connection driver: e1000e
IF: eth1 state: up speed: 100 Mbps duplex: full mac: 00:1c:25:18:ce:32
JeremyB wrote:Definitely try a USB for wifi, the 4965 had issues in windows
mintoreo wrote:JeremyB wrote:Definitely try a USB for wifi, the 4965 had issues in windows
Good to know, I'll get on it. Would that also contribute to the issue with the wired connection? And is installing a new card worthwhile for a novice to take on?
Thanks for the input!
mintoreo wrote:WOOOOO!! FIGURED IT OUT!!!!
I mean, I don't really understand what I did, but it's fixed and that's the important part.
Following the advice found here: http://ubuntuforums.org/showthread.php? ... 0bb2adc530
I had all the same issues as the poster, and used "sudo dpkg-reconfigure resolvconf" to restore a symbolic link that had somehow gone missing and a reboot. Both wired and wireless connections are working again. I'm running victory laps.
Hopefully this helps someone else too, and thanks all who lended ideas!
You are running NetworkManager. Resolvconf writes resolv.conf based on what NetworkManager tells it.
NetworkManager usually obtains configuration information via DHCP. However, in your case NM hasn't obtained a DNS nameserver address. (See below.) So your machine does not know where to send DNS queries.
Earlier your /etc/resolv.conf did contain an address, 192.168.2.1.
It seems that your modemrouter is not currently providing an address for the DNS nameserver.
Check your modemrouter configuration.
If your laptop works then it's possibly because it has a valid *static* configuration.
Installed brand new router, deleted previous settings in Network Manager.
Reset and BINGO... off to the races.