Mirc IRC error [10053] Software caused connection abort during work hours on ADSL

Migs

Well-Known Member
Joined
Aug 25, 2007
Messages
448
Reaction score
4
Hello all.

For awhile now, I can't stay connected to IRC for more than 7 minutes when there is no activity going on (no chatting, downloading files etc).

The strange thing is this only happens during work hours Monday to Friday - 9am to 6pm.

Here is some extra info that may help you all helping me out :)

Router: Billion BiPAC 7402R2 (ADSL Router)
Hardware Version Argon 432 ADSL-A/2 v1.00
Software Version 5.07
(I hope that I don't need to update the firmware)

Pinging irc.shadowfire.org [66.220.1.52] with 32 bytes of data:

Reply from 66.220.1.52: bytes=32 time=377ms TTL=53
Reply from 66.220.1.52: bytes=32 time=373ms TTL=53
Reply from 66.220.1.52: bytes=32 time=390ms TTL=53
Reply from 66.220.1.52: bytes=32 time=384ms TTL=53

Ping statistics for 66.220.1.52:
Packets: Sent = 4, Received = 4, Lost = 0 (o% loss)
Approximate round trip times in milli-seconds:
Minimum = 373ms, Maximum = 390ms, Average = 381ms


Tracing route to irc.shadowfire.org [66.220.1.52] over a maximum of 30 hops:

01 <1ms <1ms <1ms home.gateway [192.168.99.1]
02 48ms 39ms 39ms dsl-245-0-01.telkomadsl.co.za [**censored by me**]
03 * * * Request times out.
04 * * * Request times out.
05 49ms 49ms 38ms 196.43.10.130
06 40ms 39ms 38ms 196.43.33.5
07 403ms 397ms 399ms ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [196.43.18.30]
08 398ms 400ms 397ms pos2-0.cr02.ash01.pccwbtn.net [63.218.94.17]
09 403ms 409ms 402ms equinix-ash.he.net [206.223.115.37]
10 398ms 398ms 391ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
11 398ms 389ms 383ms 10gigabitethernet1-2.core1.fmt1.he.net [66.160.158.241]
12 396ms 384ms 369ms kalfu.slipgate.za.net [66.220.1.52]

Trace complete

If you need anymore info, please ask.

Thanks in advance

Regards
Migs
 
Last edited:
ping ftp.is.co.za -t for like an hour. 4 results is not a good indication of line quality, and more just of latency.

Post the results here of an hours ping. Also keep an eye out for disconnects and stuff.

Also try za.shadowfire.org instead of an international one.
 
I'm using 192.14.172.105 aka za.shadowfire.org and it logs in very quickly. Not close to 30 seconds like with irc.shadowfire.org.

Will try out w1z4rd's idea in the mean time.

Thank you for the helpful ideas so far guys!
 
By the way, thanks for the very quick response time w1z4rd and PostmanPot.
 
w1z4rd, after an hour and 6 minutes, the ping ftp.is.co.za -t is still going strong.
alot more than 4 results, heh.
 
Top
Sign up to the MyBroadband newsletter
X