Annoying slowdown at night

[Teknomajik]

All right.

I've been through all the motions. ISP called several times. two techs (PC and modem) can find zip wrong, but of course this was during the day.

TCP Analyzer:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 10.14.2007 01:26
IP address: 68.145.xx.xx

TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 65535 (NOT multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 65535
Reccomended RWINs: 64240, 128480, 256960, 513920
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 110
Timestamps: OFF
SACKs: ON
IP ToS: 10111000 (184)
Precedence: 101 (CRITIC/ECP)
Delay: 1 (low delay)
Throughput: 1 (low throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: EF PHB 101110 (46) - Expedited Forwarding (recommended for video/audio - high priority, higher drop probability). See RFC 2598.


Trace route:



Tracing route to google.ca [72.14.207.104]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.1.1

2 * * * Request timed out.

3 64 ms 31 ms 113 ms rd1no-ge3-0-0-12.cg.shawcable.net [64.59.142.243]

4 114 ms 21 ms 17 ms rc1no-ge6-0-0.cg.shawcable.net [66.163.77.5]

5 161 ms 282 ms 19 ms rc1so-pos15-0.cg.shawcable.net [66.163.77.9]

6 31 ms 186 ms 27 ms rc1wh-pos12-0.vc.shawcable.net [66.163.76.10]

7 68 ms 44 ms 68 ms rc1wt-pos1-0-0.wa.shawcable.net [66.163.76.2]

8 32 ms 79 ms 60 ms six.sea01.google.com [198.32.180.17]

9 86 ms 85 ms 124 ms 72.14.233.117

10 475 ms 150 ms 438 ms 209.85.250.110

11 126 ms 445 ms * 66.249.94.96

12 280 ms 92 ms 202 ms 66.249.94.50

13 95 ms 163 ms 172 ms eh-in-f104.google.com [72.14.207.104]


Trace complete.

NDT:

EB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 44.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 221.52kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_03

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 176.84 msec; the Packet size = 1460 Bytes; and
There were 8 packets retransmitted, 29 duplicate acks received, and 54 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 1.52 seconds (15.2%) of the time
C2S throughput test: Packet queuing detected: 50.09%
S2C throughput test: Packet queuing detected: 19.44%
This connection is network limited 99.91% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [68.145.99.79] but Client says [192.168.1.102]




I've replaced my modem. I've done just about everything I can think of. ISP says levels are good, no congestion, etc. They assure me it's at my end.

I wanna know what the hell it is!

Thanks for any and all assistance.

[trogers]

TCP Analyzer:

« SpeedGuide.net TCP Analyzer Results »
Tested on: 10.14.2007 01:26
IP address: 68.145.xx.xx

TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 65535 (NOT multiple of MSS)
RWIN Scaling: 0
Unscaled RWIN : 65535
Reccomended RWINs: 64240, 128480, 256960, 513920

IP ToS: 10111000 (184)
Precedence: 101 (CRITIC/ECP)
Delay: 1 (low delay)
Throughput: 1 (low throughput)
Reliability: 0 (normal reliability)
Cost: 0 (normal cost)
Check bit: 0 (correct)
DiffServ: EF PHB 101110 (46) - Expedited Forwarding (recommended for video/audio - high priority, higher drop probability). See RFC 2598.


Trace route:



Tracing route to google.ca [72.14.207.104]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 64 ms 31 ms 113 ms rd1no-ge3-0-0-12.cg.shawcable.net [64.59.xxx.xxx]
4 114 ms 21 ms 17 ms rc1no-ge6-0-0.cg.shawcable.net [66.163.77.5]
5 161 ms 282 ms 19 ms rc1so-pos15-0.cg.shawcable.net [66.163.77.9]

NDT:

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 176.84 msec; the Packet size = 1460 Bytes; and
There were 8 packets retransmitted, 29 duplicate acks received, and 54 SACK blocks received
The connection stalled 2 times due to packet loss
The connection was idle 1.52 seconds (15.2%) of the time
C2S throughput test: Packet queuing detected: 50.09%
S2C throughput test: Packet queuing detected: 19.44%
This connection is network limited 99.91% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

I've replaced my modem. I've done just about everything I can think of. ISP says levels are good, no congestion, etc. They assure me it's at my end.

I wanna know what the hell it is!

Thanks for any and all assistance.

Your TCP Window is not tweaked. What speed did you pay to get? ToS value at 184 gives high packet losses.

Tracert shows high and irregular ping times at hop 3 (from modem to ISP switch. Cause could be either or both spyware in your comp and loose or damaged connectors or wiring from modem to the wall jack, or faulty spiltter if any.

Scan comp with SpyBot and Ad-Aware 2007 and clean up the registry with CCleaner.

Ensure modem is placed a few feet away from all other electrical devices including the router. Check the state of your cable/wiring and ensure excess lengths are not coiled up.

[Teknomajik]

Thanks for the prompt reply!

I pay for a 10 mbps cable service, I'm running a S&D scan now, and it's a fresh windows xp install (less than a week old) but I'll try that anyway.

I ran the length of my cable, found a couple of kinks, and corrected them

Now, my modem and router are close together, and on top of my TV. I've never had issues with them interfering with each other before, is there something that got wore down due to interference?

[trogers]

Thanks for the prompt reply!

I pay for a 10 mbps cable service, I'm running a S&D scan now, and it's a fresh windows xp install (less than a week old) but I'll try that anyway.

I ran the length of my cable, found a couple of kinks, and corrected them

Now, my modem and router are close together, and on top of my TV. I've never had issues with them interfering with each other before, is there something that got wore down due to interference?

Try the following with TCP Optimizer:

General Settings tab:
Custom settings - check
Modify All Network Adapters - check
network adapter selection - your NIC
MTU 1500
TTL - 64
TCP Receive Window - 256960
MTU Discovery - Yes
Black Hole Detect - No
Selective Acks - Yes
Max Duplicate ACKs - 2
TCP 1323 Options:
Windows Scaling - checked
Timestamps - uncheck

Advanced Settings tab:
Max Connections per Server - 10
Max Connections per 1.0 Server - 20
LocalPriority - 1
Host Priority - 1
DNSPriority - 1
NetbtPriority - 1
Lan Browsing speedup - optimized
QoS: NonBestEffortLimit - 0
ToS: DisableUserTOSSetting - 0
ToS: DefaultTOSValue - 80
MaxNegativeCacheTtl - 0
NetFailureCacheTime - 0
NegativeSOACache Time - 0
LAN Request Buffer Size - 32768
Then select "Apply Changes" and reboot to take effect

After the scanning, turn off the firewall in your comp and the router and do another tracert. If uneven ping times is seen at hop 2, the modem is suffering interference. If hop 2 and 3 have even ping times, then all is well.

[Teknomajik]

So I tried all of the above, and come peak times my internet slows right down again.

My ISP insists it's not saturation, so I'm at a loss here

[Sava700]

do you go through this hop to every location?

10 475 ms 150 ms 438 ms 209.85.250.110


otherwise try www.pingplotter.com set to 1second trace intervals and watch the connections packetloss and pings.

[Teknomajik]

doesn't seem to.

The biggest hop seems to be the 3rd. I've moved my modem as far as I can (3-4ft) and still get horrid pings. I have VOIP though the same cable and my ISP tells me that the phone line is more sensitive that the internet, yet doesn't seem to be impacted.

[Teknomajik]

Holy hell.

I think I found it.

I bypass all of my cables splitters and hooked my modem to the direct incoming wall jack.


Instant gratification.

So, my next question is, if the splitter and or coax is bad, why did speed issues crop up only at night?

[trogers]

I ran the length of my cable, found a couple of kinks, and corrected them


Hop 3 is the signal path from the modem to your ISP's switch.

The 'couple of kinks' may have weaken the cable shielding and picking up interference from some electrical device that is only turned on at night.

[YeOldeStonecat]

You mention a router..by chance is it a wireless router? If so...do you have wireless disabled if you don't use it...or if you do..do you have it locked down with WPA or WPA2 security? Else...some kid next door might be stealing your connection..and bandwidth...going P2P/warez download happy or something.

I recommend keeping network appliances (such as modem/switch/router) away from sources of EMI. I'd not have mine right on top of the tele...keep away from speakers, etc.

[Teknomajik]

The wireless is indeed locked down, in fact as part of my intial troubleshooting I removed the thing from my setup completely.

I just disabled the wireless, so we'll see.

I put in new splitters, didn't seem to help as I thought it would

I'll do some rewiring this weekend. see how that goes.

[Sava700]

still sounds like a ISP problem to me.. they won't admit to it..I haven't seen one yet that does.

[Teknomajik]

Well, I called them, while I was on hold I found out about maintenance in my area, so I'm not ready to write off my new splitters -just- yet.

[cubeblue]

Wow, this sounds really similar to my issue. My problems (lately) appear late night and go into the late morning. I also have a problem with my 3rd hop, though I'm with Comcast. I don't know of any appliance or electrical device in my house that stays off during the day and turns on at night.

Teknomajik, you said you thought you had the problem nailed when you went direct to the line coming into your house right? Was it during your 'problem time' (in the evening) that you checked this?