|
Posted by Bit Twister on June 12, 2005, 1:29 pm
If you were Registered and logged in, you could reply and use other advanced thread options
On Sun, 12 Jun 2005 17:58:54 GMT, Richard Twister wrote:
> Up until this week my Comcast account was chugging along quite nicely.
> Now however it is very erratic with slow downs and time outs (Very
> frustrating when I am trying to tunnel into my work VPN to say the
> least).
>
> From what I have read here it seems to be a DNS server issue since my
> Cable modem has a solid LED for the "Cable" indicator (not blinking)
> and about the only work around is to unplug than plug in both the
> Modem and router. It will work for (maybe) an hour or so, but then it
> seems to revert back.
Seems odd, booting modem/router should not make your DNS problem better.
click up a CMD terminal and do a
ipconfig /all
When you have a outage you could ping your gateway or/and
ping 66.94.234.13 to test net speed/access to yahoo.com
ping yahoo.com to test dns lookup and get speed
> I have called Comcast 4 times this weekend and I was able to glean
> from one of "Tech's" that there was some type of maintenance going on
> around my area (although he gave me no details of what that might have
> been) so I have scheduled a tech to come out here on Tuesday night to
> check things out from the demarc point and beyond.
Did they tell you about the service call if no problem found?
You could try looking at the modem web page at
http://192.168.100.1 to check up/down stream signals
before, during and after an outage.
ping 66.94.234.13 to verify connectivity.
nslookup yahoo.com to verify dns
Note, windows can cache the lookup so the second lookup could work
with dns out.
What you do is lookup different sites you have not been to everytime
google.com, msn.com, yahoo.com, tv/radio stations,....
> I have read that adding a public DNS server entry might help things.
It might, comcast dns lookup time
dig @63.240.76.198 yahoo.com | grep "Query time:"
;; Query time: 136 msec
speakeasy.net dns lookup time
dig @66.93.87.2 yahoo.com | grep "Query time:"
;; Query time: 71 msec
Of course it would need to be the first dns server in your list.
> But does it make any differences which one I use relative to my
> location? I would assume to some extent that the answer would be yes
> (IOW I wouldn't want a DNS server located in Tokyo since I live in the
> Midwest obviously).
You would have to run tracert to each server to see time to server for
that point in time. Route could be slower later in the day. :(
|