Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: 1701E on January 18, 2011, 11:32:13 PM

Title: Internet dieing
Post by: 1701E on January 18, 2011, 11:32:13 PM
Hopefully someone can see an issue or think of something I haven't.  My internet, HTC DSL, dies randomly during the day,  We have gotten a new Modem and put it on a UPS Battery backup and it still happens every few hours.

A normal Tracert to Google looks like:

C:\Users\Xcelsior>tracert www.google.com

Tracing route to www.l.google.com [72.14.204.103]
over a maximum of 30 hops:

  1    <1 ms     3 ms     1 ms  192.168.1.1
  2    43 ms    43 ms    43 ms  ip-216-163-109-1.htcnet.org [216.163.109.1]
  3    70 ms    66 ms    65 ms  12.90.182.93
  4    87 ms    90 ms    90 ms  tbr1.wswdc.ip.att.net [12.122.113.34]
  5    71 ms    90 ms   143 ms  gar8.wswdc.ip.att.net [12.122.113.17]
  6    81 ms    75 ms    74 ms  wswdc02jt.ip.att.net [12.122.88.173]
  7    78 ms    80 ms    70 ms  xe-6-1-0.edge1.Washington4.level3.net [4.68.62.29]
  8    75 ms    82 ms    87 ms  vlan52.ebr2.Washington12.Leve l3.net [4.69.146.222]
  9    78 ms    71 ms    73 ms  ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
 10    73 ms    79 ms    68 ms  ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
 11    78 ms    65 ms    83 ms  ae-13-60.car3.Washington1.Level3.net [4.69.149.5]
 12   139 ms    73 ms    64 ms  GOOGLE-INC.car3.Washington1.Level3.net [4.79.168.6]
 13    65 ms    73 ms    64 ms  216.239.48.108
 14    65 ms    67 ms    92 ms  66.249.94.46
 15    67 ms    72 ms    77 ms  iad04s01-in-f103.1e100.net [72.14.204.103]

Trace complete.


When it dies all I get is:

C:\Users\Xcelsior>tracert www.google.com
Unable to resolve target system name www.google.com.



Is it because of level3? (Think that's the one I heard is bad around here)
I just downloaded the Free Pingplotter I can run when it dies again in case that shows anymore information.

 :salute
Title: Re: Internet dieing
Post by: Skuzzy on January 19, 2011, 09:02:58 AM
Unable to resolve a name to an IP address is due to the name server (DNS) you are using not being able to answer the question.  It could be due to a failure of the local DNS being able to contact Google's DNS server for resolution.

Yes, Level3 could be the culprit (and it would not surprise me at all).