aMule Forum
English => aMule Help => Topic started by: denisliber on October 21, 2004, 02:23:46 PM
-
HY!
I'm using aMule on MDK 10 with self compiled wx2.4.2 with GTK1 and self compiled aMule.
So,... I worked with 1.2.8 and when I moved to rc6 and now to rc7 the search became very very slow... takes some times 1-2 hours to finish.
I am talking about global search, searching localy is fast as allways, so when I start the search I get the results from the server I connected to very fast and then wait and wait and....... :(
Any idea what it might be?
-
you might mean a global search, right?
All searches are done on the server side. not on aMule side. So it must be your ISP that's shrinking the port's badnwidth :-( lot's of ISPs are doing this now.
Change your default ports to something else.
Greetings!
-
Thanks! I'll try it...
But, now I'm using 4662 and 4665 as TCP ports and 4672 as UDP, the question is what is the range of the ports I can use in each case and will it affect my ID (I mean will I stay HighID on new ports?)
Sorry if the question is trivial, well... not for me :)
-
yes as long as you have those pots open in the router/firewall
trivial? no questions are trivial. the only trivial questoin here is... "what's aMule?" ;-P
Report results, please :)
Greetings!
-
Hi,
For amule ports, UDP or TCP, u can use any ports over 1024 to 65535.
Just be carefull to not have a other application already using it, and have it open in firewall.
Thepolish
-
Hi again!
Thanks for the help ! But it didn't get better... slowwwwww. I even uninstaled it and returned to the 1.2.8 and the same search there is fast as always been :(
Do not know what to do?!
-
is search the _only_ problem you have? i mean, is webbrowseing fast, downloading fast, etc?
seems VERY strange.
-
Yes this is the problem. All other 'net things' are working well and file transfer in aMule is at the speeds I'm used to :( . I double checked the firewall and even removed it.... I checked the ports (not taken by something other ) and tried several different ports.
Sounds wierd I agree but.....
-
it could be a wx 2.4.2 problem.. i'm testing it right now
cheers
-
Thanks