[woodyear99]

I get pings of 50 - 70 ms to www.tstt.net.tt
This seems very high to me, is there anything I can do? Will calling tstt just add to my frustration? I find it is high as it seems to add lag to any online games I play......ne1 had this sort of problem with bad pings to tstt's servers?

[Terabyte]

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator.TERA01>ping www.tstt.net.tt

Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:

Reply from 196.3.132.8: bytes=32 time=28ms TTL=123
Reply from 196.3.132.8: bytes=32 time=24ms TTL=123
Reply from 196.3.132.8: bytes=32 time=24ms TTL=123
Reply from 196.3.132.8: bytes=32 time=25ms TTL=123

Ping statistics for 196.3.132.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 28ms, Average = 25ms

C:\Documents and Settings\Administrator.TERA01>


Seems like you got some problem there......I'm on a laptop connected to a desktop via ad-hoc wireless ....desktop connected to tstt through speedstream 5200

[Razzzhead]

Try PATHPING tstt.net.tt instead. That will give you the ping time for each hop along the route.

I too am getting a time of ~90 ms to tstt.net.tt using the PING command, but it looks like my DSL connection is flakey. Using Pathping, you can see below times of 124 ms between my SpeedStream DSL modem and tservq.tstt.net.tt (hop 3), which is the first hop in the chain along the phone wire.

---------------------------------------------------------------------------------
C:\>PATHPING tstt.net.tt

Tracing route to tstt.net.tt [196.3.132.8]
over a maximum of 30 hops:
0 MYPC [192.168.0.100]
1 D-Link.DI624.Router [192.168.0.1]
2 SpeedStream.Modem [192.168.254.254]
3 tservq.tstt.net.tt [209.94.205.25]
4 route.tstt.net.tt [209.94.205.6]
5 209.94.205.65
6 ns8.tstt.net.tt [196.3.132.8]

Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MYPC [192.168.0.100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% D-Link.DI624.Router [192.168.0.1]

0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% SpeedStream.Modem [192.168.254.254]
0/ 100 = 0% |
3 124ms 0/ 100 = 0% 0/ 100 = 0% tservq.tstt.net.tt [209.94.205.25]

0/ 100 = 0% |
4 124ms 0/ 100 = 0% 0/ 100 = 0% route.tstt.net.tt [209.94.205.6]
0/ 100 = 0% |
5 133ms 0/ 100 = 0% 0/ 100 = 0% 209.94.205.65
100/ 100 =100% |
6 --- 100/ 100 =100% 0/ 100 = 0% ns8.tstt.net.tt [196.3.132.8]

Trace complete.

-------------------------------------------------------------------------------------------

Try it and report back.

Quote

Will calling tstt just add to my frustration?

I've been complaining about the lousy connection since February dread. I might as well have talked to the dog. The Internet Help Desk are as much use as an ashtray on a motorbike.

[woodyear99]

Do you get the 256k speeds?

[Razzzhead]

The modem Tx rate gets set at 192 kbps rather than the advertised 256 kbps, but using the speed test, the best I get is ~155 kbps. Speed/money ratio is bordering on fraud.....

[woodyear99]

I get the 256k it is just poor pings...guess ur gonna have to keep calling and complaining about bandwidth...

this is the lowest I ever get, only after midnight...... good u think?

Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 woody [192.168.0.4]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 192.168.254.1
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.254.254
0/ 100 = 0% |
3 33ms 0/ 100 = 0% 0/ 100 = 0% tservq.tstt.net.tt [209.94.205.25]

0/ 100 = 0% |
4 33ms 0/ 100 = 0% 0/ 100 = 0% cuscon16446.tstt.net.tt [196.3.140
.237]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% route.tstt.net.tt [209.94.205.6]
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% 209.94.205.65
0/ 100 = 0% |
7 36ms 0/ 100 = 0% 0/ 100 = 0% ns8.tstt.net.tt [196.3.132.8]

Trace complete.

[Razzzhead]

That after midnight result would seem reasonable. Try the Line Packet Loss Testing at http://www.broadbandreports.com. You can see the latency of both up and down links, and which routers are lossy.

[Wolfie]

Pinging tstt.net.tt [196.3.132.8] with 32 bytes of data:

Reply from 196.3.132.8: bytes=32 time=73ms TTL=123
Reply from 196.3.132.8: bytes=32 time=77ms TTL=123
Reply from 196.3.132.8: bytes=32 time=33ms TTL=123
Reply from 196.3.132.8: bytes=32 time=42ms TTL=123
Reply from 196.3.132.8: bytes=32 time=39ms TTL=123
Reply from 196.3.132.8: bytes=32 time=34ms TTL=123
Reply from 196.3.132.8: bytes=32 time=38ms TTL=123
Reply from 196.3.132.8: bytes=32 time=53ms TTL=123
Reply from 196.3.132.8: bytes=32 time=41ms TTL=123
Reply from 196.3.132.8: bytes=32 time=62ms TTL=123

Ping statistics for 196.3.132.8:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 77ms, Average = 49ms

I don't think that's very good for an internal network ping.

[woodyear99]

Wolfie what are ur tstt.net.tt pings at night?

[woodyear99]

I wonder if it could be because of my speedstream modem?

Does that alcatel let you use ethernet?

[woodyear99]

Yeah I know, if I have anything else running like a simple web browser between different pages my pings skyrocket which is not cool