Snowman
12-04-00, 08:21 AM
Rather long, but please read....
OK, here we go- Me and a couple of friends of mine like to file swap, etc. We use simple server/client ftp programs to do so. I run a very small and simple ftp server program. Well, startingabout 2 weeks ago, every time someone connected to my ftp server on comcast@home, he could start to d/l from me, but about 1-2 minutes into the transfer, he would timeout. No matter what, this would happen. I have my port for the ftp set on 2121. Well, come to find out, I cannot d/l from his ftp server (also on comcast@home in the same city) either without the same exact problem. He says he has no problems though except with me timing out. Well, all day yesterday, I began to investigate this further.
First off, when I am d/l'ing from him and I begin to timeout, it is only the ftp transfer that times out. I can still check email, web surf, etc. The very stange thing about this whole thing is that I can use the same programs and ftp to sites all over the internet and transfer files without a single problem-but when WE try to do so, we timeout EVERYTIME.
This is my possible theory and I need you guys to tell me if this is possible: @home's policy is thou shall not run any FTP servers, right? Is it possible that they monitor commonly used ftp ports and noticed that we are doing so? Could they see both of our comcast@home's IP's and timout our connection when we try to file transfer?
This is what all I have tried to fix this: Formatted my hard drive twice, installed no regestry tweaks, installed numerous registry tweaks, scanned for viruses, installed firewall, uninstalled firewalls, reset cable modem numerous times, tried Win98SE, WinME, then back to Win98SE. I have tried every possible solution that I can think of. Now, my other friend that tries to connect to me who lives in Atlanta has the same timeout problem on my FTP server, but he is on Mediaone RR, so that could possibly eliminate some of my theory.
Keep in mind that this only happens when we transfer files amongst ourselves. I can connect to any public ftp server and have absolutely zero trouble timing out using the same programs. My mind is blown to what this could possibly be except for my conspiracy theory.
I know that @home has a computer in California that port scans their users periodically looking for servers, etc. because my firewall catches it every so often. This is a known fact. Well, in the last two weeks, I have NOT been running my firewall program but I have been running my ftp program. Is is possible that their computer saw my ftp, and somehow is starting to block access to it? Like I said, I hardly abuse their service with the ftp, only 2 people occasionally log into it and d/l from me.
What I don't know and wondering if you guys know- Does @home have this capability to do this? The last thing I haven't tried but will tonight is completely changing my ftp port from 2121 to some random number like 23146.
If anyone can give me some input on this I would appreciate it.
Snowman
OK, here we go- Me and a couple of friends of mine like to file swap, etc. We use simple server/client ftp programs to do so. I run a very small and simple ftp server program. Well, startingabout 2 weeks ago, every time someone connected to my ftp server on comcast@home, he could start to d/l from me, but about 1-2 minutes into the transfer, he would timeout. No matter what, this would happen. I have my port for the ftp set on 2121. Well, come to find out, I cannot d/l from his ftp server (also on comcast@home in the same city) either without the same exact problem. He says he has no problems though except with me timing out. Well, all day yesterday, I began to investigate this further.
First off, when I am d/l'ing from him and I begin to timeout, it is only the ftp transfer that times out. I can still check email, web surf, etc. The very stange thing about this whole thing is that I can use the same programs and ftp to sites all over the internet and transfer files without a single problem-but when WE try to do so, we timeout EVERYTIME.
This is my possible theory and I need you guys to tell me if this is possible: @home's policy is thou shall not run any FTP servers, right? Is it possible that they monitor commonly used ftp ports and noticed that we are doing so? Could they see both of our comcast@home's IP's and timout our connection when we try to file transfer?
This is what all I have tried to fix this: Formatted my hard drive twice, installed no regestry tweaks, installed numerous registry tweaks, scanned for viruses, installed firewall, uninstalled firewalls, reset cable modem numerous times, tried Win98SE, WinME, then back to Win98SE. I have tried every possible solution that I can think of. Now, my other friend that tries to connect to me who lives in Atlanta has the same timeout problem on my FTP server, but he is on Mediaone RR, so that could possibly eliminate some of my theory.
Keep in mind that this only happens when we transfer files amongst ourselves. I can connect to any public ftp server and have absolutely zero trouble timing out using the same programs. My mind is blown to what this could possibly be except for my conspiracy theory.
I know that @home has a computer in California that port scans their users periodically looking for servers, etc. because my firewall catches it every so often. This is a known fact. Well, in the last two weeks, I have NOT been running my firewall program but I have been running my ftp program. Is is possible that their computer saw my ftp, and somehow is starting to block access to it? Like I said, I hardly abuse their service with the ftp, only 2 people occasionally log into it and d/l from me.
What I don't know and wondering if you guys know- Does @home have this capability to do this? The last thing I haven't tried but will tonight is completely changing my ftp port from 2121 to some random number like 23146.
If anyone can give me some input on this I would appreciate it.
Snowman