Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

internet to slow

Status
Not open for further replies.

JOSROS

Technical User
Apr 18, 2004
22
CA
Hi,

The internet was good until 2 weeks ago,

little bit of information,

we have a gateway connected to back office then we have another network connected to our switchbox.
The speed was good suddenly slow down, when i run tracert to google this are the results:


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

C:\Documents and Settings\cn072pm>tracert
Tracing route to [74.125.65.105]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.6.187.99
2 2 ms 1 ms 1 ms 192.168.1.1
3 * * * Request timed out.
4 9 ms 9 ms 25 ms rd2bb-ge0-0-0-1.vc.shawcable.net [64.59.174.131]

5 40 ms 10 ms 15 ms rc2bb-tge0-9-2-0.vc.shawcable.net [66.163.69.41]

6 13 ms 12 ms 16 ms rc2wh-tge0-0-1-0.vc.shawcable.net [66.163.69.65]

7 20 ms 13 ms 27 ms rc4wt-pos14-0-0.wa.shawcable.net [66.163.76.130]

8 38 ms 58 ms 14 ms 72.14.216.66
9 15 ms 21 ms 16 ms 209.85.249.32
10 83 ms 61 ms 61 ms 209.85.248.128
11 76 ms 106 ms 65 ms 209.85.249.18
12 115 ms 106 ms 107 ms 209.85.242.215
13 85 ms 96 ms 97 ms 72.14.239.131
14 150 ms 116 ms 89 ms 209.85.253.221
15 119 ms 83 ms 83 ms gx-in-f105.google.com [74.125.65.105]

Trace complete.


then i run it in another pc and here are the results as well:


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

C:\Documents and Settings\cn072pm>tracert
Tracing route to [74.125.65.105]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.6.187.99
2 2 ms 1 ms 1 ms 192.168.1.1
3 * * * Request timed out.
4 9 ms 9 ms 25 ms rd2bb-ge0-0-0-1.vc.shawcable.net [64.59.174.131]

5 40 ms 10 ms 15 ms rc2bb-tge0-9-2-0.vc.shawcable.net [66.163.69.41]

6 13 ms 12 ms 16 ms rc2wh-tge0-0-1-0.vc.shawcable.net [66.163.69.65]

7 20 ms 13 ms 27 ms rc4wt-pos14-0-0.wa.shawcable.net [66.163.76.130]

8 38 ms 58 ms 14 ms 72.14.216.66
9 15 ms 21 ms 16 ms 209.85.249.32
10 83 ms 61 ms 61 ms 209.85.248.128
11 76 ms 106 ms 65 ms 209.85.249.18
12 115 ms 106 ms 107 ms 209.85.242.215
13 85 ms 96 ms 97 ms 72.14.239.131
14 150 ms 116 ms 89 ms 209.85.253.221
15 119 ms 83 ms 83 ms gx-in-f105.google.com [74.125.65.105]

Trace complete.

thank you for your help
 
It looks like your problem is from your gateway (192.168.1.1) to your Shaw modem, For Shaw the normal routing out of your LAN is LAN ->gateway ->Shaw modem (public facing IP address). However, usually if you can't reach the Shaw modem then you have NO Internet connection.

Do you have a static or dynamic IP address with Shaw? If static, did Shaw change something two weeks ago?

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
 
Interesting...there is now way to tell if the problem is from the gateway to the shaw modem from the information posted.

First, ask your ISP if they are experiencing any performance problems. Second, logon to your Firewall and find out the top 10 traffic users during the slowness. IE: With a Cisco FW you can run top talkers. This will show who is pushing the most traffic at that time. If your firewall doesn't show top bandwidth users then you'll have to figure out another way to capture that.

You can capture that by configuring port mirroring, on your switch, the traffic sent to the inside interface of your firewall. Then capture the port mirror in Wireshark.

After collecting the packets for a while you can tell who's pushing the most traffic (If any). A tool that would be useful to determine if it is traffic generated by your network or not is to install CACTI. (google it).

Cacti will graph the interfaces of your firewall and show you utilization. Is the utilization high? low?

If low - the problem is likely at your ISP or outwards from there. If high - is being generated internally and you need to track those users down.
 
there is now way to tell if the problem is from the gateway to the shaw modem from the information posted

With Shaw the routing out would be from the default gateway to the Shaw modem (public facing IP) and then out to the rest of Shaw's network. Hop 3, which given the information provided by JOSROS (...a gateway connected to back office then we have another network connected to our switchbox.), should be from what I'm taking as the default gateway (192.168.1.1) to the Shaw modem is timing out. To me that indicates either a problem with the cable from the default gateway to the modem or a problem with the modem. Shaw has excellent customer service. I'd give them a call.

Hope this helps.

Please help us help you. Read Tek-Tips posting polices before posting.
 
No, that's incorrect.

That the tracert succeeds beyond the gateway shows the path is good.

The lack of packet loss and the relatively steady latencies on each of the hops shows the link path is reliable.

That it fails on just that hop only indicates standard firewall behaviour, on that hop.
 
VinceWhirlWind is RIGHT! Traceroute sends back packets with the trace info displayed. firewalls tend to block those packets. Now if the trace timed out beyond that firewall then I'd be concerned but I can turn off these packets on a series of routers in a string and demo that behavior.
 
what download speed should you be getting? go to speakeasy.net and test your speed, how far off are you?
 
Best way to tell if and why you are getting dropped packets are

A)Wireshark
B)show commands in the edge router
C-Y)Various other tools
Z)Guessing

tim@tim-laptop ~ $ sudo apt-get install windows
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package windows...Thank Goodness!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top