![]() |
Too many connections!!!
I have started using Shareaza, its ok sometimes. I think i have caused a DoS on my own connection and too myself by setting the number of transfers, files and files per transfer too high although I'n not sure what they where. I was trying different settings to maximise throughput(download) and something happend i don't understand.
Basically the transfer monitor in Shareaza was showing very low transfer rates (relative) and the u/s was maxed out causing loss of connectivity to everything - other than whatever it was doing. My netstat. This isnt the full table, its minus the standard stuff you always see above and below the active conections: TCP m081e:1027 localhost:2616 ESTABLISHED TCP m081e:1048 m081e:0 LISTENING TCP m081e:2616 localhost:1027 ESTABLISHED TCP m081e:netbios-ssn m081e:0 LISTENING TCP m081e:1280 ANice-106-1-16-116.w81-49.abo.wanadoo.fr:20887 CLOSING TCP m081e:2139 H219-192.COLONIAL.RESNET.ALBANY.EDU:6346 CLOSING TCP m081e:2200 38.118.155.4:6346 LAST_ACK TCP m081e:2242 client80-83-32-163.abo.net2000.ch:20214 LAST_ACK TCP m081e:2314 brune-2-81-57-236-13.fbx.proxad.net:6346 FIN_WAIT_1 TCP m081e:2410 24.194.92.251:6346 LAST_ACK TCP m081e:2414 24.238.79.219:36291 LAST_ACK TCP m081e:2426 62.218.214.28:24409 FIN_WAIT_1 TCP m081e:2468 npn18.ee.cooper.edu:40230 LAST_ACK TCP m081e:2469 ACB87A49.ipt.aol.com:20589 CLOSING TCP m081e:2507 f199082.upc-f.chello.nl:6346 FIN_WAIT_1 TCP m081e:2530 h68-146-243-216.cg.shawcable.net:23724 LAST_ACK TCP m081e:2562 p213.54.146.246.tisdip.tiscali.de:36256 FIN_WAIT_1 TCP m081e:2576 isu135061.ilstu.edu:23362 FIN_WAIT_1 TCP m081e:2578 38.118.163.200:6346 ESTABLISHED TCP m081e:2579 c-67-163-114-66.client.comcast.net:6346 FIN_WAIT_1 TCP m081e:2580 d213-103-206-17.cust.tele2.fr:30841 LAST_ACK TCP m081e:2593 bb-203-125-64-153.singnet.com.sg:6346 FIN_WAIT_1 TCP m081e:2594 67.128.181.54:36014 FIN_WAIT_1 TCP m081e:2596 218.14.222.30:17891 FIN_WAIT_1 TCP m081e:2599 lns-p19-3-62-147-144-167.adsl.proxad.net:13110 LAST_ACK TCP m081e:2601 cm-24-121-3-139.lakehavasu.az.npgco.com:19630 CLOSING TCP m081e:2608 82-44-211-75.cable.ubr09.haye.blueyonder.co.uk:6346 FIN_WAIT_1 TCP m081e:2617 pD954EBD6.dip.t-dialin.net:http ESTABLISHED TCP m081e:2633 ACBC2219.ipt.aol.com:19172 ESTABLISHED TCP m081e:2634 AClermont-Ferrand-201-1-3-82.w80-15.abo.wanadoo.fr:29022 ESTABLISH TCP m081e:2651 bb220-255-44-20.singnet.com.sg:6658 LAST_ACK TCP m081e:2652 h24-77-210-166.wp.shawcable.net:6346 ESTABLISHED TCP m081e:2653 host-48-237-220-24.midco.net:23382 SYN_SENT TCP m081e:2654 dyn-83-154-145-40.ppp.tiscali.fr:16617 SYN_SENT TCP m081e:2655 wiley-198-128414.roadrunner.nf.net:30135 SYN_SENT TCP m081e:2656 ool-44c2aa4c.dyn.optonline.net:51736 SYN_SENT TCP m081e:2657 cm61-10-123-150.hkcable.com.hk:35415 SYN_SENT TCP m081e:2658 24-119-49-83.cpe.cableone.net:51736 SYN_SENT TCP m081e:2660 ip68-108-61-153.lv.lv.cox.net:51736 SYN_SENT TCP m081e:2661 roc-68-172-134-188.rochester.rr.com:26134 SYN_SENT TCP m081e:2662 ejnorton.demon.co.uk:41471 SYN_SENT TCP m081e:2663 219.233.72.37:15220 SYN_SENT TCP m081e:2664 80.81.117.29:39495 SYN_SENT TCP m081e:2665 eu191-224.clientes.euskaltel.es:38100 SYN_SENT TCP m081e:2666 p213.54.241.6.tisdip.tiscali.de:21552 SYN_SENT TCP m081e:2667 ALagny-109-1-4-73.w81-49.abo.wanadoo.fr:24677 SYN_SENT TCP m081e:2668 n219077216104.netvigator.com:14121 SYN_SENT TCP m081e:2669 61.18.163.68:30570 SYN_SENT TCP m081e:2670 217.85.142.158:33308 SYN_SENT TCP m081e:3340 204.212.236.42:6346 CLOSING TCP m081e:4054 217.228.231.150:6346 CLOSING TCP m081e:6347 4.10.170.232:4526 FIN_WAIT_1 TCP m081e:6347 12.220.133.59:2037 ESTABLISHED TCP m081e:6347 24.6.214.25:3037 LAST_ACK TCP m081e:6347 24.9.74.27:1643 TIME_WAIT TCP m081e:6347 24.43.6.225:1686 ESTABLISHED TCP m081e:6347 24.79.218.192:4835 TIME_WAIT TCP m081e:6347 24.166.186.250:2721 TIME_WAIT TCP m081e:6347 24.200.82.132:64948 ESTABLISHED TCP m081e:6347 61.15.251.26:1386 ESTABLISHED TCP m081e:6347 61.59.60.136:3126 FIN_WAIT_1 TCP m081e:6347 61.93.37.50:4566 CLOSING TCP m081e:6347 61.121.78.223:1053 SYN_RECEIVED TCP m081e:6347 62.25.239.123:4428 ESTABLISHED TCP m081e:6347 62.57.80.213:2512 CLOSING TCP m081e:6347 62.147.171.239:4102 CLOSING TCP m081e:6347 64.230.46.117:4483 LAST_ACK TCP m081e:6347 64.238.168.232:4870 SYN_RECEIVED TCP m081e:6347 66.119.197.143:4775 CLOSING TCP m081e:6347 66.235.58.193:4185 ESTABLISHED TCP m081e:6347 67.68.188.56:60436 ESTABLISHED TCP m081e:6347 68.81.152.36:3959 ESTABLISHED TCP m081e:6347 68.204.149.48:65320 TIME_WAIT TCP m081e:6347 80.3.132.133:1166 FIN_WAIT_1 TCP m081e:6347 80.59.131.115:24239 ESTABLISHED TCP m081e:6347 80.221.211.185:34757 ESTABLISHED TCP m081e:6347 80.223.238.92:3597 LAST_ACK TCP m081e:6347 81.57.251.30:1378 ESTABLISHED TCP m081e:6347 81.80.128.14:58277 LAST_ACK TCP m081e:6347 81.86.202.89:3957 SYN_RECEIVED TCP m081e:6347 81.109.195.54:3564 CLOSING TCP m081e:6347 82.48.64.137:3277 SYN_RECEIVED TCP m081e:6347 82.64.134.91:1938 ESTABLISHED TCP m081e:6347 82.65.26.218:4609 LAST_ACK TCP m081e:6347 82.83.171.132:3291 ESTABLISHED TCP m081e:6347 82.182.90.148:20534 LAST_ACK TCP m081e:6347 82.217.191.59:4873 ESTABLISHED TCP m081e:6347 168.226.70.198:2080 ESTABLISHED TCP m081e:6347 172.177.233.251:2209 CLOSING TCP m081e:6347 172.178.214.79:4047 FIN_WAIT_1 TCP m081e:6347 193.253.46.106:4769 ESTABLISHED TCP m081e:6347 194.204.28.200:1025 LAST_ACK TCP m081e:6347 205.160.48.213:1321 LAST_ACK TCP m081e:6347 207.38.196.187:1990 ESTABLISHED TCP m081e:6347 210.50.87.15:3796 ESTABLISHED TCP m081e:6347 212.194.126.181:49535 SYN_RECEIVED TCP m081e:6347 212.194.244.160:3862 ESTABLISHED TCP m081e:6347 213.23.62.164:34716 ESTABLISHED TCP m081e:6347 213.39.167.221:4936 CLOSING TCP m081e:6347 213.149.96.9:1293 FIN_WAIT_1 TCP m081e:6347 213.173.75.69:3516 ESTABLISHED TCP m081e:6347 213.209.71.152:3739 LAST_ACK TCP m081e:6347 217.44.176.22:4914 ESTABLISHED TCP m081e:6347 217.83.137.239:4071 LAST_ACK TCP m081e:6347 217.97.72.93:3967 ESTABLISHED TCP m081e:6347 217.164.76.111:1458 CLOSING TCP m081e:6347 217.187.81.165:4259 FIN_WAIT_1 TCP m081e:6347 217.236.1.243:32998 ESTABLISHED TCP m081e:6347 218.191.51.100:3631 LAST_ACK TCP m081e:6347 220.139.149.91:4960 ESTABLISHED Port 6347 is the port used for Shareaza. I'm not sure about the 2* port numbers. At the time upstream was leaving this machine at max (32kBps) and a similar speed on d/l. Shareaza showed u/s and d/s speeds of 14kBps (ish). Hmmm, way off. When i closed Shareaza the transfers stopped and the connections closed. FYI: I'm running Norton Internet Security '02 and behind a NAT forwarding 6347 to m081e. I dont uderstand p2p much or the networks they operate on but it would be nice to understand why this happend so i can avoid in the future and configure properly. Cheers guys, John :) |
Re: Too many connections!!!
Quote:
|
Re: Too many connections!!!
put your upload on 80% of your max upload speed (mine lives on about 20 under emule/overnet)
if your on the 1 meg like me put your max connections down abit. Look to see if your router has known issues with many connections emule/overnet are know to overload a few routers i imagine Shareaza is the same as it can connect to the edonkey network. as it connects to something like 4 networks i imagine its very bus all the time, i wouldnt use it my self but all depends what you want to d/l if your after torrent links use shadows experimental client or the abc mod if yoru after files on the edonkey network use overnet or emule/emule-kad all depends what sort of files ur after |
Re: Too many connections!!!
Good to see people using Shareaza. :tu:
Remember that Shareaza is basically the same as eMule so you won't get downloads at full speed very often, it's an app that should be left for a few days to complete the downloads. |
Re: Too many connections!!!
the donkey network and its spin off server less networks are never meant for fast d/ls mines been running 109 days non stop and i aint finished some files ;) done about 980 gig mind..overnet seems to be fastest (i tested a lot) for certain popular releases
|
| All times are GMT. The time now is 23:19. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum