Jump to content

Huge Speed Problems


Recommended Posts

So I posted in the wrong forum it looks like and since I'm an idiot noob I didn't even do that right.  I'm looking for any help anyone can offer.  Here's most of what was asked for. TY

Running Windows Media Center 2005 OS (Windows XP)

Cox provides the net at adv. speeds of 4 Mbps down and 512 Kbps up

I'm not totally sure what I'm doing, but I believe I DL'ed the tweaks from speedguide.net

Checked for spyware and I'm running Norton Anti-Virus

Here are my test results:

:::.. Download Stats ..:::

Connection is:: 256 Kbps about 0.3 Mbps (tested with 386 kB)

Download Speed is:: 31 kB/s

Tested From:: https://testmy.net (server2)

Test Time:: Fri Feb 10 14:53:38 CST 2006

Bottom Line:: 5X faster than 56K 1MB download in 33.03 sec

Diagnosis: May need help : running at only 6.23 % of your hosts average (Cox.net)

Validation Link:: https://testmy.net/stats/id-MIVDC5N1A

------  Web100 Detailed Analysis  ------

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 1506.91 msec; the Packet size = 1460 Bytes; and

No packet loss was observed.

This connection is receiver limited 64.95% of the time.

  Increasing the the client's receive buffer (63.0 KB) will improve performance

This connection is network limited 35.03% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:

RFC 2018 Selective Acknowledgment: OFF

RFC 896 Nagle Algorithm: ON

RFC 3168 Explicit Congestion Notification: OFF

RFC 1323 Time Stamping: OFF

RFC 1323 Window Scaling: OFF

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 [x.x.x.x] but Client says [x.x.x.x]

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 123

AckPktsOut: 0

BytesRetrans: 0

CongAvoid: 0

CongestionOverCount: 0

CongestionSignals: 0

CountRTT: 123

CurCwnd: 65700

CurMSS: 1460

CurRTO: 2880

CurRwinRcvd: 65535

CurRwinSent: 16304

CurSsthresh: 2147483647

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 411720

DataPktsIn: 0

DataPktsOut: 282

DupAcksIn: 0

ECNEnabled: 0

FastRetran: 0

MaxCwnd: 65700

MaxMSS: 1460

MaxRTO: 3040

MaxRTT: 2080

MaxRwinRcvd: 65535

MaxRwinSent: 16304

MaxSsthresh: 0

MinMSS: 1460

MinRTO: 320

MinRTT: 70

MinRwinRcvd: 65535

MinRwinSent: 16304

NagleEnabled: 1

OtherReductions: 0

PktsIn: 123

PktsOut: 282

PktsRetrans: 0

X_Rcvbuf: 103424

RcvWinScale: 2147483647

SACKEnabled: 0

SACKsRcvd: 0

SendStall: 0

SlowStart: 43

SampleRTT: 2060

SmoothedRTT: 2050

X_Sndbuf: 103424

SndWinScale: 2147483647

SndLimTimeRwin: 7066091

SndLimTimeCwnd: 3811210

SndLimTimeSender: 2575

SndLimTransRwin: 1

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 229220

SndLimBytesCwnd: 182500

SndLimBytesSender: 0

SubsequentTimeouts: 0

SumRTT: 185350

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTimeUsec: 824939

Duration: 10882447

c2sData: 2

c2sAck: 2

s2cData: 9

s2cAck: 2

half_duplex: 0

link: 100

congestion: 0

bad_cable: 0

mismatch: 0

spd: 0.00

bw: 7.39

loss: 0.000001000

avgrtt: 1506.91

waitsec: 0.00

timesec: 10.00

order: 0.0000

rwintime: 0.6495

sendtime: 0.0002

cwndtime: 0.3503

rwin: 0.5000

swin: 0.7891

cwin: 0.5013

rttsec: 1.506911

Sndbuf: 103424

aspd: 1.32349

Checking for mismatch on uplink

(speed > 50 [0>50], (xmitspeed < 5) [0.27<5]

(rwintime > .9) [0.64>.9], (loss < .01) [1.0E<.01]

Checking for excessive errors condition

(loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.35>.6],

(loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]

Checking for 10 Mbps link

(speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]

(xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]

Checking for Wireless link

(sendtime = 0) [2.0E=0], (speed < 5) [0<5]

(Estimate > 50 [7.39>50], (Rwintime > 90) [0.64>.90]

(RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]

Checking for DSL/Cable Modem link

(speed < 2) [0<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [2.0E-4=0], (mylink > 0) [3.0>0]

Checking for half-duplex condition

(rwintime > .95) [0.64>.95], (RwinTrans/sec > 30) [0.1>30],

(SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]

Checking for congestion

(cwndtime > .02) [0.35>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [0>0]

estimate = 7.39 based on packet size = 11Kbits, RTT = 1506.91msec, and loss = 1.0E-6

The theoretical network limit is 7.39 Mbps

The NDT server has a 101.0 KByte buffer which limits the throughput to 0.52 Mbps

Your PC/Workstation has a 63.0 KByte buffer which limits the throughput to 0.33 Mbps

The network based flow control limits the throughput to 0.33 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is '10 Gig', Server Acks report link is 'T1'

TCP properties for IP = x.x.x.x

Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0)

Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405b4

MTU = 1500

MTU is fully optimized for broadband.

MSS = 1460

Maximum useful data in each packet = 1460, which equals MSS.

Default TCP Receive Window (RWIN) = 65535

RWIN Scaling (RFC1323) = 0 bits

Unscaled TCP Receive Window = 65535

Note: TCP 1323 Options need to be enabled for RWIN over 2^16 (65535). Windows 9x might also need the MS Vtcp386 fix.

For optimum performance, consider changing RWIN to a multiple of MSS.

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of 8)

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44) 

bandwidth * delay product (Note this is not a speed test):

Your TCP Window limits you to: 2621.4 Kbps (327.675 KBytes/s) @ 200ms

Your TCP Window limits you to: 1048.56 Kbps (131.07 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 119 hops

TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = OFF 

IP type of service field (RFC1349) = 00000000 (0)

If there's any other info needed, I can try to get it for you.  Thank you very much in advance for the help.

Link to post
Share on other sites

So I've checked everything, tried to tweak everything, and I still have the aforementioned slow speeds.  I live in an apartment and my roommates computer is running at the same slow speed as well.  I had a tech guy from Cox come out and he said everything looks great and he doesn't think I have a problem.  His recommendation was to wait a while and call back if the speed doesn't pick up.

I've scanned for viruses and spyware, and nothing shows up.  I tried moving things around in case of potential noise, no luck.  Here's the main problem I think...it seems whenever I try to download something, the speed starts off OK and quickly plummets to 31kbps range.  I think something is inhibiting the speed, but I'm too computer dumb to figure out what.  Web pages load fine and the tech guy said I had good ping numbers and I didn't lose hardly any packets (he could be wrong but I took him for his word).  Any input would be appreciated.

Link to post
Share on other sites

Hey Bookworm1x!

If it's not an ISP problem but something on your end, the guys and girls on this forum are awesome with helping out, you're in the right place!

Try running a tracert to this address (Start > Run > type 'command' > in the black command terminal that appears type 'tracert testmy.net' > copy and paste the results into a new post).

That'll give the peeps here an idea of where your data stream is going. 

Link to post
Share on other sites

Hi there everyone,

Bookworm's nitro test results showed 2 abnormalies: very high RTT value (1507 ms) and RWIN set to 65535.

"Round trip time = 1506.91 msec

MaxRwinRcvd: 65535"

The test concluded that Bookworm's comp is the source of limiting signal flow 65% of the time.

"This connection is receiver limited 64.95% of the time.

  Increasing the the client's receive buffer (63.0 KB) will improve performance

This connection is network limited 35.03% of the time"

Rammolo is correct to suspect that a good possibility is modem/router problem and Nitro4WD gave a good susgestion to run a tracert which may be able to show the location of the problem by comparing ping times.

Bookworm mentioned he DL from www.speedguide.net, but your RWIN at standard 65535 shows you have not yet tweak your comp. When RTT value can be corrected to normal values (100-160 ms if you are located in the US and 250-300 ms if from overseas), you can choose RWIN values of first 64240 and then 128480 to test for optimum setting as recommended by the TCP Analyzer:

"For optimum performance, consider changing RWIN to a multiple of MSS.

Other values for RWIN that might work well with your current MTU/MSS:

513920 (MSS x 44 * scale factor of Cool

256960 (MSS x 44 * scale factor of 4)

128480 (MSS x 44 * scale factor of 2)

64240 (MSS x 44)

bandwidth * delay product (Note this is not a speed test):"

Shall we have a look at a tracert?

Link to post
Share on other sites

Thanks for all of your help and support.  Here is what you asked for.

C:DOCUME~1HP_ADM~1>tracert testmy.net

Tracing route to testmy.net [67.18.179.85]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2     8 ms    14 ms     7 ms  10.3.32.1

  3    10 ms     9 ms    11 ms  68.12.10.209

  4     9 ms    15 ms     7 ms  mtc3dsrc02-gew0303.rd.ok.Cox.net [68.12.14.13]

  5     8 ms     8 ms     8 ms  68.1.1.56

  6    12 ms    24 ms    14 ms  dllsbbrc02-pos0002.rd.dl.Cox.net [68.1.0.114]

  7    18 ms    14 ms    14 ms  dllsbbrc01-pos0100.rd.dl.Cox.net [68.1.0.142]

  8    14 ms    41 ms    14 ms  68.105.30.2

  9    15 ms    15 ms    14 ms  64.124.79.77.theplanet.com [64.124.79.77]

10    13 ms    15 ms    14 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

11    33 ms    15 ms    14 ms  vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

12    12 ms    15 ms    14 ms  gi1-0-2.car17.dllstx4.theplanet.com [67.18.116.85]

13    15 ms    15 ms    14 ms  85.67-18-179.reverse.theplanet.com [67.18.179.85]

Trace complete.

EDIT: ...and to clearify...I restored my computer after I tried all the tweaking.  That explains the difference.

Link to post
Share on other sites

Your tracert does not show any problem with signal flow. So our first assumption  is not correct. Still, there is the question of high RTT.

There is a part of the nitro test result you did not post. This part shows the number of retransmission, duplicate ACKs, etc.

Could you do the nitro test again but with the U of Michigan:

http://speedtest.umflint.edu/

Link to post
Share on other sites

TCP/Web100 Network Diagnostic Tool v5.2.0f

click START to begin

Checking for Middleboxes . . . . . . . . . . . . . . . . . .  Done

running 10s outbound test (client to server) . . . . . 270.99Kb/s

running 10s inbound test (server to client) . . . . . . 260.42kb/s

Your PC is connected to a Cable/DSL modem

click START to re-test

Cable modem/DSL/T1 link found.

Link set to Full Duplex mode

No network congestion discovered.

Good network cable(s) found

Normal duplex operation found.

Web100 reports the Round trip time = 1473.96 msec; the Packet size = 1460 Bytes; and

No packet loss was observed.

This connection is receiver limited 63.24% of the time.

  Increasing the current receive buffer (63.0 KB) will improve performance

This connection is network limited 36.66% of the time.

  Contact your local network administrator to report a network problem

    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

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 [x.x.x.x] but Client says [x.x.x.x]

WEB100 Kernel Variables:

Client: localhost/127.0.0.1

AckPktsIn: 116

AckPktsOut: 0

BytesRetrans: 0

CongestionSignals: 0

CountRTT: 116

CurrentCwnd: 65700

CurrentMSS: 1460

CurrentRTO: 2810

CurrentRwinRcvd: 65535

CurrentRwinSent: 5840

CurrentSsthresh: 2147483647

DSACKDups: 0

DataBytesIn: 0

DataBytesOut: 394200

DataPktsIn: 0

DataPktsOut: 270

DupAcksIn: 0

ECNEnabled: 0

FastRetran: 0

MaxCwnd: 65700

MaxMSS: 1460

MaxRTO: 3020

MaxRTT: 2050

MaxRwinRcvd: 65535

MaxRwinSent: 5840

MaxSsthresh: 0

MinMSS: 1460

MinRTO: 280

MinRTT: 50

MinRwinRcvd: 65535

MinRwinSent: 5840

NagleEnabled: 1

PktsIn: 116

PktsOut: 270

PktsRetrans: 0

Rcvbuf: 128000

SACKEnabled: 3

SACKsRcvd: 0

SmoothedRTT: 2000

Sndbuf: 128000

SndLimTimeRwin: 6509910

SndLimTimeCwnd: 3773750

SndLimTimeSender: 9243

SndLimTransRwin: 1

SndLimTransCwnd: 1

SndLimTransSender: 1

SndLimBytesRwin: 211700

SndLimBytesCwnd: 182500

SndLimBytesSender: 0

SumRTT: 170980

Timeouts: 0

TimestampsEnabled: 0

WinScaleRcvd: 2147483647

WinScaleSent: 2147483647

DupAcksOut: 0

StartTime: 2147483647

CurrTime: 10314890

c2sData: 2

c2sAck: 2

s2cData: 6

s2cAck: 2

Checking for mismatch condition

(cwndtime > .3) [0.36>.3], (MaxSsthresh > 0) [0>0],

(PktsRetrans/sec > 2) [0>2], (estimate > 2) [7.55>2]

Checking for mismatch on uplink

(speed > 50 [0.30>50], (xmitspeed < 5) [0.27<5]

(rwintime > .9) [0.63>.9], (loss < .01) [1.0E<.01]

Checking for excessive errors condition

(loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.36>.6],

(loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]

Checking for 10 Mbps link

(speed < 9.5) [0.30<9.5], (speed > 3.0) [0.30>3.0]

(xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (link > 0) [100>0]

Checking for Wireless link

(sendtime = 0) [8.97=0], (speed < 5) [0.30<5]

(Estimate > 50 [7.55>50], (Rwintime > 90) [0.63>.90]

(RwinTrans/CwndTrans = 1) [1/1=1], (link > 0) [100>0]

Checking for DSL/Cable Modem link

(speed < 2) [0.30<2], (SndLimTransSender = 0) [1=0]

(SendTime = 0) [8.979973871316965E-4=0], (link > 0) [100>0]

Checking for half-duplex condition

(rwintime > .95) [0.63>.95], (RwinTrans/sec > 30) [0.10>30],

(SenderTrans/sec > 30) [0.10>30], OR (link <= 10) [100<=10]

Checking for congestion

(cwndtime > .02) [0.36>.02], (mismatch = 0) [0=0]

(MaxSsthresh > 0) [0>0]

bw = 7.55 based on packet size = 11Kbits, RTT = 1473.96msec, and loss = 1.0E-6

The theoretical network limit is 7.55 Mbps

The transmit buffer (125.0 KByte) limits the application to 0.66 Mbps

Your receive buffer (63.0 KByte) limits the application to 0.33 Mbps

The network based flow control limits the application to 0.34 Mbps

Client Data reports link is 'T1', Client Acks report link is 'T1'

Server Data reports link is 'OC-12', Server Acks report link is 'T1'

Link to post
Share on other sites

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsHP_Administrator>C:netstat-b

'C:netstat-b' is not recognized as an internal or external command,

operable program or batch file.

C:Documents and SettingsHP_Administrator>netstat -b

Active Connections

  Proto  Local Address          Foreign Address        State          PID

  TCP    your-55e5f9e3d2:1043  ats-rab.dial.aol.com:5190  ESTABLISHED    1796

  [AOLSoftware.exe]

  TCP    your-55e5f9e3d2:1049  205.188.8.23:5190      ESTABLISHED    1968

  [aim6.exe]

  TCP    your-55e5f9e3d2:2354  kdc.uas.aol.com:https  ESTABLISHED    1796

  [AOLSoftware.exe]

  TCP    your-55e5f9e3d2:2994  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:2995  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:2996  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:2997  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:2999  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3001  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3002  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3005  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3006  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3009  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3010  opium2.msg.vip.dcn.yahoo.com:http  TIME_WAIT

  0

  TCP    your-55e5f9e3d2:3015  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3016  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3017  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3018  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3019  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3020  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3021  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3022  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3023  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3024  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3025  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3026  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3027  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3029  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3030  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3031  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3032  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3033  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3034  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3035  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3036  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3037  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3038  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3039  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3040  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3041  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3042  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3043  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3044  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3046  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3048  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3053  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3055  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3059  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3061  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3063  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3064  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3065  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3066  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3067  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3068  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3070  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3071  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3073  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3074  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3075  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3076  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3077  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3078  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3079  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3080  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3081  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

  TCP    your-55e5f9e3d2:3082  85.67-18-179.reverse.theplanet.com:http  TIME_WA

IT      0

C:Documents and SettingsHP_Administrator>

Link to post
Share on other sites

Judging from your netstat, I imagine the eliminating some startup items will do some good.

Click start, run, type msconfig and click ok. Go to the startup tab, and start unchecking things that you don't absolutely need to load when windows starts (keep in mind you can always start applications manually when you need them). For example, you don't need real-time anti-virus/anti-spyware protection; it is a resource hog, and you are just as well protected if you are updating and scanning manually. You don't need IM or P2P programs on startup, and you probably don't need 90% of the other stuff starting up. Basically, anything with the path of "C:program files" is not absolutely necessary.

Once you've removed a bunch of checkmarks, click apply, then click close, and restart when prompted. Then try another speedtest and a netstat.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...