eMule Plus 1.1 suddenly goes LowID
|
|
![]() ![]() ![]() |
eMule Plus 1.1 suddenly goes LowID
| LorenzGr |
Feb 9 2006, 08:11
|
|
Group: Members Posts: 5 Joined: 14-January 06 |
I write to confirm what already mentioned. Seems that more i browse the web sooner happens this behaviour. This time i left my pc on with only eMule+ and without user interaction for 5 days and still is high Id.
|
|
Post
#61
|
|
| eklmn |
Feb 10 2006, 06:52
|
|
Group: Developers Posts: 1039 Joined: 29-May 03 |
QUOTE(LorenzGr @ Jan 14 2006, 10:08) My ip remains the same.. but the lowid behaviour happens.. usually after 1 day of continue connection can you please download TCP Optimizer from www.speedguide.net & set proper MTU (i.e. when packet will be not fragmented) |
|
Post
#62
|
|
| LorenzGr |
Feb 10 2006, 14:44
|
|
Group: Members Posts: 5 Joined: 14-January 06 |
Another update:
with bittorrent alive this time only 12 hours of high id! A record! also this time the download rate was poor, but the upload one has everytime been to the maximum (like always)... @eklmn i know of tcp optimizer (but i've never used it) and i know what is MTU, i'm a computer addict! I'll try just now and will give you an update of the situation! |
|
Post
#63
|
|
| LorenzGr |
Feb 10 2006, 19:17
|
|
Group: Members Posts: 5 Joined: 14-January 06 |
I've set the MTU to my maximum with TCP Optimizer.. I've also setted the optimal settings advised by the program...
I can't know if is related... this time 4 hours of High ID! A new record! Maybe i've found a relation with this, everytime in the field of the theory: if the maximum upload rate is reached often (like with Bittorrent + eMule together or with eMule with web browsing together) the undesired behaviour happens earlier. Could be a correct explanation? |
|
Post
#64
|
|
| AnakinSG1 |
Feb 21 2006, 14:02
|
|
Group: Members Posts: 3 Joined: 21-February 06 |
QUOTE(LorenzGr @ Feb 10 2006, 17:17) I've set the MTU to my maximum with TCP Optimizer.. I've also setted the optimal settings advised by the program... I can't know if is related... this time 4 hours of High ID! A new record! Maybe i've found a relation with this, everytime in the field of the theory: if the maximum upload rate is reached often (like with Bittorrent + eMule together or with eMule with web browsing together) the undesired behaviour happens earlier. Could be a correct explanation? Hi fellows! I'm new on this forum, and get registered becouse of this thread. I'm having this anoying behavior long time ago ... Since I change my computer I guess ... and that happened at early march 2004. I bought a Athlon 64 3000+ with ASUS A8N-SLI (nForce 4). So, I was intending to use the hardware firewall provided by nForce 4. Ok, all worked fine for me, except emule plus ... I have been using it for a long time, and I never noticed this before. I consider you guys winners, coz' my connection refuse at about 4 hours in the best cases. During my use, I have learned how to configure properly that crap nVidia Firewall, so, for a resonable time, I hadn't this issue, and 12 hours connected with Razorback was no problem. But the problem has returned ... and when I'm using MSN + Brownsing internet + Emule Plus, it seems like my connection die suddenly! I looked at my firewall and it shows me that all my tcp outgoing traffic has been bloked since. It only returns to work If I change my Firewall profile to medium ... the problem is that doing this, I loose my port configuration. Earlyer versions of emule plus, changed the port used by client ... what port it uses indeed? And why it hang my outgoing traffic?. I'm using the following System: OS: Windows XP SP2 - totaly up to date (all fixes installed) MEMO: 1 GB DDR 400 Dual PROCESS: Athlon 64 X2 3800+ Firewall: nVidia Firewall - latest version ActiveArmour: not functioning ISP type: ADSL 500 KBPS PPPOE connection Modem: Zyxel Parks 462 R (Router) But in "bridge mode" AntiVirus: AVAST 6.4 This post has been edited by AnakinSG1: Feb 21 2006, 14:09 |
|
Post
#65
|
|
| xalbux |
Feb 21 2006, 14:56
|
|
Group: Members Posts: 234 Joined: 2-March 03 |
@anakinSG1
Your problem is probably related to the nvidia firewall. For the others the LowID occurance means that they only have to restart eMule Plus to resolve the problem. Another apllications aren't affected at all and remain fully functional (e.g. browsing, email-transfers, ftp, etc.) Either it's a misconfiguration of Your firewall. May be some kind of flood detection. Hard to say as I don't know anything about the nvidia firewall. Or should consider to leave the nvidia firewall and use a descent one that is well known to work with eMule Plus without interference. Regards |
|
Post
#66
|
|
| AnakinSG1 |
Feb 21 2006, 15:31
|
|
Group: Members Posts: 3 Joined: 21-February 06 |
@xalbux
Thanks for your reply! I was wondering about the firewall ... I used to use Sygate Personal Firewall without probems in the other PC. I post here because apparentely the issue is the same. Razorback kicks me off and then, the others servers start to give me low id, until de connection crash again. Thanks again for your time, before give up I'll try nvidia forums... maibe they know something ... Best regards. This post has been edited by AnakinSG1: Feb 21 2006, 15:50 |
|
Post
#67
|
|
| glaskrug |
Feb 25 2006, 11:21
|
|
Group: Betatesters Posts: 157 Joined: 11-September 05 |
Just for the record I want to add that I am too suffering from this lowID issue.
Every once in a while, after a few hours, mostly after the connection to a server is lost and e+ tries to reconnect, I get a persistent lowID. It tried 3 times and every time it gets a lowID. Sometimes waiting a few minutes and manually reconnecting to another server helps, but most of the time I have to restart e+ to get a highID. And yes, I also noticed that no other client shows this kind of behaviour XP Pro SP2, all updates, tcpip.sys patched stable connection, static IP no software firewall KAV Pro 5.x (latest) |
|
Post
#68
|
|
| AnakinSG1 |
Feb 27 2006, 00:32
|
|
Group: Members Posts: 3 Joined: 21-February 06 |
QUOTE(glaskrug @ Feb 25 2006, 09:21) Just for the record I want to add that I am too suffering from this lowID issue. Every once in a while, after a few hours, mostly after the connection to a server is lost and e+ tries to reconnect, I get a persistent lowID. It tried 3 times and every time it gets a lowID. Sometimes waiting a few minutes and manually reconnecting to another server helps, but most of the time I have to restart e+ to get a highID. And yes, I also noticed that no other client shows this kind of behaviour XP Pro SP2, all updates, tcpip.sys patched stable connection, static IP no software firewall KAV Pro 5.x (latest) Yeah, I made several tests. The problem is not my firewall. I reinstalled all nforce drivers and the firewall and the problem persist. When disconnected from a server, then all other automatic reconections became low id. If I close emule and reopen i can get high id again. Ps.: this won't happen with shareaza. |
|
Post
#69
|
|
| beter pan |
Mar 5 2006, 16:03
|
|
Group: Members Posts: 2 Joined: 4-July 05 |
I have got an 512/128 adsl connection. by opening 4662 port, I used to get a high id. unfortunately I suddenly lost getting high id. I upgraded emule plus to v 1.2 but nothing has changed.
please help me to get a high id... |
|
Post
#70
|
|
| muleteer |
Mar 5 2006, 16:26
|
|
Group: Betatesters Posts: 8261 Joined: 29-February 04 |
1. Open your firewall configuration and delete any rules there for emule.exe. Now run the client and when the firewall asks you again, give emule.exe full access, both to connect to the internet and to accept incoming connections from the internet.
2. Try another server. Of late some of the servers have been incorrectly handing out LowIDs. e.g. If the DonkeyServers are giving you LowID, try UseNeXT or EMServer No.1. |
|
Post
#71
|
|
| LorenzGr |
Mar 11 2006, 19:34
|
|
Group: Members Posts: 5 Joined: 14-January 06 |
I write only for advise that eMule 1.2 is still affected by this annoying bug.
From what i've seen i think that could be considered more than a theory: if the maximum upload rate is reached often (like with Bittorrent + eMule together or with eMule with web browsing together) the undesired behaviour happens earlier. Lowering the upload limit of eMule works in fact well for longering the time without encountering this bug. This post has been edited by LorenzGr: Mar 11 2006, 19:36 |
|
Post
#72
|
|
| glaskrug |
Mar 12 2006, 14:33
|
|
Group: Betatesters Posts: 157 Joined: 11-September 05 |
QUOTE(LorenzGr @ Mar 11 2006, 19:34) I write only for advise that eMule 1.2 is still affected by this annoying bug. From what i've seen i think that could be considered more than a theory: if the maximum upload rate is reached often (like with Bittorrent + eMule together or with eMule with web browsing together) the undesired behaviour happens earlier. Lowering the upload limit of eMule works in fact well for longering the time without encountering this bug. Can not confirm. Actually I even compiled a version that doesn't upload at all (for test reasons only of course) a few weeks ago, and still I get a LowId after loosing server connection almost every single time. Sometimes manually connecting to another server helps, but most of the time only a restart of e+ solves the problem. |
|
Post
#73
|
|
| rgreen83 |
Mar 12 2006, 22:22
|
|
Group: Members Posts: 78 Joined: 9-December 03 |
Just to add a tiny bit to this story, I have noticed that before any of this happens, I notice a very sharp drop in general and download connections, like 50-75% dropped in between a six second update. they then continue to drop until reaching zero for download and near it for general (uploads stay connected for some reason) then whether i disconnect manually or the server disconnects me, I am then bit by the lowid bug.
Also i, like glaskrug, can not confirm what lorenzgr is seeing, as I often run utorrent along side e+ both with what their full upload limits would be were they running alone, and i watch them fight back and forth for upload speed when one needs more, so I am def always using my max upload rate. |
|
Post
#74
|
|
| xalbux |
Apr 3 2006, 19:43
|
|
Group: Members Posts: 234 Joined: 2-March 03 |
And again.
Same occurence as everytime. eMule Plus stops listening on the TCP port. Every other Application is still functional and listening. No windows restart required. Just restarted eMule Plus to resolve. @all I suggest You keep posting Your 'Suddenly Low ID' events. Loss of connectivity is a worst case scenario for a P2P application. Regards |
|
Post
#75
|
|
![]() ![]() ![]() |
| Lo-Fi Version | Time is now: 20th May 2013 - 01:12 |