aMule Forum
English => Multiplatform => Mac OSX => Topic started by: KayCee on March 20, 2006, 04:09:21 PM
-
aMule doesn't want to connect to the internet. It tries all the time to connect, so the status is always "Servers: Trying to connect".
I used aMule 2.0.3 all the time and had no problems. Then I downloaded aMule 2.1.0, I had the same problems like now.
The settings are the same, that I had on my aMule 2.0.3.
The Serverlist is also the same.
Please help me!
-
I too am having this problem....
I have only recently downloaded my first amule. I have started with the lastest version. The first few times I used aMule it connected just fine. I have adjusted a few settings, but mainly only bandwiths etc. I don't think I have fiddled with it too much.
I can't seem to get it to connect at all anymore...
Don't know much about this stuff.... been trying to find more info in FAQ's and other forums, but no luck finding a cure so far!!
PLEASE HELP US!!!
Cheers,
Beets ?( :baby:
-
many many servers are offline since razorback2 got shutdown
try one of the following:
ed2k://|server|62.241.53.2|4242|/
ed2k://|server|62.241.53.4|4242|/
ed2k://|server|62.241.53.16|4242|/
-
Apparently Razorback is just doing fine.
But I have the same problem. I just cant connect to any servers.
I have the ports forwarded, and still I get no connection at all.
I am running MAC OS 10.4.x and aMule 2.1.1
2006-03-29 15:00:27: Credit-Datei geladen, 0 Clients sind bekannt
2006-03-29 15:00:27: - Dies ist aMule 2.1.1 using wxMac v2.7.0 (Unicoded), basierend auf eMule.
2006-03-29 15:00:27: Läuft auf MacOS (Darwin 8.5.0 Power Macintosh)
2006-03-29 15:00:27: - Besuche [URL]http://www.amule.org[/URL] um zu sehen, ob eine neue Version verfügbar ist.
2006-03-29 15:00:27: Lade ipfilter.dat-Dateien.
2006-03-29 15:00:27: 0 IP-Bereiche von ipfilter.dat geladen. 0 fehlerhafte Zeilen wurden ignoriert.
2006-03-29 15:00:27: 0 IP-Bereiche von ipfilter_static.dat geladen. 0 fehlerhafte Zeilen wurden ignoriert.
2006-03-29 15:00:27: Lade Datei server.met: /Users/profipimp/Library/Application Support/aMule/server.met
2006-03-29 15:00:30: 247 Server in server.met gefunden
2006-03-29 15:00:30: 6 part-Dateien gefunden
2006-03-29 15:00:30: Externe Verbindungen in der Konfigurationsdatei deaktiviert
2006-03-29 15:00:30: MuleUDPSocket: Created Server UDP-Socket at port 4665
2006-03-29 15:00:30: MuleUDPSocket: Created Client UDP-Socket at port 5445
2006-03-29 15:00:30: 3 bekannte freigegebene Dateien gefunden
2006-03-29 15:00:31: Error: Cannot get the official hostname (error 22: Invalid argument)
2006-03-29 15:00:31: AICH-Thread: Synchronisations-Thread gestartet.
2006-03-29 15:00:31: AICH-Thread: Masterhashes von bekannten Dateien wurden geladen.
2006-03-29 15:00:31: AICH-Thread: Keine neuen Dateien gefunden.
2006-03-29 15:00:31: AICH-Thread: Beendet.
2006-03-29 15:00:31: Deine Kopie von aMule ist aktuell.
2006-03-29 15:01:08: Fehler beim Verbinden zu allen Servern in der Liste. Ein neuer Durchgang wird gestartet.
I checked active servers with the emule client of my flatmate, and hes able to connect to all servers.
I do NOT understand it at all.
Plz hlp me cause apparently I am a big noob.
:)
-
well maybe its a firewall issue, is your flatmate in the same LAN as you are?
if yes, you both should be using different ed2k ports, and then forward them from the router to your PC
maybe your flatmate did that for his eMule and you are using the same ports as he does...so this cant work
btw: razorback2 is dead, the remaining razorbacks are fake servers from teh RIAA
-
Originally posted by stefanero
well maybe its a firewall issue, is your flatmate in the same LAN as you are?
yes, we are...
if yes, you both should be using different ed2k ports, and then forward them from the router to your PC
well, I manage the router in our flat, and he has ports TCP 30500 and UDP 30505 forwarded.
So that cant be the problem, because I am using default ports with aMule. Must be something different. I get a connection on my debian 2.6.16 linux OS and NO connection under mac os x (I opened the ports in the mac firewall as well). Just no connection at all.
:(
btw: razorback2 is dead, the remaining razorbacks are fake servers from teh RIAA
[/quote]
good to know ;)
-
Originally posted by profipimp
So that cant be the problem, because I am using default ports with aMule. Must be something different. I get a connection on my debian 2.6.16 linux OS and NO connection under mac os x (I opened the ports in the mac firewall as well). Just no connection at all.
:(
Did you try changing the ports to something non-standard? Some ISPs filter the default P2P ports...
-
do you debian and MacOS use teh SAME ip address?
is it the SAME pc or a different one?
if its teh same pc, check the IPs , if its a different one, you of course cannot use the same ports...
-
Hi!
As 'profipimp' also I have the same problem.
At home I have 1xPC (main computer, Windows XP), 1xmacMini (Intel, internal firewall disabled) and one wireless router from Linksys (WRT54GC).
Everything works just fine from my PC. aMule or eMule it doesn't matter, because both work. I can't say the same for my macMini. When I start aMule I get the same message as 'profipimp' (Timed out). IP of macMini is 192.168.1.3 and on my PC 192.168.1.2. I disconected PC from my network, redirected mule ports from 192.168.1.2 to 192.168.1.3. And no luck :(
Should I try different, nonstandard ports?
-
you are redirecting from
192.168.1.2 -> 192.168.1.3 ?? so you are routing from winXP to mac???
try non standart ports, but if you say the standart ports work on winXP it should not matter...
-
Originally posted by stefanero
you are redirecting from
192.168.1.2 -> 192.168.1.3 ?? so you are routing from winXP to mac???
No...I have changed the routing mechanism on router (Linksys). I changed it from 192.168.1.2(PC) to 192.168.1.3 (Mac).
What else can I do?
-
Originally posted by stefanero
do you debian and MacOS use teh SAME ip address?
Yes, they share the same reserved DHCP-address. Since the router auths my MAC-adress, it doesnt make a destinction between OS running.
is it the SAME pc or a different one?
its the same.
if its teh same pc, check the IPs , if its a different one, you of course cannot use the same ports...
its the same pc and ip
So I wonder if it probably is a bigger problem, or if not, what it could be.
-
I am kinda clueless with the two off you here...looks to me this is a MacOS issue since you say it works on other OS running on the same pc and IP,
so it cant be portforwarding or anything regarding that...
I'll show this thread our macos gurus ;) maybe they have some idear
-
one last question
does teh other OS have a highID ? or lowID?
-
Hi!
Mine has High ID.
-
Hmm... weird.
Have you tried forwarding ports for other apps to the Mac (like ftp or http)? Do those work?
-
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.
-
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:
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 :)
-
It seems that the new MAC OSX system update fixes it for me.
Good connection. Good u/d. all good.
:baby: :baby: :baby: 8)
EDIT:
Well, only for the first start of aMule. ;( ;(
Second start -> same symptoms.
-
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
-
I wonder if this is a MacOS "feature"
-
I wonder if this has something to do with the problem described here (http://forum.amule.org/thread.php?threadid=9753&boardid=49&sid=).