Inquisitor
-
Posts
57 -
Joined
-
Last visited
Never -
Speed Test
My Results
Posts posted by Inquisitor
-
-
Trust means everything to me, as I'm an extremely honest individual. I don't appreciate being questioned, but I understand that most people are unworthy of having faith placed in them.
-
I know this is a fluke. I can pretend it's for real though, can't I?
Here are the results from those two links:
:::.. Download Stats ..:::
Connection is:: 34090 Kbps about 34.1 Mbps (tested with 12160 kB)
Download Speed is:: 4161 kB/s
Tested From:: https://testmy.net/ (server1)
Test Time:: Mon Aug 22 01:31:23 EDT 2005
Bottom Line:: 609X faster than 56K 1MB download in 0.25 sec
Diagnosis: Awesome! 20% + : 845.37 % faster than the average for host
:::.. Download Stats ..:::
Connection is:: 41942 Kbps about 41.9 Mbps (tested with 12160 kB)
Download Speed is:: 5120 kB/s
Tested From:: https://testmy.net/ (server2)
Test Time:: Mon Aug 22 01:32:41 EDT 2005
Bottom Line:: 749X faster than 56K 1MB download in 0.2 sec
Diagnosis: Awesome! 20% + : 1026.56 % faster than the average for host
-
After deleting cache:
:::.. Download Stats ..:::
Connection is:: 43085 Kbps about 43.1 Mbps (tested with 12160 kB)
Download Speed is:: 5259 kB/s
Tested From:: https://testmy.net/ (server1)
Test Time:: Mon Aug 22 00:58:14 EDT 2005
Bottom Line:: 769X faster than 56K 1MB download in 0.19 sec
Diagnosis: Awesome! 20% + : 1126.79 % faster than the average for host
So, does anyone know what's going on? Not that I dislike such speeds.
-
:::.. Download Stats ..:::
Connection is:: 45547 Kbps about 45.5 Mbps (tested with 12160 kB)
Download Speed is:: 5560 kB/s
Tested From:: https://testmy.net/ (server1)
Test Time:: Mon Aug 22 00:24:19 EDT 2005
Bottom Line:: 813X faster than 56K 1MB download in 0.18 sec
Diagnosis: Awesome! 20% + : 1421.28 % faster than the average for host
Now that's what I'm talking about.
-
The reason I knew something would probably go wrong, is certainly not because of anything you did. It's the result of having previous problems when tampering with the settings. Perhaps this ISP isn't very receptive to it; I've no idea why.
In any event, this is after I went back to default windows settings:
http://ttester.broadbandreports.com/tweak/block:51f48d2?service=cable&speed=3500&os=winXP&via=normal
I've been 'unpingable' for quite awhile -- is that something usually seen, or an indication something's wrong?
BTW, it's nice to know I'm not the only night owl.
Also, fantastic job with the forums, Cable. Been awhile since I posted. This site is looking nice.
-
I knew something would probably go wrong.
Before I used the 3500/384 settings you provide for Cablenut:
Connection is:: 3366 Kbps about 3.4 Mbps (tested with 2992 KB)
Download Speed is:: 411 KB/s
After:
Connection is:: 2862 Kbps about 2.9 Mbps (tested with 2992 KB)
Download Speed is:: 349 KB/s
The latter results were consistent over many tests. Any idea what went wrong?
-
SB5100
I've never had problems connecting or anything, so I assume it's not a big deal. Also, the cap was set back to 2.0 mbps. The reason it took longer, he said, was because the TFTP server wasn't started properly.
Anyhow, I've always wondered why the logs looked like that, with all the 'critical' errors and 'failed to acquire' responses
-
$45 a month, for 1.5 mbps (advertised as 2.0 mbps)
They can do this, only because there's essentially no competition. If there's a hint that Cox, or whomever, is coming to town, I guarantee their service will improve. To no avail, because I'd sign up with Cox immediately.
-
They must have competition. Otherwise, these prick companies will keep it as low as they can while trying to steal as much money as possible.
-
Check this out:
1970-01-01 00:00:27 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:17 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:10 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:41 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:14 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:14 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:14 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-01 00:00:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:16 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2004-08-10 18:35:00 3-Critical 0x04E33B3C Unicast Ranging Received Abort Response - Re- initializing MAC
2004-08-10 12:42:59 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2004-08-10 12:42:57 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response
2004-08-10 12:42:27 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received
2004-08-10 12:42:17 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2004-08-10 12:41:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:16 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:41:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:41:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:43 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2004-08-10 12:40:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2004-08-10 12:40:05 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2004-08-10 12:40:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2004-08-10 11:59:37 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2004-08-10 11:59:28 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2004-08-10 11:59:28 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2004-08-10 11:59:20 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2004-08-10 11:59:20 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2004-08-10 11:59:13 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2004-08-10 11:59:13 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2004-08-10 11:59:04 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
In addition, I got this bullshit e-mail from a system administrator, who says he accidentally set the configuration file from 2.0 to 1.5. Now, he says it's been returned to 2.0, all you have to do is power cycle the modem -- done it, and it's still 1.5.
-
Concerning D-Link, their website states that they're "the #1 Wireless provider in Europe and China." That's pretty bad, if the Chinese get this technology ahead of North America. Not a good sign.
-
The likely cause, is a new configuration file.
All glory to uncappers. (within reason.. just to get what you pay for)
-
PPPoE connection?
You've certainly nothing to complain about. You're in the 99% percentile, when it comes to bandwidth.
-
Game developers haven't even been able to max out the Radeon 9700. Meaning there's little incentive to buy these two cards, unless you're rich or crazy.
-
That likely won't happen until the connection drops below 1.2. The customer rep., said they consider anything above 1.2 (on their 'up to 2 mbps service), to be 'acceptable'.
The 3.5 mbps service, is $70.
-
Line booster? Can you shed some more light on that topic for me, Swimmer? Are you speaking of some sort of line overload? Perhaps too many people on one node?
The bandwidth is pretty steady, around 1.4; that leads me to believe it's either a configuration file, or a crowded node.
-
What's the advertised speed you should be getting, microwave? Here, they promote an 'up to 2 mbps' service -- I get 1.4.
-
Hey Lorne, Well iv'e done just about everything possible to increase my speed, guess ill be happy at 3.5-3.7mbps. Im using a router and just wondering if there are any tweaks or settings that can be changed to increase the speed. Thanx......
Be more than hesitantly happy about 3.6 mbps. That's a fantastic connection. If it ever got worse, you'd realize that.
-
All I know is, when the cable company made the switch from SB3100 to SB5100 (always on), my bandwidth increased from 2, to around 4.2. After three weeks, it reverted back to 1.9; and a week later, to 1.4.
I mentioned this to the cable company, they sent people out, and had no explanation for the decline. (that they were willing to admit) I suspect it's either a new configuration file, or they're filling the nodes to capacity.
-
What are you paying for your service, bdodom? That's a superb connection.
-
I've tried everything. What it boils down to, is external factors. It's either a new configuration file, or a problem with the line itself. I suppose I enjoyed the 800kb bursts, and 450kb/sec downloads, while I had it.
-
Consider yourself fortunate.
I'm learning to manage with this lousy service.
::: Download Stats :::
Connection is: 1589 Kbps about 1.6 Mbps (tested with 579 KB)
Download Speed is: 194 KB/sec
Auth Code: 2023836 (validate at http://www.testmy.net)
Bottom Line: 28 times faster than 56K you can download 1MB in 5.28 second(s)
Validation Link :: https://testmy.net/cgi-bin/auth_check.cgi?ta=&top=&align=&num=2023836&kbps=1589&gen=gen&a=4.57142857142857&b=1.71428571428571&c=1145.14285714286
-
Hi, disturbed..
What's your RWIN / MTU settings?
I, too, got 2 mbps over the advertised speed. (around 4.3) However, they sent out new config files, or something, and now it's at around 1.4-1.5.
-
Your results are fake.
Hilarious Results
in Show off your speed
Posted
Inquisitor: Running Norton AV? Kill it.
No Norton. It was strange, but it wasn't my bandwidth I'm fairly certain. Nor was it a cached result. There was no cache on my end, and it happened on consecutive days.