Lag

[DeputyDog]

Well after some tests I have come to the conclusion that the problem is either my modem or the line. We have had rain here for the last week and today and tomorrow and the next day we are frozen over here in Austin. So of course the city shuts down, cuz we southern folk dont know nuttin bout dat der ice.

This is what it is doing. Every few seconds it will lose signal or drop all packets.

DOes the same with and without router on any machine.
C:\Documents and Settings\Gabriel>ping http://www.suddenlink.net /t

Pinging http://www.suddenlink.net [208.180.42.11] with 32 bytes of data:

Reply from 208.180.42.11: bytes=32 time=50ms TTL=248
Reply from 208.180.42.11: bytes=32 time=42ms TTL=248
Reply from 208.180.42.11: bytes=32 time=47ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=41ms TTL=248
Reply from 208.180.42.11: bytes=32 time=30ms TTL=248
Reply from 208.180.42.11: bytes=32 time=37ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=32ms TTL=248
Reply from 208.180.42.11: bytes=32 time=48ms TTL=248
Reply from 208.180.42.11: bytes=32 time=37ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=37ms TTL=248
Reply from 208.180.42.11: bytes=32 time=46ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=40ms TTL=248
Reply from 208.180.42.11: bytes=32 time=40ms TTL=248
Reply from 208.180.42.11: bytes=32 time=41ms TTL=248
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=42ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=39ms TTL=248
Reply from 208.180.42.11: bytes=32 time=39ms TTL=248
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=40ms TTL=248
Reply from 208.180.42.11: bytes=32 time=47ms TTL=248
Reply from 208.180.42.11: bytes=32 time=52ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=32ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=39ms TTL=248
Reply from 208.180.42.11: bytes=32 time=42ms TTL=248
Reply from 208.180.42.11: bytes=32 time=38ms TTL=248
Reply from 208.180.42.11: bytes=32 time=45ms TTL=248
Reply from 208.180.42.11: bytes=32 time=32ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=37ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11: bytes=32 time=44ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=34ms TTL=248
Reply from 208.180.42.11: bytes=32 time=47ms TTL=248
Reply from 208.180.42.11: bytes=32 time=43ms TTL=248
Reply from 208.180.42.11: bytes=32 time=35ms TTL=248
Reply from 208.180.42.11: bytes=32 time=36ms TTL=248
Request timed out.
Reply from 208.180.42.11: bytes=32 time=33ms TTL=248
Reply from 208.180.42.11:

--

Cant contact them for a few days becuase of everyone else contacting them and people cant get to work.

Ill get it delt with once we thaw and either get a new modem or get the line tested.

Stay tuned.

[Kirg]

IP changed to 60001 again, and with it the bad lag is back. The mobs dance happily around us, while we try to chuck some pot .

[Nolan Silvermoon]

yup, i noticed the ip change, and yup, the dreaded lag monster has reared its ugly head again

[Mythri Wolfwood]

When I tried logging on using the address with the 60001 port, it said the server was found, but I timed out. However, when logging in using the address with the 5121 port, I get in right away.

UPDATE: I can no longer log in using the address with the 5121 port. A full remote server reset was made about an hour ago, however, the lag still remains.