i have to redial everytime to get 300++ms IP
if not my online game lag like hell

wat happen
suddenly surfing became so slow?

it just happened las nite at 10pm all of a sudden cant connect to streamyx
this morning 6am can connect but getting timeout often
surfing and gaming is a totally disaster now
anyone facing this problem

this morning 9 am i try to connect
walla i get a ping 230ms to yahoo website
i play online game smoothly
but have to go for class
so it seems to be some IP range is not affected
some other IP gave me 500 - 600ms to yahoo
n guess wat today no timeout at all
i think is recovering slowly but not much at least no timeout is enough for me if not the page will take very long to load and wont load at all

is mine ok?
should i ask the technician to change G.DMT to T1.413?
and how come my modem not responding after a period of time using it
i have to off and on back the modem which is troublesome for everytime
mine is D-Link 500G i think its the firmware problem?
anyone have the latest firmware to solve this hang problem

getting IP 60.50.XX.XX range all 500++ ms ping to www.yahoo.com
IP 60.53.XX.XX can get 200++ or 300++ ms ping
IP 60.52.XX.XX some IP only have to redial many times to get 300++ ms ping
IP 124.XX.XX.XX lag from las nite 10pm onwards

just now i ping at 500++ms
suddenly become like this
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\system32>ping www.yahoo.com

Pinging www.yahoo-ht2.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=250ms TTL=45
Reply from 209.131.36.158: bytes=32 time=249ms TTL=45
Reply from 209.131.36.158: bytes=32 time=252ms TTL=46
Reply from 209.131.36.158: bytes=32 time=251ms TTL=46

Ping statistics for 209.131.36.158:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 249ms, Maximum = 252ms, Average = 250ms

C:\WINDOWS\system32>ping www.yahoo.com

Pinging www.yahoo-ht2.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=249ms TTL=45
Reply from 209.131.36.158: bytes=32 time=250ms TTL=45
Reply from 209.131.36.158: bytes=32 time=250ms TTL=45
Reply from 209.131.36.158: bytes=32 time=250ms TTL=45

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

This post has been edited by [W]HIT3_@NG3L: Mar 18 2007, 08:06 AM

why is streamyx acting slow and slower after day by day?
yesterday was slow today is worst

thats what im facing with IP 60.53.XX.XX and 124.82.XX.XX
IP 60.50.XX.XX no time out but high ping as much as 500++ms to www.yahoo.com
other IP number please report if there is high ping or time out

reconnect fee?

im feeling the dialup speed now yay!

wow corporate IP?
weird i saw my school corporate package IP is 60.51.XX.XX

don't ask us
nobody knows why
we all also facing slow speed not only you
yet tmnut still says is your side problem not our side

This post has been edited by [W]HIT3_@NG3L: Mar 23 2007, 10:48 PM

still no news from tmnut website
another earthquake?

still having timeout in ping

certain IP have good speeds
for me 60.50.XX.XX all is high ping but no timeout (slow speed)
60.53.XX.XX and 124.82.XX.XX has very low ping but a lot timeout (fast speed)
so choose which one u want

how do i change the mode to G.Lite like yours above?

is it based on the mode set on my DSLAM?
lets say mine is G.DMT so i set to G.DMT?
or if i set to G.LITE it will change to G.LITE at DSLAM?
btw if something screwed how to change back to multimode?
reset factory default settings?

there's an earthquake in japan
so tmnut gonna blame earthquake again
or their engineer's hand are itchy so go play play with the international link

---

Added on March 26, 2007, 10:50 pmthe exchange is not far from my house

This post has been edited by [W]HIT3_@NG3L: Mar 26 2007, 10:50 PM

after 2 weeks of dial-up slowmyx speed their engineers only realize
"Oh i feel the speed is a bit slow"

its just their lame excuse blaming the cable problem
which the main problem is their so call"Enough Backbone Server" which in the reality it's not enough at all
i bet if the problem is solved there comes another problem

This post has been edited by [W]HIT3_@NG3L: Mar 30 2007, 02:00 PM