Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Monster Lag Spikes


  • Please log in to reply
6 replies to this topic

#1 d0z3r

d0z3r

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:30 PM

Posted 16 November 2010 - 01:09 PM

Hello, I just switched my ISP from Qwest to Comcast and needed to return the router I was renting from them. So I went out and bought a new linksys e1000 router and hooked it up to the modem when I got home. I followed all installation steps correctly and it worked fine for about two days. All of the sudden my laptop started getting laggy in firefox and other programs that connect to the internet. The first thing I did was opened up cmd and did a tracert to www.google.com and the speeds were fine except every 5-10 seconds it would say * * * REQUEST TIMED OUT. So I went to my other two desktops and did the same thing. The results were showing the same thing just a lot less severe. I turned the desktops off and connected my laptop directly to the modem via ethernet and the problem stopped so I knew it must be the router. I took it back and returned it and got the same one because I have never had any problems with linksys. After installation I attempted to connect but my laptop would not receive an IP address and the other machines were fine. I released and renewed the IP address and still nothing. After I restarted my computer, it worked for some reason. I scanned all three computers with avg, Malware Bytes, and Spybot which I do regularly and came up with nothing. I also talked to multiple support people which of course they gave me obvious answers that didn't help at all. I don't know much about networking, I'm more of a hardware guy so I need some help on this one.
Customer: I'm running Windows '98
Tech: Yes.
Customer: My computer isn't working now.
Tech: Yes, you said that.

BC AdBot (Login to Remove)

 


#2 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:05:30 PM

Posted 16 November 2010 - 10:24 PM

Can you post the traceroute to google, and the results of ping'ing Google 20 times? Comcast is one of those ISPs that if you get "Request Timed Out" during the traceroute (while it's on their network) it doesn't really represent a problem.

To do a traceroute:
Start -> run (smart search in Vista/7) -> type cmd and press enter.
In the black box that appears type
tracert www.google.com

To do a ping:
Start -> run (smart search in Vista/7) -> type cmd and press enter.
In the black box that appears type
ping www.google.com -n 20


Right click -> mark -> highlight everything thats in both windows, press enter, and post it in your next reply.

#3 d0z3r

d0z3r
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:30 PM

Posted 16 November 2010 - 10:51 PM

Below are the results
1 2 ms <1 ms <1 ms LINKSYS [192.168.1.1]
2 * * * Request timed out.
3 11 ms 10 ms 8 ms ge-1-23-ur02.pimaco.az.pima.comcast.net [68.86.2
01.53]
4 9 ms 10 ms 11 ms te-8-1-ar02.pimaco.az.pima.comcast.net [68.87.17
2.5]
5 30 ms 22 ms 25 ms te-1-2-0-4-cr01.losangeles.ca.ibone.comcast.net
[68.86.91.37]
6 68 ms 58 ms 55 ms pos-0-10-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.87.38]
7 * * * Request timed out.
8 * * 64 ms 75.149.231.70
9 * * * Request timed out.
10 80 ms 78 ms 91 ms 216.239.47.121
11 * * * Request timed out.
12 82 ms 88 ms 91 ms 209.85.241.211
13 * * 86 ms 209.85.240.228
14 105 ms 82 ms 84 ms 64.233.174.123
15 107 ms 85 ms 83 ms 216.239.49.246
16 86 ms 88 ms 83 ms px-in-f103.1e100.net [74.125.155.103]

C:\Users\Daniel Baird>ping www.google.com -n 20

Pinging www.l.google.com [74.125.224.18] with 32 bytes of data:
Reply from 74.125.224.18: bytes=32 time=72ms TTL=54
Reply from 74.125.224.18: bytes=32 time=71ms TTL=54
Reply from 74.125.224.18: bytes=32 time=70ms TTL=54
Reply from 74.125.224.18: bytes=32 time=73ms TTL=54
Reply from 74.125.224.18: bytes=32 time=70ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.224.18: bytes=32 time=110ms TTL=54
Reply from 74.125.224.18: bytes=32 time=96ms TTL=54
Reply from 74.125.224.18: bytes=32 time=118ms TTL=54
Reply from 74.125.224.18: bytes=32 time=136ms TTL=54
Request timed out.
Request timed out.
Reply from 74.125.224.18: bytes=32 time=68ms TTL=54
Reply from 74.125.224.18: bytes=32 time=88ms TTL=54
Reply from 74.125.224.18: bytes=32 time=71ms TTL=54
Reply from 74.125.224.18: bytes=32 time=68ms TTL=54
Reply from 74.125.224.18: bytes=32 time=70ms TTL=54
Reply from 74.125.224.18: bytes=32 time=80ms TTL=54

Ping statistics for 74.125.224.18:
Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 136ms, Average = 84ms
Customer: I'm running Windows '98
Tech: Yes.
Customer: My computer isn't working now.
Tech: Yes, you said that.

#4 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:05:30 PM

Posted 17 November 2010 - 12:24 AM

Ok, traceroute/ping shows a problem. Not sure if it's happening inside of the Comcast network, or outside of their control.

Can you try ping'ing this IP: 68.86.87.38 ?

Same thing as before, 20 times.
ping 68.86.87.38 -n 20

Post back the results.

If that returns ok, then its most likely something down the road that you can't fix.

#5 d0z3r

d0z3r
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:30 PM

Posted 17 November 2010 - 09:40 AM

Ok, well I pinged it and everything was perfect so I tried the traceroute again to make sure it was still acting up but it stopped...temporarily...which it always does at some point during the day for an hour or two <_<
Customer: I'm running Windows '98
Tech: Yes.
Customer: My computer isn't working now.
Tech: Yes, you said that.

#6 NpaMA

NpaMA

  • Members
  • 635 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Memphis, TN
  • Local time:05:30 PM

Posted 18 November 2010 - 01:14 AM

Just post back if it starts happening again. The last thing I asked you to ping is the first thing outside of the Comcast network. So if it responds correctly, it's basically outside of what Comcast (or you) can do. Problems "down the road" will happen, but normally don't last for long. If it comes back/continues you could call Comcast support but anyone outside of Level 3+ support will have no idea what you mean.

#7 d0z3r

d0z3r
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:30 PM

Posted 18 November 2010 - 10:13 AM

I actually think I fixed it. I think I was on the same wireless channel as one of my neighbors that has a stronger signal. I changed the channel and so far it has been working ok. Thank you for the help though.

Edited by d0z3r, 18 November 2010 - 10:13 AM.

Customer: I'm running Windows '98
Tech: Yes.
Customer: My computer isn't working now.
Tech: Yes, you said that.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users