Weird: "xdcc send #?" Causes freezeup!

[Riamus]

Sorry I couldn't be more help. Although it seems a strange problem to be caused by the college firewall, it could be possible that they made a change which is causing you the trouble.

One last possibility which won't help too much unless you know the servers is with using specific ports to download from. I assume you can download from HTTP? Test with someone on port 1080. Have someone manually dcc a small text file to you on that port. Manual command is:

/dcc send 255.255.255.255:1080 filename

Replace the IP (255.255.255.255) with yours. And replace the filename with the file (use path if necessary). Also, if the path/filename has spaces, put quotes around the entire path\filename...

Example:

/dcc send 255.255.255.255:1080 "c:\program files\test.txt"

You can also try various other ports that are usually left alone by college firewalls... e-mail ports, for example.

You may also want to try different filetypes in case the college has just suddenly started blocking specific filetypes. That's one reason why I said to use a text file for the test.

[jljr222]

Thanks for all your help, but I would think that it is because of my school, but unfortunately I have no way to test that theory. I tried your above suggestion, however it didn't seem to make a difference, no matter what port I choose it always failed. Also, just so you know. I tried to download a small .txt from a channels "!faq" trigger and worked. It worked on an TDCC server, and I haven't had a chance to test those, but it seemed to work well. Any idea why?

[Riamus]

Well, if text files work fine, then the college (or you somehow) is blocking specific filetypes.

[jljr222]

Well I don't know what it is, and I probably never will. Hopefully when I head home April, I should have this all sorted out. Thanks for all of your help and support with this matter. I really appreciate it.

[jljr222]

[Riamus]