mIRC Home    About    Download    Register    News    Help

Print Thread
dcc problems(resume spoilt) #74548 09/03/04 07:50 AM
Joined: Mar 2004
Posts: 2
B
bykte Offline OP
Bowl of petunias
OP Offline
Bowl of petunias
B
Joined: Mar 2004
Posts: 2
Hi, why I can receive files from others but when the file got cancelled halfway and when the user tried to send me again, I choose resume. It will not worked. It will stuck there. Then they will give error messages such as "DCC Get of XXX.tar from 007 timed out" / -007- *** Closing Connection: DCC Timeout (180 Sec Timeout). The only way to solve it is to overwrite the files. THAT WONT DO! I am behind a router and I have opened "1024-1026". I am using mIRC 6.14. Under Connect->Options::Advanced dialog, I checked "DCC" for Port range for connections. Under the first and last, i used 1024 & 1026 respectively. I checked the "use random ports". I also checked "Bind sockets to IP Address" in which I insert my LAN Ip for my com which is 10.0.0.14. Any idea? Any help will be appreciated.

Re: dcc problems(resume spoilt) #74549 09/03/04 10:53 AM
Joined: Feb 2003
Posts: 2,751
Raccoon Offline
Hoopy frood
Offline
Hoopy frood
Joined: Feb 2003
Posts: 2,751
I wouldn't say this is a "sploit".

A problem like this would usually be on the sender's side. Not all IRC clients are capable of supporting resume, or some of them are incompatable with eachother. Try having another mIRC v6.14 user send you a file, and then try resuming it.

Your router/port/bind settings should have no effect on this, as the receiver of the file.

- Raccoon


Well. At least I won lunch.
Good philosophy, see good in bad, I like!
Re: dcc problems(resume spoilt) #74550 09/03/04 09:03 PM
Joined: Sep 2003
Posts: 4,230
D
DaveC Offline
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
I have seen this problem before, its a peice of hardware maybe your router adjusts the port range of incoming files, you must understand that when you recive a file, you actually recive first a message in mirc like this "DCC SEND filename IP port size", you then make the connection to the person who is sending you the file, this method is used to bypass your firewall, as you make an outgoing connection.

heres the likely problem. the sender of the file sends this message in mirc as follows. "DCC SEND blah.rar 3389006414 5000 200000000"
3389006414 is the senders ip
5000 is the port
200000000 is the size

your hardware doesnt let you have that port so alters the port number to one it lets you have say 23000, all goes well becuase when you connect out using 23000, it adjusts this to 5000 for the sender, the problem comes if you go to resume, when you do this you send a resume request as follows "DCC RESUME blah.rar port size" aka "DCC RESUME blah.rar 23000 150000000"
23000 being the port you were told to use
150000000 being the size of the file you have

now when the sender gets this, his mirc or what ever hes using just goes to itself , "Im not sending anyone a file on port 23000 so im going to ignore that message" and thus your resume request is declined, and you get a timeout situation.

Re: dcc problems(resume spoilt) #74551 10/03/04 10:03 AM
Joined: Feb 2003
Posts: 307
T
tontito Offline
Fjord artisan
Offline
Fjord artisan
T
Joined: Feb 2003
Posts: 307
well i have seen a similar procedure when i was making my proxy server.
Mirc alwais trys to make a direct connection, so when one of the clients is inside of a lan protected by a proxy firewall, if it is sending a file (ole), and the other client (tontito) can't connect, it requests that the original client(ole) makes the connection to send the file(in original protocol, the sender only waits to recive the connection)

example:
ole -> DCC SEND phpBB-2.0.6.zip 2130706433 0 672919 127
tontito -> DCC SEND phpBB-2.0.6.zip 2130706433 2211 672919 127

has you noticed there is a extra field (since ole is configed to make dcc pass to proxy), that originaly was 0 then it was changed to 2211 (port were tontito is now listining for a connection to recive the file)

i know this sounds a bit confusing, it also confused me (now imagine try to resume a connection) :tongue: