Tech Support Forum banner
Status
Not open for further replies.
1 - 20 of 20 Posts

· Registered
Joined
·
18 Posts
Discussion Starter · #1 ·
i'm currently connected to the internet via a wirelessadapter via a wireless router via comcast.. the computer with the router/modem is working just fine but my internet is very limited and slow... even though it say my connection is good very good.. i was able to go to this website.. but there are several that i cannot go to.. they wont load. and even this one is working at a slow pace.
i no it's not a firewall problem.. cause i tried disabling them.. but it did nothing... and i just recently had a bunch of malware removed and i'm thinking maybe that has something to do with it?
help!
 

· Registered
Joined
·
18 Posts
Discussion Starter · #3 ·
i use netgear for both my router and adapter.. i'm not sure of the exact model. they are both fairly new.. under a year old. and yea they are left on all the time
 

· Global Moderator
Electronic Design
Joined
·
52,687 Posts
Register at DSLReports and run their Line Quality Tests. It's best to run this test with a direct wired connection to eliminate any wireless issues from the results. It's useful many times to run this test several times, and we'd like to see each of the results. Post the results link from the top of the test display page for each test run here.

The link to post is near the top of the page and looks like:

If you wish to post this result to a forum, please copy/paste this URL
http://www.dslreports.com/linequality/nil/2357195 <- sample only, yours will obviously be different!
and your IP will be disguised.

Copy/paste that link here.

Note: You will have to enable PING (ICMP) request response either in your router (if you have one), or in your computer's firewall for direct modem connections. This is very important to get the most important part of the test to run.
 

· Registered
Joined
·
264 Posts
go to command prompt (Start>Accessories>Command Prompt) and type in the following:

PING localhost

[hit the enter key]

PING google.com

[hit the enter key again]

PING godaddy.com




Paste the results in a new post



THEN


type in

TRACERT yahoo.com

[hit the enter key]

TRACERT google.com

[hit the enter key again]

TRACERT godaddy.com

[hit the enter key]

paste the results in a new post along with the Ping posts.


You should have results similar to these (if not, then it narrows down the problem):

Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Ryan>PING privateclientlaw.com

Pinging privateclientlaw.com [68.178.232.100] with 32 bytes of data:
Reply from 68.178.232.100: bytes=32 time=50ms TTL=113
Reply from 68.178.232.100: bytes=32 time=50ms TTL=113
Reply from 68.178.232.100: bytes=32 time=51ms TTL=113
Reply from 68.178.232.100: bytes=32 time=49ms TTL=113

Ping statistics for 68.178.232.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 51ms, Average = 50ms

C:\Users\Ryan>TRACERT privateclientlaw.com

Tracing route to privateclientlaw.com [68.178.232.100]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        9 ms    12 ms  GE-1-1-ur01.bellevue.wa.seattle.comcast.net [68.
86.98.17]
  4    10 ms     *       10 ms  te-9-3-ur02.bellevue.wa.seattle.comcast.net [68.
86.96.70]
  5    10 ms    11 ms    13 ms  te-8-3-ar02.seattle.wa.seattle.comcast.net [68.8
6.96.73]
  6    12 ms    13 ms    12 ms  te-9-1-ar02.seattle.wa.seattle.comcast.net [68.8
6.90.210]
  7  1768 ms    13 ms    14 ms  COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.10
6]
  8    17 ms    11 ms    14 ms  te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
  9    11 ms    17 ms    17 ms  ae-32-54.ebr2.Seattle1.Level3.net [4.68.105.126]

 10    18 ms    17 ms    21 ms  ae-1-100.ebr1.Seattle1.Level3.net [4.69.132.17]

 11    32 ms    35 ms    36 ms  ae-3.ebr1.SanJose1.Level3.net [4.69.132.49]
 12    29 ms    31 ms    35 ms  ae-61-61.csw1.SanJose1.Level3.net [4.69.134.194]

 13    42 ms    35 ms    36 ms  ae-63-63.ebr3.SanJose1.Level3.net [4.69.134.225]

 14    41 ms    39 ms    49 ms  ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
 15    54 ms    37 ms    37 ms  ae-93-93.csw4.LosAngeles1.Level3.net [4.69.137.4
6]
 16    39 ms    46 ms    50 ms  ae-92-92.ebr2.LosAngeles1.Level3.net [4.69.137.2
9]
 17    46 ms    47 ms    47 ms  ae-4-4.car2.Phoenix1.Level3.net [4.69.133.37]
 18    48 ms    49 ms    47 ms  ae-11-11.car1.Phoenix1.Level3.net [4.69.133.33]

 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24    49 ms    56 ms    54 ms  ip-64-202-160-153.secureserver.net [64.202.160.1
53]
 25    49 ms    49 ms    49 ms  parkwebwin-v01.prod.mesa1.secureserver.net [68.1
78.232.100]
 26    52 ms    56 ms    49 ms  parkwebwin-v01.prod.mesa1.secureserver.net [68.1
78.232.100]

Trace complete.

C:\Users\Ryan>
 

· Registered
Joined
·
18 Posts
Discussion Starter · #9 ·
here are the first ping results


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jennifer Peterson>PING localhost

Pinging DJFQ5R61 [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Jennifer Peterson>PING google.com

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=91ms TTL=235
Reply from 72.14.207.99: bytes=32 time=90ms TTL=235
Reply from 72.14.207.99: bytes=32 time=93ms TTL=235
Reply from 72.14.207.99: bytes=32 time=90ms TTL=235

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 93ms, Average = 91ms

C:\Documents and Settings\Jennifer Peterson>PING godaddy.com

Pinging godaddy.com [208.109.132.201] with 32 bytes of data:

Reply from 208.109.132.201: bytes=32 time=52ms TTL=108
Reply from 208.109.132.201: bytes=32 time=686ms TTL=108
Reply from 208.109.132.201: bytes=32 time=57ms TTL=108
Reply from 208.109.132.201: bytes=32 time=52ms TTL=108

Ping statistics for 208.109.132.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 686ms, Average = 211ms

C:\Documents and Settings\Jennifer Peterson>
 

· Registered
Joined
·
18 Posts
Discussion Starter · #10 ·
and here's the second set
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jennifer Peterson>TRACERT yahoo.com

Tracing route to yahoo.com [206.190.60.37]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 22 ms 11 ms * ge-3-6-ur01.everett.wa.seattle.comcast.net [68.8
6.177.9]
4 11 ms 11 ms * te-9-3-ur02.everett.wa.seattle.comcast.net [68.8
6.96.78]
5 11 ms 9 ms 12 ms te-8-4-ur05.everett.wa.seattle.comcast.net [68.8
6.96.218]
6 9 ms * * te-8-3-ur06.everett.wa.seattle.comcast.net [68.8
6.96.222]
7 11 ms * 10 ms te-7-1-ur07.everett.wa.seattle.comcast.net [68.8
6.96.226]
8 11 ms 11 ms * te-7-2-ur08.everett.wa.seattle.comcast.net [68.8
6.96.230]
9 12 ms 13 ms 9 ms te-7-3-ar02.seattle.wa.seattle.comcast.net [68.8
6.96.82]
10 13 ms 11 ms 11 ms te-9-1-ar02.seattle.wa.seattle.comcast.net [68.8
6.90.210]
11 11 ms 11 ms 11 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.11
0]
12 13 ms 11 ms 11 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
13 17 ms 18 ms 17 ms ae-31-53.ebr1.Seattle1.Level3.net [4.68.105.94]

14 11 ms 16 ms 17 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

15 43 ms 37 ms 51 ms ae-2.ebr2.Denver1.Level3.net [4.69.132.54]
16 68 ms 76 ms 67 ms ae-3.ebr3.Chicago1.Level3.net [4.69.132.62]
17 97 ms 93 ms 104 ms ae-2.ebr2.Washington1.Level3.net [4.69.132.70]
18 102 ms 94 ms 103 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
19 95 ms 95 ms 95 ms ae-11-69.car1.Washington1.Level3.net [4.68.17.3]

20 98 ms 94 ms 94 ms 4.79.228.2
21 95 ms 95 ms 95 ms ae2-p140.msr1.re1.yahoo.com [216.115.108.57]
22 98 ms 94 ms 95 ms ge-9-3.bas-a1.re4.yahoo.com [216.39.49.3]
23 94 ms 95 ms 93 ms w2.rc.vip.re4.yahoo.com [206.190.60.37]

Trace complete.

C:\Documents and Settings\Jennifer Peterson>TRACERT

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

C:\Documents and Settings\Jennifer Peterson>TRACERT google.com

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 15 ms 20 ms * ge-3-6-ur01.everett.wa.seattle.comcast.net [68.8
6.177.9]
4 31 ms 15 ms * te-9-3-ur02.everett.wa.seattle.comcast.net [68.8
6.96.78]
5 11 ms 13 ms * te-8-4-ur05.everett.wa.seattle.comcast.net [68.8
6.96.218]
6 9 ms 12 ms * te-8-3-ur06.everett.wa.seattle.comcast.net [68.8
6.96.222]
7 11 ms * 10 ms te-7-1-ur07.everett.wa.seattle.comcast.net [68.8
6.96.226]
8 9 ms 11 ms * te-7-2-ur08.everett.wa.seattle.comcast.net [68.8
6.96.230]
9 11 ms 12 ms 10 ms te-7-3-ar02.seattle.wa.seattle.comcast.net [68.8
6.96.82]
10 12 ms 10 ms 11 ms te-9-1-ar02.seattle.wa.seattle.comcast.net [68.8
6.90.210]
11 11 ms 11 ms 12 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.11
0]
12 165 ms 13 ms 238 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
13 68 ms 56 ms 28 ms ae-2-54.mp2.Seattle1.Level3.net [4.68.105.97]
14 85 ms 85 ms 82 ms as-1-0.bbr1.Atlanta1.Level3.net [209.247.9.101]

15 82 ms 83 ms 83 ms ae-11-51.car1.Atlanta1.Level3.net [4.68.103.2]
16 82 ms 85 ms 97 ms GOOGLE-INC.car1.Atlanta1.Level3.net [4.78.209.19
4]
17 86 ms 83 ms 83 ms 72.14.239.21
18 87 ms 90 ms 89 ms 216.239.43.249
19 85 ms 101 ms 90 ms jc-in-f99.google.com [64.233.187.99]

Trace complete.

C:\Documents and Settings\Jennifer Peterson>TRACERT godaddy.com

Tracing route to godaddy.com [208.109.132.201]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms * 11 ms ge-3-6-ur01.everett.wa.seattle.comcast.net [68.8
6.177.9]
4 9 ms 9 ms * te-9-3-ur02.everett.wa.seattle.comcast.net [68.8
6.96.78]
5 11 ms 11 ms 11 ms te-8-4-ur05.everett.wa.seattle.comcast.net [68.8
6.96.218]
6 10 ms 11 ms 9 ms te-8-3-ur06.everett.wa.seattle.comcast.net [68.8
6.96.222]
7 10 ms * 12 ms te-7-1-ur07.everett.wa.seattle.comcast.net [68.8
6.96.226]
8 10 ms 10 ms * te-7-2-ur08.everett.wa.seattle.comcast.net [68.8
6.96.230]
9 10 ms 11 ms 12 ms te-7-3-ar02.seattle.wa.seattle.comcast.net [68.8
6.96.82]
10 11 ms 10 ms 11 ms te-9-1-ar02.seattle.wa.seattle.comcast.net [68.8
6.90.210]
11 11 ms 13 ms 14 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.11
0]
12 10 ms 11 ms 11 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
13 13 ms 13 ms 11 ms ge-1-0-0-55.gar1.Seattle1.Level3.net [4.68.105.1
37]
14 11 ms 11 ms 10 ms att-level3-oc48.Seattle1.Level3.net [4.68.127.11
0]
15 77 ms 76 ms 76 ms 12.127.6.62
16 76 ms 75 ms 76 ms cr2.st6wa.ip.att.net [12.122.23.229]
17 80 ms 80 ms 80 ms cr1.sffca.ip.att.net [12.122.28.33]
18 80 ms 76 ms 78 ms cr1.la2ca.ip.att.net [12.122.3.122]
19 76 ms 79 ms 76 ms cr2.phmaz.ip.att.net [12.122.31.190]
20 77 ms 78 ms 78 ms tbr2.phmaz.ip.att.net [12.122.22.206]
21 77 ms 77 ms 75 ms 12.122.108.65
22 80 ms 77 ms 78 ms 12.122.255.106
23 76 ms 76 ms 77 ms mdf001c7613r0003-gig-10-1.phx1.attens.net [63.24
1.130.170]
24 * * * Request timed out.
25 * * * Request timed out.
26 52 ms 54 ms 52 ms ip-64-202-160-153.secureserver.net [64.202.160.1
53]
27 56 ms 53 ms 59 ms corpweb-v101.prod.mesa1.secureserver.net [208.10
9.132.201]
28 54 ms 54 ms 52 ms corpweb-v101.prod.mesa1.secureserver.net [208.10
9.132.201]

Trace complete.

C:\Documents and Settings\Jennifer Peterson>
 

· Registered
Joined
·
264 Posts
it seems that you have internet access, as you are getting results from PINGs and TRACERTs. Try typing in command prompt

PING [a website you cannot access]

and TRACET [the same website you cannot access]


so instead of PING google.com PING the website you cannot access. paste the results.
 

· Registered
Joined
·
18 Posts
Discussion Starter · #12 ·
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jennifer Peterson>PING myspace.com

Pinging myspace.com [216.178.38.116] with 32 bytes of data:

Reply from 216.178.38.116: bytes=32 time=36ms TTL=235
Reply from 216.178.38.116: bytes=32 time=37ms TTL=235
Reply from 216.178.38.116: bytes=32 time=36ms TTL=235
Reply from 216.178.38.116: bytes=32 time=38ms TTL=235

Ping statistics for 216.178.38.116:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 38ms, Average = 36ms

C:\Documents and Settings\Jennifer Peterson>TRACET myspace.com
'TRACET' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Jennifer Peterson>TRACET myspace.com
'TRACET' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Jennifer Peterson>
 

· Registered
Joined
·
264 Posts
OK, well it looks like command prompt can access myspace, which means it has to do with the computer. by the way, TRACET was a typo, i meant TRACERT. but the PING worked, so i dont need the tracert. It seems to have a perfect connection. Have you tried a different internet browser, eg firefox? also, can other computers on the local network see the laptop when it is connected?
 

· Registered
Joined
·
264 Posts
How old is your PC, and what manufacturer is it?
I had a malware issue that wasn't going away, so i had to do a recovery on my computer,

but before you try a recovery, try hooking up your computer via ethernet cord to the router, and see if you can access the sites you normally can't through the ethernet.
 
1 - 20 of 20 Posts
Status
Not open for further replies.
Top