Websites taking long to load/timing out

I

ixmike88

Posts: 26   +0
recently websites take long to load and sometimes time out, nothing has really changed in terms of software, and i believe it's a problem for another computer at my house as well, i am connected via ethernet so it's not a wireless hardware issue and my internet connection doesn't drop when the websites time out, and it's not firefox because when i ping via command prompt sometimes the pings time out

i did a traceroute for google and a website i visit regularly, and i noticed that the first trace times out in both occasions, i'm not really familiar with traceroute but i believe the first trace is to the router/modem, however i can ping the router/modem fine and connect to the config via firefox, i have also tried restarting the gateway and the problem still persists

C:\Documents and Settings\Administrator>tracert google.com

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

1 * * * Request timed out.
2 * * 22 ms 99-7-72-3.lightspeed.livnmi.sbcglobal.net [99.7.72.3]
3 30 ms 20 ms 20 ms 75.26.93.210
4 24 ms 20 ms 22 ms 75.26.64.80
5 * 22 ms 21 ms 75.26.64.6
6 20 ms 20 ms 33 ms 151.164.99.200
7 28 ms 27 ms 27 ms 151.164.99.129
8 27 ms 27 ms 27 ms 72.14.218.45
9 28 ms 28 ms 28 ms 209.85.254.130
10 39 ms 39 ms 39 ms 72.14.232.141
11 38 ms 45 ms 41 ms 209.85.241.37
12 51 ms * 46 ms 72.14.239.193
13 40 ms 40 ms 38 ms iw-in-f103.1e100.net [74.125.95.103]

Trace complete.

C:\Documents and Settings\Administrator>tracert nadota.com

Tracing route to nadota.com [174.143.246.215]
over a maximum of 30 hops:

1 * * * Request timed out.
2 22 ms 20 ms 20 ms 99-7-72-3.lightspeed.livnmi.sbcglobal.net [99.7.72.3]
3 20 ms 20 ms 20 ms 75.26.93.210
4 20 ms 20 ms 20 ms 75.26.64.80
5 * * * Request timed out.
6 25 ms 21 ms 22 ms 151.164.99.200
7 27 ms 27 ms 29 ms 151.164.99.129
8 27 ms 30 ms 33 ms xe-11-1-0.edge4.Chicago3.Level3.net [4.68.62.37]
9 29 ms 29 ms 29 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
10 61 ms 58 ms 67 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
11 72 ms 70 ms 72 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
12 64 ms 71 ms 71 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
13 59 ms 59 ms 58 ms ae-3-80.edge2.Dallas3.Level3.net [4.69.145.140]
14 59 ms 60 ms 59 ms RACKSPACE-M.edge2.Dallas3.Level3.net [4.59.36.50]
15 61 ms 61 ms 59 ms vlan907.core7.dfw1.rackspace.net [98.129.84.181]
16 61 ms 59 ms 60 ms 98.129.84.173
17 60 ms 59 ms 60 ms 174-143-246-215.static.slicehost.net [174.143.246.215]

Trace complete.

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254

C:\Documents and Settings\Administrator>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.1.254:
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\Administrator>tracert 192.168.1.254

Tracing route to home [192.168.1.254]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home [192.168.1.254]

Trace complete.


if u need any other information please let me know, thanks
 
your router can be configured to IGNORE PING ... thus timeouts to it are meaningless
 
let's do some simple things first

1) use IPCONFIG /ALL and post your results

2) find your ISP gateway (it's not show in the above)

3)
ping your router by ip address
ping your isp gateway by address
nslookup www.google.com. (note the trailing DOT!)
ping www.google.com (note: missing the dot)​
you should have NO timeouts and you should get the google.com ip-address returned by nslookup.

pls post your findings ...
 
C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : mike-g
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 6C-F0-49-71-B8-0A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : Tuesday, September 14, 2010 1:04:55
PM
Lease Expires . . . . . . . . . . : Wednesday, September 15, 2010 1:04:5
5 PM

C:\Documents and Settings\Administrator>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time=4ms TTL=255
Reply from 192.168.1.254: bytes=32 time=2ms TTL=255
Reply from 192.168.1.254: bytes=32 time=2ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255

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

C:\Documents and Settings\Administrator>nslookup www.google.com.
Server: home
Address: 192.168.1.254

Non-authoritative answer:
Name: www.l.google.com
Addresses: 209.85.225.104, 209.85.225.99, 209.85.225.105, 209.85.225.106
209.85.225.103, 209.85.225.147
Aliases: www.google.com


C:\Documents and Settings\Administrator>ping google.com

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

Reply from 209.85.225.104: bytes=32 time=44ms TTL=50
Reply from 209.85.225.104: bytes=32 time=56ms TTL=50
Reply from 209.85.225.104: bytes=32 time=39ms TTL=52
Reply from 209.85.225.104: bytes=32 time=81ms TTL=50

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

C:\Documents and Settings\Administrator>nslookup google.com
Server: home
Address: 192.168.1.254

Non-authoritative answer:
Name: google.com
Addresses: 74.125.95.104, 74.125.95.106, 74.125.95.99, 74.125.95.147
74.125.95.105, 74.125.95.103

don't know what an isp gateway is, my ip is 99.7.73.137 if it helps define it

block ping is already enabled on my router by default
 
http://checkip.dyndns.org/ will show your public WAN address (ie how your ISP sees you)

your router has a router's LAN address, in your case 192.168.1.254

your system has the LAN address 192.168.1.100

the ISP Gateway is none of the above;
your router config interface will show you the correct ISP gateway.

recall: your system(192.168.1.100)==>to the router(192.168.1.254)==>ISP Gateway address(?)
and that is not the same as your public WAN address.

in a tracert;
the first line is your router(LAN==192.168.1.254)
and the second will be the ISP Gateway :)

2 * * 22 ms 99-7-72-3.lightspeed.livnmi.sbcglobal.net [99.7.72.3]
Click to expand...
the object of all the PING / NSLOOKUP was to prove traffic went to the right places &
that your DNS was able to convert a NAME => IP address

Node Type . . . . . . . . . . . . : Broadcast
Click to expand...

NodeType controls the name resolution request and the values are shown here:
Code: 
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\NetBT\Parameters\NodeType RegDword = 8
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\NetBT\Parameters\NodeType RegDword = 8
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\NodeType RegDword = 8

you will need to reboot to make it effective and then ipconfig /all will show
Node Type . . . . . . . . . . . . : Hybrid

174.143.246.215
Click to expand...
this is the North Amer DotA Syn.
There should be only two reasons you can't access that site
  1. the server is down
  2. that site has been block at your router, parental controls, or your firewall
A blocked site will normally respond as Not Available(404) or sometimes as a Timeout

C:\Documents and Settings\Administrator>tracert google.com
Click to expand...
you're living on the ragged edge ... NEVER access websites with this login.
If any thing attacks you, your system is history!
 
after talking with a tech via phone for a while it was concluded that all of my nat sessions (1024) were being occupied by bit torrent, and bit torrent was shut down and the router was reset the nat session usage went down to 70-100, and when i reopened bit torrent it instantly occupied every remaining session

my global connections is set to 300 for bit torrent, is this the issue? i'm not too familiar with the config of this and any feedback on this would be appreciated
 
You must log in or register to reply here.

Similar threads

S
Ping Issues
Replies
13
Views
3K
DelJo63
D
midian182
HP monitors, laptops, accessories, and more are up to 58% off in the Labor Day Sale
Replies
0
Views
1K
midian182
midian182
elpretentio
Facebook not working in Mexico (ISP is Cablemas)
Replies
0
Views
4K
elpretentio
elpretentio

Latest posts

Back