Welcome, Guest. Please login or register.

Author Topic: AmIRC issues...  (Read 2202 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline alberonnTopic starter

  • Jr. Member
  • **
  • Join Date: Aug 2002
  • Posts: 66
    • Show only replies by alberonn
AmIRC issues...
« on: September 05, 2004, 11:08:16 PM »
Last night I was trying out AmIRC's DDC Send and Recieve options and I was not getting it to transfer at all. It would recognise that someone was trying to send something to me and the guy saw I was trying to send to him. But he couldn't get the file.

We were both behind a router and he suggested that it may be a port forewarding issue. I 'm not too up on this stuff so any help woud be nice.

On a related issue, anytime I try to do a file transfer with AmTelnet, it usually locks up as well. But I don't know if that's just an AmTelnet issue.

Both programs are registered as well.
 

Offline KennyR

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 8081
    • Show only replies by KennyR
    • http://wrongpla.net
Re: AmIRC issues...
« Reply #1 on: September 05, 2004, 11:18:06 PM »
If you're behind a router, there's two things you need to do to be able to send dcc with AmIRC (receiving is always ok).

1) You have to forward the DCC ports to your computer running AmIRC. You can select these yourself with the last AmIRC beta, I recommend 1045-1055 (1 for each file being DCC'd simultaneously.

2) If you don't have a static IP or some kind of DNS address (or manually set your IP in AmIRC each time you're online), you'll have to run some script to tell AmIRC what your IP address is, otherwise it'll use your LAN one, and this won't work. SetTIADCC (on Aminet) will do this; set it to be run when AmIRC starts.

Note that software routers with conntrack properly set up don't suffer from 2).
 

Offline alberonnTopic starter

  • Jr. Member
  • **
  • Join Date: Aug 2002
  • Posts: 66
    • Show only replies by alberonn
Re: AmIRC issues...
« Reply #2 on: September 07, 2004, 06:11:46 AM »
OK, I got Port forewarding set up on the router, but right now I have ports 8662-8671 set, since that seems to be what AmIRC seems to be using. I can set then if I use TIADCC, (I think,) but I don't know if that'll require more setup on my end.

Does both computers have to have the same port #'s to do DCC stuff?

I do have a Static IP and the DNS set for my Amiga allready. I did that since I wanted to remember what my locak IP address was for any sortof local networking I was planning on doing later. I also had to do it for my Gamecube since that was the reccomended way of setting it up...

I'll give the setTIADCC a peek though...
 

Offline alberonnTopic starter

  • Jr. Member
  • **
  • Join Date: Aug 2002
  • Posts: 66
    • Show only replies by alberonn
Re: AmIRC issues...
« Reply #3 on: September 07, 2004, 07:47:15 AM »
OK, I setup SetTIADCC and my router with the range you reccomended. But I have yet to test things. I setup the SetTIADCC ARexx script to launch on Connection, as the readme reccomended, but it doesn't run the script. However, it does run fine when I manually run it out of the Rexx menu. Not sure what I'm doing wrong. I checked Use TIADCC in Networks and put the range in there as well.

I know it's working when I can see the ENV variable in ENV:

Seeing what goes in there told me I misread what you told me. Yeah, I guess I do need the script to get my actual IP address? LOL

I have yet to test this setup though...

Oh yeah, I'm running AmIRC v3.5.25
 

Offline KennyR

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 8081
    • Show only replies by KennyR
    • http://wrongpla.net
Re: AmIRC issues...
« Reply #4 on: September 08, 2004, 02:13:31 AM »
Quote
alberonn wrote:
Seeing what goes in there told me I misread what you told me. Yeah, I guess I do need the script to get my actual IP address? LOL


Yeah, you need it to get your internet IP address. AmIRC is dumb and will use your LAN one otherwise, and so the DCC will go nowhere. AmIRC doesn't know what IP-NAT is.

Not sure why the script isn't being run on start, since it sounds like you set it up just right. Very strange.