Author Topic: Need Help with Settings.  (Read 3261 times)

Offline mnosteele

  • Dr Tweak
  • Administrator Nut
  • Certifiable Nut
  • *****
  • Posts: 2353
  • Gender: Male
  • Dr Tweak
    • www.drtweak.com
Re:Need Help with Settings.
« Reply #7 on: September 27, 2002, 09:44:58 pm »
Your latency is great.... latency changes continuosly even rising as high as 500ms at times and there isn't much you can do about it. If yours is stable at 100-200ms that is good, mine averages anywhere from 90-140 while playing games. The afd buffers in Cablenut will help the most with lowering and stabilizing your latency. :) ;D
AMD Phenom II X4 Black Edition 3.2, WD Raptor 150GB, 8GB Crucial RAM, Win 7 Ultimate

Offline apmartin

  • A New Nut
  • *
  • Posts: 10
  • I'm a llama!
Re:Need Help with Settings.
« Reply #8 on: September 27, 2002, 10:35:58 pm »
I know this may sound dumb...but what are "afd buffers"?  :)

Offline mnosteele

  • Dr Tweak
  • Administrator Nut
  • Certifiable Nut
  • *****
  • Posts: 2353
  • Gender: Male
  • Dr Tweak
    • www.drtweak.com
Re:Need Help with Settings.
« Reply #9 on: September 27, 2002, 10:40:27 pm »
No doesn't sound dumb ;), just read the definitions of the settings here.

AFD - Ancillary Function Driver which, basically, acts as an entry point for Winsock functions to get to TCPIP.sys.
 ;D
« Last Edit: September 27, 2002, 10:40:46 pm by mnosteele »
AMD Phenom II X4 Black Edition 3.2, WD Raptor 150GB, 8GB Crucial RAM, Win 7 Ultimate

Offline apmartin

  • A New Nut
  • *
  • Posts: 10
  • I'm a llama!
Re:Need Help with Settings.
« Reply #10 on: September 27, 2002, 11:11:37 pm »
    I was reading on some other post that you told them to do a tracert to dslnuts.com.  I did two just to see what would happen and this is what I got.  I have no idea what it means and I was thinking that maybe you could tell me if it was good or bad.  Thanks


 1     5 ms     2 ms     2 ms  192.168.0.1
 2    63 ms    56 ms    67 ms  ip68-99-192-1.ph.ph.cox.net [68.99.192.1]
 3    57 ms    70 ms    61 ms  ip68-2-3-65.ph.ph.cox.net [68.2.3.65]
 4   121 ms    51 ms    63 ms  ip68-2-0-157.ph.ph.cox.net [68.2.0.157]
 5     *      105 ms   118 ms  chnddsrc02-gew0303.rd.ph.cox.net [68.2.14.13]
 6    49 ms    52 ms    50 ms  chndbbrc02-pos0101.rd.ph.cox.net [68.1.0.168]
 7    87 ms    77 ms    76 ms  dllsbbrc01-pos0102.rd.dl.cox.net [68.1.0.146]
 8   163 ms    99 ms    80 ms  12.119.145.125
 9    79 ms    59 ms    66 ms  gbr5-p30.dlstx.ip.att.net [12.123.17.50]
10    82 ms   146 ms    90 ms  tbr1-p012401.dlstx.ip.att.net [12.122.12.65]
11    68 ms   138 ms    82 ms  ggr1-p340.dlstx.ip.att.net [12.122.12.74]
12    77 ms    87 ms    70 ms  dal-brdr-02.inet.qwest.net [205.171.1.13]
13     *      139 ms   114 ms  dal-core-01.inet.qwest.net [205.171.25.45]
14    75 ms    98 ms    82 ms  dal-edge-07.inet.qwest.net [205.171.25.54]
15   125 ms   118 ms    66 ms  ci-dfw-OC12.cust.qwest.net [65.118.50.2]
16    72 ms   110 ms    60 ms  gige1.fire1.propagation.net [66.34.255.3]
17    70 ms    56 ms    66 ms  66.34.255.82
18    68 ms    69 ms   116 ms  66.34.156.231




 1     2 ms     2 ms     2 ms  192.168.0.1
 2   124 ms    53 ms    80 ms  ip68-99-192-1.ph.ph.cox.net [68.99.192.1]
 3    30 ms    80 ms    36 ms  ip68-2-3-65.ph.ph.cox.net [68.2.3.65]
 4    50 ms    68 ms    98 ms  ip68-2-0-157.ph.ph.cox.net [68.2.0.157]
 5   147 ms    31 ms    62 ms  chnddsrc02-gew0303.rd.ph.cox.net [68.2.14.13]
 6    47 ms    42 ms    29 ms  chndbbrc02-pos0101.rd.ph.cox.net [68.1.0.168]
 7    54 ms   126 ms   103 ms  dllsbbrc01-pos0102.rd.dl.cox.net [68.1.0.146]
 8     *       56 ms    62 ms  12.119.145.125
 9    84 ms    72 ms    62 ms  gbr5-p30.dlstx.ip.att.net [12.123.17.50]
10    68 ms    91 ms    83 ms  tbr1-p012401.dlstx.ip.att.net [12.122.12.65]
11    75 ms    78 ms   158 ms  ggr1-p340.dlstx.ip.att.net [12.122.12.74]
12    79 ms    63 ms    53 ms  dal-brdr-02.inet.qwest.net [205.171.1.13]
13    81 ms   128 ms    70 ms  dal-core-01.inet.qwest.net [205.171.25.45]
14    64 ms    54 ms    67 ms  dal-edge-07.inet.qwest.net [205.171.25.54]
15    59 ms    62 ms    69 ms  ci-dfw-OC12.cust.qwest.net [65.118.50.2]
16    80 ms    72 ms    59 ms  gige1.fire1.propagation.net [66.34.255.3]
17    45 ms   130 ms    68 ms  66.34.255.82
18    82 ms    70 ms    85 ms  66.34.156.231

Offline dannjr

  • Main Certifiable NutcAsE
  • Administrator Nut
  • Certifiable Nut
  • *****
  • Posts: 6342
  • Gender: Male
  • Share your life. Be a organ donor other Bday 1998
    • DSLnuts | Broadbandnuts | Cablenut
Re:Need Help with Settings.
« Reply #11 on: September 28, 2002, 02:25:16 am »
The time outs can be normal in some cases.. In these the time outs are on cox where there might be a bottle neck of heavy traffic.. If the tracerts had been taken with cable between 9pm and 1am you can get that on a Friday or Tuesday generally the busy part of the week this time of year..
If you get high reading like 100ms here at the site it just means its getting busy.

The hard sell to the cable company on the time outs is that if your not above 500ms your not having problems..

To me 500ms you may as well be on dialup.. But thats me..

Now where you hit quest on there is the uplink for dslnuts right at Dalas TX. You can see how busy that one is.. Theres over 20000 connections running right there.. Most servers hold 250 web sites plus you have dedicated servers and quest as a ISP in general.. Dont worrie quest aint the only connection in... I hope that helped
Be a Organ Donor. A chance at life.
This site never spams or sells its list to anyone. No pop up's or scams
An inconvenience, but if you want to make omelettes, you have to break some eggs.