tweaking continued.....

[Chillinhh]

Ok well ill try that.

[Chillinhh]

OK i pinged www.cox.net trough command prompt and got this


Pinging www.cox.net [68.1.17.9] with 32 bytes of data:

Reply from 68.1.17.9: bytes=32 time=40ms TTL=247
Reply from 68.1.17.9: bytes=32 time=80ms TTL=247
Reply from 68.1.17.9: bytes=32 time=60ms TTL=247
Reply from 68.1.17.9: bytes=32 time=40ms TTL=247

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


ISnt that high?

[Chillinhh]

Pinging www.speedguide.net [63.217.30.70] with 32 bytes of data

Reply from 63.217.30.70: bytes=32 time=220ms TTL=239
Reply from 63.217.30.70: bytes=32 time=230ms TTL=239
Reply from 63.217.30.70: bytes=32 time=180ms TTL=239
Reply from 63.217.30.70: bytes=32 time=161ms TTL=239

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

[Chillinhh]

well tommorow there coming to check out my lines and stuff. :)
I hope i get something new. HEHE.

[Lobo]

It's alittle high, but ISP can fix it, be cool mate:)

[Chillinhh]

lol ok ill try. Ok theyll be here tomorow theyll be here tommorow. IT will get faster it will get faster just remember that. I need to remember that before i launch my cable modem out the window and try to hit the cox van down the road.

[Lobo]

I want it:D

[Chillinhh]

Well cox said that its a pc issue. THey also said that soon there coming out with new packages for gamers:D so you can get even more bandwitch im capped at 3000/256 and if they come out with packages with more me will be happy.:D :D WEll anyways my problem is not solved and the computer was locking up a lot so he said its a computer issue and that everthing else is fine. I wonder what it is it was fine until i upgraded to windows 2000 and when i try to format my hard drive and do a clean install for windows 2000 it says that theres an error on the hard drive and it can not format so i have to do dual boot. WEll anyone know what i can try and see what my problem is?Im not happy.:(

[Chillinhh]

Ok well i used these settings

DefaultReceiveWindow = 384000
DefaultSendWindow = 32768
DisableAddressSharing = 1
InitialLargeBufferCount = 100
InitialMediumBufferCount = 240
InitialSmallBufferCount = 320
LargeBufferSize = 81920
MaxFastTransmit = 64000
MediumBufferSize = 15040
PriorityBoost = 0
SmallBufferSize = 1280
TransmitWorker = 32
FastSendDatagramThreshold = 4096
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceive = 0
GlobalMaxTcpWindowSize = 128480
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 0
TcpLogLevel = 1
TcpMaxDupAcks = 2
TcpMaxHalfOpen = 100
TcpMaxHalfRetried = 80
TcpRecvSegmentSize = 1460
TcpSendSegmentSize = 1460
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 128480
MaxConnectionsPer1_0Server = 20
MaxConnectionsPerServer = 10
DefaultTTL = 64
DisableUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 92


but when i do the analyzer this is what i get.



Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Note: Read the FAQ if the above is not your IP address.

TCP options string = 020405b401010402

MTU = 1500
MTU is fully optimized for broadband.

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

Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535
Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install 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:
Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 49 hops
TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

[Andrzej]

during waiting for LOBO :cool:
please recol for me yours: PC, OS, & cap
1.your Tcp1323Opts = 0 limited
RWIN value to Default Receive Window (RWIN) = 65535
you can try Tcp1323Opts = 1 (but with pings > 200ms try =3):)

[Chillinhh]

my caps are 3000/256 and the rest of info is in my sig.

[Chillinhh]

my speeds are still f**ked i dont know what it is my lines and stuff are fine. When i had windows 98 they were find then i upgraded to 2000 they went to hell can anyone help me out? I dont like not being able to play quake 3!!!!!!!!!!

[mnosteele52]

If you are using a GlobalMaxTcpWindowSize/TcpWindowSize of 65535 or higher you need to set Tcp1323Opts to 1. Try doing that and see what you get, then try and set it back to 0 and try GlobalMaxTcpWindowSize/TcpWindowSize's of 37960 or 52560 and see what you get.:) :D

[Chillinhh]

The best i did with was 513920 but that was only 1400 download. Know what else i need to do i set the buffermultipler to 400. I miss those 3000's:(

[Chillinhh]

man i cant even play the new unreal because of my internet lags so baddd...

[Chillinhh]

I mean my friend with dsl pings way lower than me!! My speeds are normally way better than his... I wish i could fix this.

[Chillinhh]

Here is my settings

TCP properties for IP = xx.xxx.xx.xxx (ipxx-xxx-xx-xxx.nc.hr.cox.net)
Browser/OS = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Note: Read the FAQ if the above is not your IP address.

TCP options string = 020405b40103030301010402

MTU = 1500
MTU is fully optimized for broadband.

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

Default Receive Window (RWIN) = 513920
RWIN Scaling (RFC1323) = 3 bits
Unscaled Receive Window = 64240
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:
Your RcvWindow limits you to: 20556.8 kbps (2569.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 8222.72 kbps (1027.84 KBytes/s) @ 500ms

MTU Discovery (RFC1191) = ON

Time to live left = 48 hops
TTL value is ok.

Timestamps (RFC1323) = OFF

Selective Acknowledgements (RFC2018) = ON

IP type of service field (RFC1349)= 00000000

[mnosteele52]

Lower your RWIN, why would you use such a high RWIN?:rolleyes:

[Chillinhh]

well to what? also i cant get my onboard lan card to work. When i go to surf the net it just says the can not find page thing.

[Chillinhh]

My internet isnt as bad in the morning i wonder why?

[Andrzej]

you describe your system as:
:2cool: my caps are 3000/256 and the rest of info is in my sig.
specs-Amd xp 2200+, epox 8k5a2+,corsair 512mb pc2700,ax-7 heatsink and tornado fan,
ATI All In Wonder radeon 8500,
Windows 2000 and mandrake and maybe trying redhat,
Cable Cox HSI
:( with WILD not fixed ping range 30-230!
:) I had used such & similar Default Receive Window (RWIN) = 513920 for mths
=352*mss he he he
from 2mths I was swiched on PPPoE & it not working for me
in the past it worked fine for me
despite few retransmisions
its not such important on surfing
but probably can killed MANY gamers round the world
Is realy you use TCP/IP on "gamer personality" ????
>check for retransmision
high ping Timestamps (RFC1323) = OFF see above = you better swich on
unfixed ping to several IP unfortunately I have such experience
first: check on your wire at home; disconect ALL unnecesary devices
second: A your ISP - you can reduce mthly fee :)

[Chillinhh]

what are you saying with all that?

[Andrzej]

I did not follow you

[Chillinhh]

what im saying is i didnt follow what you said earlier. Hehe

[Andrzej]

OK hehehe
1. explained hrd data is yours
2. RWIN is yours - such one I had (513920) for mths
3. ping problem 30-230 is from your posts
to IP 68.1.17.9 ping 40-80ms in
http://forums.speedguide.net/showthread.php?s=&postid=798517#post798517

to IP 63.217.30.70 ping 160-230ms in
http://forums.speedguide.net/showthread.php?s=&postid=798518#post798518

so in my opinion: you can have problem with ping stability:)
that & my experience in this meter was explained in my post above;)
thank you that you noted
it will be beter for me to "write posts more simply" :2cool:

[Chillinhh]

lol. WEll anyways i just want to get this freaking thing smoking like it used to it used to smoke around 3000 or so when i had windows 98,upgraded to windows 2000 and then my speeds when to h*** i cant play quake 3 or unreal or any multiplayer games. :( :(

[Chillinhh]

Its got to be a tweaking problem because im getting like 900 and when i had 98 i got 900 then i tweaked it and was rocking so i think i just need to find the right settings.So if ya could post some settings for me. espically dr.tweak hes who got me rocking when i had 98.

[Chillinhh]

You got to help me every server i get in says my ping is 999 i cant play any games im so ****ing pissed.

[Chillinhh]

I messaged cox and they said that 900 kbps is not bad w/e. WEll i lag at 999 on all servers someone please help.

[Chillinhh]

Ever since i upgraded to windows 2000 its been nothing but trouble. I Should have got windows xp instead:mad:

[Chillinhh]

Holy crap looked what happened when i tried one of speed guides patches.

Pinging www.cox.net [68.1.17.9] with 32 bytes of data:

Reply from 68.1.17.9: bytes=32 time=1062ms TTL=245
Reply from 68.1.17.9: bytes=32 time=1111ms TTL=245
Reply from 68.1.17.9: bytes=32 time=1102ms TTL=245
Request timed out.

Ping statistics for 68.1.17.9:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1062ms, Maximum = 1111ms, Average = 818ms

[Chillinhh]

This is what i got with my own tweaks
Pinging www.cox.net [68.1.17.9] with 32 bytes of data:

Reply from 68.1.17.9: bytes=32 time=160ms TTL=247
Reply from 68.1.17.9: bytes=32 time=111ms TTL=247
Reply from 68.1.17.9: bytes=32 time=100ms TTL=247
Reply from 68.1.17.9: bytes=32 time=90ms TTL=247

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

[Chillinhh]

I guess no one knows how to help me :( this internet **** is too much trouble.

[Lobo]

I don't have problem, call your ISP


Pinging [68.59.104.1] with 32 bytes ->bytes=32 time=9ms TTL=255
Pinging [68.59.104.1] with 32 bytes ->bytes=32 time=8ms TTL=255
Pinging [68.59.104.1] with 32 bytes ->bytes=32 time=10ms TTL=255
Pinging [204.127.166.135] with 32 bytes ->bytes=32 time=47ms TTL=53
Pinging [204.127.166.135] with 32 bytes ->bytes=32 time=49ms TTL=53
Pinging [204.127.166.135] with 32 bytes ->bytes=32 time=48ms TTL=53
Pinging [207.155.184.74] with 32 bytes ->bytes=32 time=55ms TTL=241
Pinging [207.155.184.74] with 32 bytes ->bytes=32 time=54ms TTL=241
Pinging [207.155.184.74] with 32 bytes ->bytes=32 time=54ms TTL=241
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=41ms TTL=240
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=41ms TTL=240
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=39ms TTL=240
Ping statistics for above hosts:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 8ms, Maximum = 55ms, Average = 37ms

:)

[Chillinhh]

isp cant do **** i called them they just say its a computer problem that i need a patch or something and i told them i tried tweaking and they said well i cant help you.

[Chillinhh]

i know yall are getting tired of me posting and complaining but its worrys the hell out of me. Anyways just if anyone has any suggestions let me know. THeres got to be something to do with some software because when i upgraded to 2000 it went down.