Results 1 to 18 of 18

Thread: Best configuration given to me, can I get better then this?

  1. #1
    Regular Member ITALIAN_GUY_20's Avatar
    Join Date
    Jul 2003
    Location
    Australia (Adelaide)
    Posts
    106

    Question Best configuration given to me, can I get better then this?

    Hello again ppl, I have been prescribed this configuration (look below), and yeah it is ok, good browsing speed, good ping connection, good download/upload connection. But..... I have seen better, and I was wondering if "I" could get the same?

    My configuration is as follows:

    TCP options string = 020405b40103030101010402
    MTU = 1500
    MTU is fully optimized for broadband.
    MSS = 1460
    Maximum useful data in each packet = 1460, which equals MSS.

    Default Receive Window (RWIN) = 128480
    RWIN Scaling (RFC1323) = 1 bits
    Unscaled Receive Window = 64240

    RWIN is 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)
    64240 (MSS x 44)
    bandwidth * delay product:

    Your RcvWindow limits you to: 5139.2 kbps (642.4 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 2055.68 kbps (256.96 KBytes/s) @ 500ms
    MTU Discovery (RFC1191) = ON
    Time to live left = 52 hops

    TTL value is ok.
    Timestamps (RFC1323) = OFF
    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 01011010

    Precedence (priority) = 010 (immediate)
    Delay = 1 (low delay)
    Throughput = 1 (high throughput)
    Reliability = 0 (normal reliability)
    Cost = 1 (low cost)

    I am running Windows Xp Professional
    My ISP is Telstra
    And my connection is Cable Uncapped (6000/6000).

    If you can prescribe a better configuration for me, I would love to hear your thoughts, and will be thankful for your help.
    DON'T LIVE YOUR LIFE TOO SERIOUSLY, YOU MIGHT NOT GET OUT OF IT ALIVE.

  2. #2
    R.I.P. 2013-11-22 blebs's Avatar
    Join Date
    Dec 2000
    Location
    North Canton, Ohio
    Posts
    12,819
    The only thing I might change is your RWIN. It probably won't make a difference, but you might try 256960 and see if it doesn't speed up the downloads any. Outside of that, looks good.

  3. #3
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    Your killin me here..... what are you tring to accomplish?


  4. #4
    R.I.P. 2013-11-22 blebs's Avatar
    Join Date
    Dec 2000
    Location
    North Canton, Ohio
    Posts
    12,819
    Which one of us is killing you here?

  5. #5
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    Originally posted by blebs99
    Which one of us is killing you here?
    LOL ITALIAN_GUY_20, he keeps posting this over and over......... and I don't understand why?




  6. #6
    Regular Member ITALIAN_GUY_20's Avatar
    Join Date
    Jul 2003
    Location
    Australia (Adelaide)
    Posts
    106

    Answer to your question.

    To get the BEST connection I can get, and to get the BEST connection is to ask about and to configer the computer to you get a better and better connection.
    DON'T LIVE YOUR LIFE TOO SERIOUSLY, YOU MIGHT NOT GET OUT OF IT ALIVE.

  7. #7
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    I understand that but it doesn't seem like you understand what the goal is in tweaking your connection....... 90% of your caps although it is VERY important to understand that sometimes you are not going to get that due to circumstances beyond your control.



  8. #8
    Regular Member ITALIAN_GUY_20's Avatar
    Join Date
    Jul 2003
    Location
    Australia (Adelaide)
    Posts
    106

    Cool I understand

    ok ok ok, I think I have done my dash already, thank you for ALL your help, I already have a GREAT connection, and thanx to your help and others I have a better one. I am greatful and I will stop now. If you want to see the END result here it is.

    TCP options string = 020405b40103030201010402
    MTU = 1500
    MTU is fully optimized for broadband.
    MSS = 1460
    Maximum useful data in each packet = 1460, which equals MSS.

    Default Receive Window (RWIN) = 256960
    RWIN Scaling (RFC1323) = 2 bits
    Unscaled Receive Window = 64240

    RWIN is 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)
    128480 (MSS x 44 * scale factor of 2)
    64240 (MSS x 44)
    bandwidth * delay product:

    Your RcvWindow limits you to: 10278.4 kbps (1284.8 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 4111.36 kbps (513.92 KBytes/s) @ 500ms
    MTU Discovery (RFC1191) = ON
    Time to live left = 52 hops

    TTL value is ok.
    Timestamps (RFC1323) = OFF
    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 01011010

    Precedence (priority) = 010 (immediate)
    Delay = 1 (low delay)
    Throughput = 1 (high throughput)
    Reliability = 0 (normal reliability)
    Cost = 1 (low cost)

    I will just go now and help others like you do. And yeah, take care of yourself and each other.
    DON'T LIVE YOUR LIFE TOO SERIOUSLY, YOU MIGHT NOT GET OUT OF IT ALIVE.

  9. #9
    Junior Member
    Join Date
    Apr 2000
    Location
    Ottawa, Ontario, Canada
    Posts
    17
    Italian guy, now you should dedicate yourself to HELPING ME... find me post subjected 'ROGERS CUSTOMER' somewhere in this forum, and pleeasee help!! I get the maddest spikes... I get the weirdest pings, and I get the most fluctuating lag I've ever been getting, this has all been occuring lately...I've tried all the patches on this site, nothing has improved/hampered it ...so please, help...me.

    -Anil
    Hi, I own two pairs of shoes.

  10. #10
    Regular Member ITALIAN_GUY_20's Avatar
    Join Date
    Jul 2003
    Location
    Australia (Adelaide)
    Posts
    106

    Thumbs up Ok, Here's what to do

    Copy and paste these links provided (oen by one ofcourse) and follow the instructions.

    http://forums.speedguide.net/showthr...301#post643301

    http://forums.speedguide.net/showthr...hreadid=105640

    After doing that come back here and tell me your progress.
    DON'T LIVE YOUR LIFE TOO SERIOUSLY, YOU MIGHT NOT GET OUT OF IT ALIVE.

  11. #11
    Junior Member
    Join Date
    Apr 2000
    Location
    Ottawa, Ontario, Canada
    Posts
    17
    Ok italian, here goes.

    I have WINDOWS XP PRO CORP.
    I have ROGERS @HOME HIGH SPEED
    I have 1500/192 advertised caps.
    TCP/IP ANALYZER
    ------------------------------------------------------------------------------------
    TCP options string = 020405b401010402010303000101080aac105d4600000000
    MTU = 1500
    MTU is fully optimized for broadband.
    MSS = 1460
    Maximum useful data in each packet = 1448, which is less than MSS because of Timestamps, or other TCP/IP options used.

    Default Receive Window (RWIN) = 17520
    RWIN Scaling (RFC1323) = 0 bits
    Unscaled Receive Window = 17520

    RWIN is 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: 700.8 kbps (87.6 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms
    Consider increasing your RWIN value to optimize TCP/IP for broadband.
    MTU Discovery (RFC1191) = ON
    Time to live left = 57 hops

    TTL value is ok.
    Timestamps (RFC1323) =
    Timestamps (RFC1323) = ON
    Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.

    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 00000000

    ------------------------------------------------------------------------------------
    CABLE NUTS AUTOMATED TELL-ME-ALL SCRIPT
    Download: 1500kbps
    Upload: 162kbps
    Latency: 100ms
    MTU: 1500
    DefaultReceiveWindow = 192000
    DefaultSendWindow = 20736
    DisableAddressSharing = 1
    InitialLargeBufferCount = 200
    InitialMediumBufferCount = 480
    InitialSmallBufferCount = 640
    LargeBufferSize = 819200
    MaxFastTransmit = 64000
    MediumBufferSize = 150400
    Priority Boost = 0
    SmallBufferSize = 12800
    TransmitWorker = 32
    FastSendDatagramThreshhold = 4096
    EnableFastRouteLookup = 1
    EnablePMTUDiscovery = 1
    IgnorePushBitsOnReceives = 0
    GlobalMaxTcpWindowSize = 20440
    MaxFreeTcbs = 8000
    MaxHashTableSize = 16384
    MaxNormLookupMemory = 5000000
    SackOpts = 1
    SynAttackProtect = 1
    Tcp1323Opts = 0
    TcpLogLevel = 1
    TcpMaxDupAttacks = 3
    TcpMaxHalfOpen = 100
    TcpMaxHalfOpenRetired = 80
    TcpRecvSegmentSize = 1460
    TcpSendSegmentSize = 1460
    TcpTimedWaitDelay = 30
    TcpUseRFC1122UrgentPointer = 0
    TcpWindowSize = 20440
    MaxConnectionsPer1_0Server = 10
    MaxConnectionsPerServer = 8
    DefaultTimeToLive = 64
    DefaultUserTOSSetting = 0
    TcpMaxDataRetransmissions = 6
    DefaultTOSValue = 90
    ------------------------------------------------------------------------------------
    >OTHER INFO ON MY LINE<
    ------------------------------------------------------------------------------------
    >NYC SPEAKEASY.NET TEST<
    ------------------------------------------------------------------------------------
    Another complaint I have before I go is...My pings to SPEAKEASY.NET game-servers... theyre are unbelievably fluctuating, let me paste you some examples.
    [][][][
    Pinging 64.81.159.135 with 32 bytes of data:
    Reply from 64.81.159.135: bytes=32 time=39ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=37ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=36ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=39ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=42ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=55ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=44ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=55ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=70ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=43ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=89ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=39ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=51ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=45ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=181ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=50ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=56ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=80ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=44ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=50ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=53ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=49ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=36ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=37ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=54ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=47ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=39ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=45ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=45ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=83ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=47ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=92ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=356ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=36ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=65ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=50ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=80ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=119ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=44ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=42ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=37ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=46ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=37ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=43ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=39ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=43ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=55ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=42ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=107ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=54ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=46ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=43ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=64ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=47ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=74ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=70ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=148ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=52ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=40ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=38ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=55ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=54ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=79ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=83ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=43ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=52ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=59ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=64ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=67ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=44ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=103ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=84ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=59ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=96ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=41ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=94ms TTL=239
    Reply from 64.81.159.135: bytes=32 time=55ms TTL=239

    Ping statistics for 64.81.159.135:
    Packets: Sent = 95, Received = 95, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 356ms, Average = 58ms
    [][][][][

    No real loss... just massively fluctuating... its really sad trying to PLAY on this server with this much fluctuation.

    ------------------------------------------------------------------------------------
    That's my story, and I'm stickin' to it! Please give any advice you can, I will be your student.

    -Anil
    Hi, I own two pairs of shoes.

  12. #12
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    OK it looks as if you have already found your maximum anticipated latency and used it on the CableNut Live page and it gave you those settings. The next step is to install CableNut and put in those settings then do the following:

    VERY IMPORTANT TO DO THE FOLLOWING

    1. Under your LAN connection - properties - general tab, uninstall all the protocols there that you do not need.

    2. Open IE and select tools - internet options - connections - LAN settings, make sure NOTHING there is checked.

    3. Make sure you have the latest drivers for your NIC from the manufacturer. Set your NIC duplex mode to 10mb half duplex for Cable, for DSL it is ISP dependent unless you are using a router, if so then set it to 100mb full duplex for both Cable & DSL (the instructions are in my Help & Tips link). If you are using a router make sure you have the latest firmware.

    4. Clear your temporary internet files.

    5. Power cycle your modem, unplug it for atleast 15 seconds.

    6. Download and update then do a scan with SpyBot 1.2 & Ad Aware 6.0 to remove any spyware then install and update SpywareBlaster to stay spyware FREE. YOU MUST USE BOTH AD AWARE & SPYBOT TO ENSURE YOU ARE SPYWARE FREE SINCE ONE FINDS WHAT THE OTHER MISSES.

    7. Make sure you do the faster web page tweak in my Help & Tips link.

    Once you do all that please post back with another analyzer test and speed test.


  13. #13
    Junior Member
    Join Date
    Apr 2000
    Location
    Ottawa, Ontario, Canada
    Posts
    17
    After doing ALL the stuff you just posted manofsteel, I got these results from the ANALYZER:
    ------------------------------------------------------------------------------------
    TCP options string = 020405b401010402010303000101080aac1a733e00000000
    MTU = 1500
    MTU is fully optimized for broadband.
    MSS = 1460
    Maximum useful data in each packet = 1448, which is less than MSS because of Timestamps, or other TCP/IP options used.

    Default Receive Window (RWIN) = 17520
    RWIN Scaling (RFC1323) = 0 bits
    Unscaled Receive Window = 17520

    RWIN is 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: 700.8 kbps (87.6 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms
    Consider increasing your RWIN value to optimize TCP/IP for broadband.
    MTU Discovery (RFC1191) = ON
    Time to live left = 57 hops

    TTL value is ok.
    Timestamps (RFC1323) =
    Timestamps (RFC1323) = ON
    Note: Timestamps add 12 bytes to the TCP header of each packet, reducing the space available for useful data.

    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 00000000
    ------------------------------------------------------------------------------------

    Any difference? Hmmmmmmmmmmmm


    -Anil
    Hi, I own two pairs of shoes.

  14. #14
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    Those settings are not the settings you posted above. Reopen CableNut and put in the following settings and remember to save to registry and reboot.

    DefaultReceiveWindow = 192000
    DefaultSendWindow = 20736
    DisableAddressSharing = 1
    InitialLargeBufferCount = 200
    InitialMediumBufferCount = 480
    InitialSmallBufferCount = 640
    LargeBufferSize = 819200
    MaxFastTransmit = 64000
    MediumBufferSize = 150400
    Priority Boost = 0
    SmallBufferSize = 12800
    TransmitWorker = 32
    FastSendDatagramThreshhold = 4096
    EnableFastRouteLookup = 1
    EnablePMTUDiscovery = 1
    IgnorePushBitsOnReceives = 0
    GlobalMaxTcpWindowSize = 20440
    MaxFreeTcbs = 8000
    MaxHashTableSize = 16384
    MaxNormLookupMemory = 5000000
    SackOpts = 1
    SynAttackProtect = 1
    Tcp1323Opts = 0
    TcpLogLevel = 1
    TcpMaxDupAttacks = 3
    TcpMaxHalfOpen = 100
    TcpMaxHalfOpenRetired = 80
    TcpRecvSegmentSize = 1460
    TcpSendSegmentSize = 1460
    TcpTimedWaitDelay = 30
    TcpUseRFC1122UrgentPointer = 0
    TcpWindowSize = 20440
    MaxConnectionsPer1_0Server = 10
    MaxConnectionsPerServer = 8
    DefaultTimeToLive = 64
    DefaultUserTOSSetting = 0
    TcpMaxDataRetransmissions = 6
    DefaultTOSValue = 90


    Also remember that the analyzer is only a tool to check your current reigistry settings, also post a speed test.


  15. #15
    Junior Member
    Join Date
    Apr 2000
    Location
    Ottawa, Ontario, Canada
    Posts
    17
    TCP/IP ANALYZER:
    ------------------------------------------------------------------------------------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) = 20440
    RWIN Scaling (RFC1323) = 0 bits
    Unscaled Receive Window = 20440

    RWIN is 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: 817.6 kbps (102.2 KBytes/s) @ 200ms
    Your RcvWindow limits you to: 327.04 kbps (40.88 KBytes/s) @ 500ms
    MTU Discovery (RFC1191) = ON
    Time to live left = 54 hops

    TTL value is ok.
    Timestamps (RFC1323) = OFF
    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 01011010

    Precedence (priority) = 010 (immediate)
    Delay = 1 (low delay)
    Throughput = 1 (high throughput)
    Reliability = 0 (normal reliability)
    Cost = 1 (low cost)
    ------------------------------------------------------------------------------------
    That's fully updated to what my CABLENUTS is... and for the test.
    ------------------------------------------------------------------------------------
    Speed test at NYC SPKZ.NET
    ------------------------------------------------------------------------------------
    >OTHER INFO ON MY LINE<
    ------------------------------------------------------------------------------------
    >LINE TEST<
    ------------------------------------------------------------------------------------
    Please please please please... keep in mind these tests were done at 2am my time, NO ONE IS ONLINE ... no one in my area at least.
    Thanks,
    -Anil
    Hi, I own two pairs of shoes.

  16. #16
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    Everything looks excellent, your caps are 1500 and your getting 1465, that's over 90%. Enjoy it, most people would be very jealous.


  17. #17
    Junior Member
    Join Date
    Apr 2000
    Location
    Ottawa, Ontario, Canada
    Posts
    17
    But... what I still don't understand is why I'm getting spikes. When I'm playing games, I checked all the game_net settings, and they haven't been changed ever since last summer (when all I received was 30ms pings) and now it's all different... I'm pretty damn sure rogers@home is up to something

    -Anil
    Hi, I own two pairs of shoes.

  18. #18
    Dr Tweak mnosteele52's Avatar
    Join Date
    Jul 2001
    Location
    Chesapeake, VA
    Posts
    11,912
    There is nothing you can do to tweak your latency, it is controlled by your ISP. It could be the servers you are connecting to playing the game, but in any case it is out of your control.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •