mIRC Home    About    Download    Register    News    Help

Print Thread
#96160 30/08/04 05:09 AM
Joined: Jul 2004
Posts: 4
S
Solarin Offline OP
Self-satisified door
OP Offline
Self-satisified door
S
Joined: Jul 2004
Posts: 4
I'm on Windows XP SP2 and the receiving user is on Windows ME. Both are using mirc 6.16

Here is my debug output:
PRIVMSG Someuser :DCC SEND 09_-_some_random_file.mp3 1123360477 4985 6082560
PRIVMSG Solarin :DCC RESUME "09_-_some_random_file.mp3" 64453 2191360

Tried connecting at port 6668 instead of port 6667 on the server...

PRIVMSG Someuser :DCC SEND 09_-_some_random_file.mp3 1123360477 4985 6082560
PRIVMSG Solarin :DCC RESUME "09_-_some_random_file.mp3" 65361 2191360

I'm on adsl and they are on dialup. This doesn't work with other mirc versions such as 6.15 and 6.12. I even tried mirc 5.91 to no avail.

I would have to say it is the port number on the RESUME coming back to me that is causing the problem. Why does it do that and what command could the user type/paste to temporarily get past this issue?

#96161 31/08/04 09:30 AM
Joined: Sep 2003
Posts: 4,230
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
Theres a router involved there or a NAT, its translating the port number, it detects the dcc send , and adjusts it to the higher port number (normally 60,000+) only ptoblem is on a resume that portnumber is sent rather than the true one a resume is ment to send, aka the sender ignores the resume request. When i was working on it i found no way around the problem, i do believe they may have fixed it later with a router bios upgrade (thats speculation tho)

#96162 01/09/04 03:07 AM
Joined: Jul 2004
Posts: 4
S
Solarin Offline OP
Self-satisified door
OP Offline
Self-satisified door
S
Joined: Jul 2004
Posts: 4
wouldn't a /ctcp nick resume ...
back to me with the correct port work?


#96163 02/09/04 10:45 AM
Joined: Sep 2003
Posts: 4,230
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
i cant remeber why , but that didnt work either......

hmmmm now i think about it the problem might have been that the mirc never knows the real port since the port translation has already happened,

From memory u could fix it doing that but as said , if you dont know the port number?


Link Copied to Clipboard