[mdlug] Strange Network Issue
R Kannan
rk111810 at gmail.com
Sat Oct 18 18:31:25 EDT 2014
On 10/18/2014 05:26 PM, Carl T. Miller wrote:
> The first thing I would check is the routes on each of
> these hosts. Can you post the output of "route -n"?
>
> c
>
>
> R KANNAN wrote:
>> Hello
>>
>> I wasencountering a strange issue on my desktop (Mythbuntu 12.04) that
>> I do not see on another laptop (Mythbuntu 12.04) on the same network.
>> Both are connecting to the same router albeit differently (wired vs.
>> wired) and using the same primary and secondary DNS. Some of the names
>> are not resolved since yesterday
>>
>> kannan at HP-DVR:~$ nslookup www.nfl.com
>> Server: 127.0.0.1
>> Address: 127.0.0.1#53
>>
>> ** server can't find www.nfl.com: SERVFAIL
>>
>> kannan at OldLaptop:~$ nslookup www.nfl.com
>> Server: 127.0.0.1
>> Address: 127.0.0.1#53
>>
>> Non-authoritative answer:
>> www.nfl.com canonical name = www.nfl.com.edgesuite.net.
>> www.nfl.com.edgesuite.net canonical name = a989.g.akamai.net.
>> a989.g.akamai.net canonical name =
>> user-att-23-119-216-0.a989.g.akamai.net.
>> Name: user-att-23-119-216-0.a989.g.akamai.net
>> Address: 23.77.237.48
>> Name: user-att-23-119-216-0.a989.g.akamai.net
>> Address: 23.77.236.168
>>
>> Then I tried pinging the gateway (my router) from my desktop and it
>> failed.. But I could ping other machines within my network. This
>> explained why I could not go outside of my networ.
>>
>> I wonder what changed. BTW, I installed WireShock on my computer and
>> had to change some file settings to make it work for non-root. I am
>> not sure if that had any effect.
>>
>> Any ideas?
>>
>> Thanks for any help
>>
Found that the wireless in the desktop was working. Though it still was
not able to resolve www.nfl.com. It was getting timed out..
kannan at HP-DVR:~$ nslookup www.nfl.com
;; connection timed out; no servers could be reached
So changed the network cable guessing this is a hardware issue. Now it
seems to be working as well as the wireless. Still cannot resolve
www.nfl.com. But I can access other sites and can browse.
route -n yields..
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
I will keep the new cable and monitor to see if I can narrow this down.
BTW, I had installed Wireshark (not Wireshock) and I don't believe that
has anything to do with this issue.
Thanks
More information about the mdlug
mailing list