• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How's This For a T1 Connection?

olds

olds

Elite Member
I hooked my laptop up directly to our company router as I am getting slow speeds. Measuring with Net Stat Live, I achieved a single burst of 124.4 Kb and an average of 42.6 Kb. That is about ISDN speeds for the burst and 56K speeds for the average. I doubled checked it against Speed411.com and it measured it at 42 Kb.
Then, just for fun, I did a tracert and ping of www.ibm.com

Tracing route to www.ibm.com [129.42.18.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 10.160.221.254
2 5 ms 5 ms 6 ms 10.160.250.57
3 5 ms 5 ms 6 ms rthqinternet2.dot.ca.gov [64.174.7.6]
4 8 ms 8 ms 10 ms 206.13.19.165
5 17 ms 17 ms 16 ms bb1-g6-0.scrm01.pbi.net [64.171.152.247]
6 10 ms 9 ms 13 ms sl-gw25-stk-2-0.sprintlink.net [160.81.16.89]
7 9 ms 10 ms 12 ms sl-bb21-stk-8-1.sprintlink.net [144.232.4.225]
8 11 ms 14 ms 14 ms sl-bb22-sj-5-0.sprintlink.net [144.232.8.42]
9 17 ms 24 ms 17 ms 144.232.18.138
10 28 ms 28 ms 25 ms tbr1-p013601.sffca.ip.att.net [12.122.11.77]
11 60 ms 61 ms 64 ms tbr1-p013601.sl9mo.ip.att.net [12.122.11.109]
12 59 ms 69 ms 67 ms gbr5-p100.sl9mo.ip.att.net [12.122.11.106]
13 59 ms 65 ms 60 ms gar2-p360.sl9mo.ip.att.net [12.123.24.233]
14 81 ms 72 ms 73 ms 12.125.74.74
15 * * * Request timed out.
16 * * * Request timed out.
17 * *


Pinging www.ibm.com [129.42.17.99] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 129.42.17.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
I didn't know ibm didn't allow pings.
I am just trying to find out where my bottleneck is.
Pinging www.yahoo.akadns.net [66.218.71.84] with 32 bytes of data:
Reply from 66.218.71.84: bytes=32 time=12ms TTL=53
Reply from 66.218.71.84: bytes=32 time=14ms TTL=53
Reply from 66.218.71.84: bytes=32 time=12ms TTL=53
Reply from 66.218.71.84: bytes=32 time=16ms TTL=53
Ping statistics for 66.218.71.84:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 16ms, Average = 13ms
 


<< I didn't know ibm didn't allow pings. >>



Many sites dont. Microsoft doesnt. You just have to know who does (learned yahoo on the call floor for an isp a while back). 😉



<< I am just trying to find out where my bottleneck is. >>



Try downloading from various sites throughout the US and see what the speeds are. The bottleneck maynot be yours, it could be theirs.
 
It's mine. No matter which site I surf too, my speeds are in the 56K range. They just put in a new router and I went from 4Kb to the 42.6Kb. Last year I was hitting 800 -900 Kb, easy.
 


<< It's mine. No matter which site I surf too, my speeds are in the 56K range. They just put in a new router and I went from 4Kb to the 42.6Kb. Last year I was hitting 800 -900 Kb, easy. >>



You could always try complaining to the isp.
 
I did, all they say is that it's an old building. 150 feet away in the next building they are blazing. I guess the problem is not between the router and my desk as hooking up diretly to the router didn't help. Oh well. We'll have a new building in a couple of years. :Q
 
Sounds like BS. Pull out your contract and see what kind of service level agreements they gave you. And try downloading from sites closer to you to see if that improves the speed at all.
 
The pings seem to be inline for a T-1 but the bandwidth is low. What does a site like DSL Reports say about your connection. Also, it is the ISP's responsibiltiy that you get the bandwidth that you paid for. This is not a DSL or Cable connection that can vary. This is leased line connetion to the Internet and it should deliver as advertised
 
I haven't ran the test on DSL reports. I'll do it when I go back to work on Tuesday. I don't work on Fridays and Monday is a holiday. 😀
 
Are you sure it's a full T1 and not fractional? Is it Point-to-Point or frame relay? All that makes a difference.
 
It is a full T1. I was hitting 800 - 900 Kb last year. I don't know what Point-to-Point or frame relay is so I can't say on that part.
 
Point-to-Point is a direct leased line from you to your ISP. Frame Relay is your T1 going into your local telco's cloud and your circuit coming out at your ISP, usually on a T3 or higher pipe. Many companies opt for Frame Relay cause it usually is much cheaper - you contract for the minimum amount of bandwidth you want them to provide. Usually, you can contract for a guaranteed low amount and end up much higher bandwidth for free. Occasionally their cloud gets overloaded and you end up only getting what you are paying for.


 
Gee, sounds like the IT Admin deliberately is limiting bandwidth. Some companies pay for bandwidth by the data transferred. If you are 'browsing' the web, they may limit your bandwidth on purpose while reserving specific portions for critical and system uses (like directory replication, syncing and many other things)
 
what the CIR... or did U get one of those new "cheap" lines where they say tey dont provide a CIR cause U dont need it?
 
I don't know what a CIR is. I did find out that they are capping the 5 of us that share the T1 to 56K. Everyone claims ignorance when I ask why. They are "looking into it". :disgust:
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top