File_pile
November 3rd, 2002, 01:20 PM
Hi all!
I'm only a couple of weeks into using WinMX (my first file-sharing program) and was wondering if anyone has some answers for a few questions I have regarding how it works.
I too have had pretty poor upload/download speeds on occasion and today got flat-out disconnected from the network. While I have WinMX up everything internet-related gets really bogged down for me, even though I may not be downloading anything and my uploads are maxxing out at 4k/s total. I began getting concerned that something was running in the background that I was unaware of, so I used the software with my router (linksys) to monitor the incoming and outgoing logs for suspicious activity.
I have a CABLE connection and connect to WinMX via a PRIMARY connection, and have opened 2 ports (not the default ones for MX) for tcp and udp access.
What I did:
After a couple of days of consistantly excrutiatingly slow downloads, and embarrassing uploads, I closed MX and opened up my connection log to see what ip's where hitting what.
Thankfully, with MX closed and no active net usage on my part, my outgoing log remained static (so I feel better about there not being something in my background that's broadcasting on me and hogging bandwidth).
My incoming log, however, told a very different story. For the next 4 hours, I kept getting hits on my tcp port that I had dedicated to MX every 5-10 mins or so (in addition to some random hits on different ports). Some of the IP addresses would repeat the action to me a couple of times, others only once.
I understand the structure of the peer-to-peer network for the most part, but why do I keep getting these hits long after MX is closed?
Is it caused by secondary connections trying to contact and connect through me (being a primary)?
Is it people that were queue'd to download from me whose 'find sources' cycle had come back around looking for me?
Is it other primary connections looking for my machine to incorporate themselves on the 'primary grid' I was on?
Should I be at all concerned with the incoming hits on me that werent referencing the MX ports I had dedicated (what could they be)?
Thanks to anyone who read through this all this rambling and share-on!
-L:wings
I'm only a couple of weeks into using WinMX (my first file-sharing program) and was wondering if anyone has some answers for a few questions I have regarding how it works.
I too have had pretty poor upload/download speeds on occasion and today got flat-out disconnected from the network. While I have WinMX up everything internet-related gets really bogged down for me, even though I may not be downloading anything and my uploads are maxxing out at 4k/s total. I began getting concerned that something was running in the background that I was unaware of, so I used the software with my router (linksys) to monitor the incoming and outgoing logs for suspicious activity.
I have a CABLE connection and connect to WinMX via a PRIMARY connection, and have opened 2 ports (not the default ones for MX) for tcp and udp access.
What I did:
After a couple of days of consistantly excrutiatingly slow downloads, and embarrassing uploads, I closed MX and opened up my connection log to see what ip's where hitting what.
Thankfully, with MX closed and no active net usage on my part, my outgoing log remained static (so I feel better about there not being something in my background that's broadcasting on me and hogging bandwidth).
My incoming log, however, told a very different story. For the next 4 hours, I kept getting hits on my tcp port that I had dedicated to MX every 5-10 mins or so (in addition to some random hits on different ports). Some of the IP addresses would repeat the action to me a couple of times, others only once.
I understand the structure of the peer-to-peer network for the most part, but why do I keep getting these hits long after MX is closed?
Is it caused by secondary connections trying to contact and connect through me (being a primary)?
Is it people that were queue'd to download from me whose 'find sources' cycle had come back around looking for me?
Is it other primary connections looking for my machine to incorporate themselves on the 'primary grid' I was on?
Should I be at all concerned with the incoming hits on me that werent referencing the MX ports I had dedicated (what could they be)?
Thanks to anyone who read through this all this rambling and share-on!
-L:wings