Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lionel77]

Hmm... weird.

Have you tried forwarding ports for other apps to the Mac (like ftp or http)? Do those work?

[ken]

Hmm.  Well, there are two different issues here.  Low-ID would result from an outside client being unable to initiate a connection to your computer, and that's the sort of thing which is usually affected by port forwarding.

However, they are unable to connect to an outside computer.  This means that the outside computer can't even reply when the Mac initiates the connection.  This indicates an issue with the NAT router or firewall.  However, that should prevent the Mac from doing anything on the net, even web browsing.  If you use the "telnet " command in a Terminal window, can you initiate a connection to an ed2k server?  (For example, "telnet 62.241.53.2 4242".  If it connects, press the escape key (usually control-]) and then type "quit".)  If you can telnet, then it's definitely something with aMule.

Hmm.  Maybe an endian issue crept back in due to the building of aMule as a Universal Binary.  Perhaps aMule is trying to connect to the IP of the server but with the bytes reversed.  Try this: add a server by IP address, but with the compoents of the IP address in reverse order.  For example, Donkey Server No1 is at 62.241.53.2:4242 but try 2.53.241.62:4242, instead.

Double hmm.  The people experiencing this problem seem to be using a mix of PPC and Intel Macs.  I wouldn't expect an endianness bug to affect both platforms.  I would expect it to hit one or the other.  Well, let's see what the tests I've suggested reveal.

[profipimp]

Originally posted by ken
If you use the "telnet " command in a Terminal window, can you initiate a connection to an ed2k server?  (For example, "telnet 62.241.53.2 4242".  If it connects, press the escape key (usually control-]) and then type "quit".)  If you can telnet, then it's definitely something with aMule.

Well, seems to be something with aMule:

Code: [Select]

telnet 62.241.53.2 4242
Trying 62.241.53.2...
Connected to 62.241.53.2.

I also tried adding servers manually, no luck.

My System (hope it helps):
Computername:   iBook G4
Computermodell:   PowerBook6,5
CPU-Type:   PowerPC G4  (1.2)
Number of CPUs:   1
CPU-Frequency:   1.33 GHz
L2-Cache (per CPU):   512 KB
DDR-RAM:  768 MB
Busgeschwindigkeit:   133 MHz
Boot-ROM-Version:   4.8.7f1
Systemversion: Mac OS X 10.4.5 (8H14)
Kernelversion: Darwin 8.5.0

Thanks for all your work

[profipimp]

It seems that the new MAC OSX system update fixes it for me.
Good connection. Good u/d. all good.

 :baby: :baby: :baby:

EDIT:

Well, only for the first start of aMule.   ;( ;(

Second start -> same symptoms.

[Sivex]

Ive been having this problem too.
I had it in the previous versions and still have it now, even though i thought i would be solved with the new one.
I have the same prob with edonkey and overnet X(.
But anyway, i dont really care cause even if u do connect to any server the donwloads are sooooooo slow.
There are much better programs out there

[stefanero]

I wonder if this is a MacOS "feature"

[lionel77]

I wonder if this has something to do with the problem described here.