D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-325 => Topic started by: venfan on December 10, 2011, 03:14:34 PM

Title: Help with aMule
Post by: venfan on December 10, 2011, 03:14:34 PM: anyone using aMule?
I tried to configure aMule, and managed to get High Id by configuring ports in the router, no still doesn't work. Search will not show any result.
Is there any guide available?
Thank you
Title: Re: Help with aMule
Post by: mbinax on December 12, 2011, 01:30:15 PM: I have the same problem.
I use an old Trust Wireless Access Point SpeedShare Turbo (http://www.trust.com/products/product.aspx?artnr=13643 (http://www.trust.com/products/product.aspx?artnr=13643)).

Anybody knows how to obtain High ID ?
Title: Re: Help with aMule
Post by: venfan on December 12, 2011, 05:39:07 PM: Quote from: mbinax on December 12, 2011, 01:30:15 PM
I have the same problem.
I use an old Trust Wireless Access Point SpeedShare Turbo (http://www.trust.com/products/product.aspx?artnr=13643 (http://www.trust.com/products/product.aspx?artnr=13643)).

Anybody knows how to obtain High ID ?

You have to configure your router in the "port forwading" section (name may change depending on your router brand)so it will send the information of certain ports to your DNS. The ports you have to configure are:
TCP 4662
DNP 4672
TCP 4665
You have to "forward" those ports to your DNS's IP in your network.

I got a high IP by doing this, but still doesn't work.
Hope this helps
Title: Re: Help with aMule
Post by: mbinax on December 13, 2011, 03:00:24 PM: Quote from: venfan on December 12, 2011, 05:39:07 PM
TCP 4662
DNP 4672
TCP 4665
You have to "forward" those ports to your DNS's IP in your network.

I've done, but nothing have changed.
Look at this Port Forwarding line, where I have to contact my NAS (IP: 192.168.1.74) on 4662 TCP port:
<Name> <Protocol> <LAN Server>
aMule TCP TCP 4662/4662 192.168.1.74

Is it right? Private and Public port have to be the same, as I did ?
Title: Re: Help with aMule
Post by: venfan on December 13, 2011, 04:44:12 PM: Quote from: mbinax on December 13, 2011, 03:00:24 PM
I've done, but nothing have changed.
Look at this Port Forwarding line, where I have to contact my NAS (IP: 192.168.1.74) on 4662 TCP port:
<Name> <Protocol> <LAN Server>
aMule TCP TCP 4662/4662 192.168.1.74

Is it right? Private and Public port have to be the same, as I did ?

Looks right to me....
Not sure what other setting can be affecting.
Sorry.
Title: Re: Help with aMule
Post by: tedfroop on December 19, 2011, 05:55:06 PM: Don't know if this helps, (from the aMule wiki.)

Go under Gaming applications
Now forward the ports to your computer:
Standard client TCP port
Change both Ports start and End to 4662
In the next field set TCP
In the field, the last 3 digits of your LAN IP
Extended client UDP port
Change both Ports start and End to 4672
In the next field set UDP
In the field, the last 3 digits of your LAN IP
Extended server requests UDP port
Change both Ports start and End to 4665
In the next field set UDP
In the field, the last 3 digits of your LAN IP
Now check Enable
And click Save settings
Then restart aMule :)
Title: Re: Help with aMule
Post by: mbinax on January 15, 2012, 09:52:44 AM: OK! Now it works!
Thank you!

Does anybody knows WHERE I can find (and edit) via-telnet the amule.conf on the NAS ??
Title: Re: Help with aMule
Post by: DGal on July 04, 2013, 03:12:50 PM: I just caught your forum conversation and am wondering if anyone can break this down to someone who doesn't know the lingo. I've been using aMule for 8 years and basically without problems that I couldn't work out. It always has a low ID, but now it's displaying "Stopped" or "Waiting" by the movies that aren't downloading. And it used to download anywhere between 5 and 15 at a time but now only 1 or 2. I read that you do things to the router, which I did, then it wouldn't even connect me to the internet. Any help would be greatly appreciated!