I've been using eMule Plus 1.1 since end of October 2004.

Had no problems so far.
But since last week it goes to LowID after several hours/days.

There's not much to say about possible causes.
I haven't changed the system since months. And so the router.

Somehow eMule Plus stops listening to the TCP port.
When I try to scan the incoming tcp port I get no answer.

Regards

does the emule-pc have a static ip config?

Many ISPs have a backup link in case the regular one fails temporarily. Sometimes this backup link needs p2p clients to be reconfigured. Or you could wait it out; the old setup will work wen the regular link is restored.

The computer has a LAN IP: 192.168.x.x
The ports are forwarded by a router.
Whenever the problem occurs all other forwardings in the router are still working.

Check your IP here when your connection is working properly and compare it with when it gives trouble.
http://www.stilllistener.com/checkpoint1/
Or do a trace route from your pc to list which IP addresses are used in the hops between you and a site. I still think I'm on the right track here.

Oops, E did it again :-)

Router is still working.
I have another P2P application running in the background and its port is still reported as open. I have used 'shields up' from www.grc.com to probe my ports.
eMule Plus port is reported as closed but eMule plus is still running and transferring.

I also checked my IP with Your link, nuleteer.
It identifies the same IP the router is claiming to have as external IP.
I also checked with checkip.dyndns.org. All are reporting the same IP.

I also made a tracert.
hop nr.1 is the LAN IP of the router
hop n.r2 is an IP that has nothing in common with the external IP. It's in a different subnet. Just the IP netstat can't resolve any IP belonging to that IP.
hop nr.3+4 are probably equipment of my ISP, The reverses namelookup reveals my ISP's namen. but these two are quite similar to hop. nr.2.

u always used to run both? how many connections is it probably using?

No, I usually only run eMule Plus.
This time I had a torrent running in addition, with only few connections used. Only 7 torrent clients are involved in that download.

I just mentioned the second P2P programm because that one is still listening on its port while eMule stopped listening.

Mine did this just a couple days ago. I had to log out of WindowsXP and log back in to get it to work again... but it did start working again.

At the command prompt type netstat -a and 'enter' and see if any other app is using that port.

I can't tell about the time eMule went into Low ID 'mode'.
But closing eMule Plus and restarting gives immediatly a High ID.If there was another application using that port, it's not active anymore. But I don't really think this is the cause.

does it also happen if no bittorrent is running at the same time?
did u tweak any windows tcp-settings?
or maybe have a short ttl for nat-table in router?

I sometimes (when doing intensive upload tasks, like running other p2p concurrently) have to decrease upload a lot for both of them to have High ID. That might be your case.

Hi,

I have been experiencing the same kind of problem, after some length of time, usually 3 or 4 days, emule just stops listening connections.

Restarting emule fixes the issue so I believe it´s not a misconfiguration problem.

I don´t run any other p2p concurrently with emule.


I have WinXPPro sp2, athlon1400, 512mb.



cheers.

Same problem here. But the only thing that helped me was to get back to an older version before 1.1

try setting "server connection keep-alive" to 2 minutes.

Does not work

Well, it did it again. Had no problems since may last post here.

eMule still reported being connected to razorback 2 but downloadednothing the last twelve hours. So I just reinitiated a server connect resulting in a Low ID. As before a restart gives immediatly back an High ID.

*sigh*

I had no problems for the last weeks, but today it just did it again.
Two times within several hours.

Everything is running fine but t suddenly stops listening on its incoming TCP port.

edit:

April, 13th 2005
And again :-/

And again.

Redone a portscan:
The TCP port is dead. No response to the portscanner although it is still listed with netstat or the GUI tool I use. a freeware called 'Active Ports'.
The UDP port is responsive.

Same to me...
I have Win98. First, E+ stopped downloading for a couple of days.
Then, everytime I tried to run it just refused to load (It freezed at the loading of servers and I had to CTRL-ALT-DEL it).
So I tried re-installing it. Nothing.
Then I deleted server.met, and the preferences files. It ran, but since then I have a low ID.
I went in preferences to see ports used and created a new rule (deleting the old one) in my firewall (it's a software given by default by Libero, my ADSL provider).
Nothing. Still have low-id (yellow arrows around the globe) and no downloads. Sigh... I'll try reverting to an older version.

Just getting used to it

It did it again on friday 23th april in the morning.
And this sunday 25th.

It seems chances for the TCP listening stop are higher when I have downloads with many sources in queue. My current source settings are:
- source exchange enabled
- max. sources per file 1000
- disable source exchange for files with more than 800 sources
no auto max sources
no dropping of highest QR

Most time I don't have files with such many sources in the down queue that these limits are exceeded. Combined with a max of 10 concurrent downloading files I can't imagine thes are way too much sources to handle.

I don't even know if the number of handled sources could interfere with the tcp listening. It's just a guess.

regards

Maybe it is a problem of firewall or router which can't handle well extensive load...

How many clients are waiting in your upload queue?

Seems to me, it's the same problem i have with Internet Connection Check.


Router i can exclude, because i do not have one.
I also think, it's not a problem with my firewall (Kerio, several versions), because it happens only after some days (~3-5) and there is no problem with other programs, at this time.

I reported a port hanging problem in interim. Could that be related to this?

Am I right in stating that while under normal circumstances everything is fine, if the port happens to get stuck for some obscure reason, the fault is unrecoverable and needs a reboot to fix?

Number of clients on the waiting queue differed from 900 to 2500.
Maximum is set to 3000.

@muleteer
No system reboot is needed to fix the 'port hanging'.
I just close eMule Plus and restart it. Back to high ID and a responsive tcp port.

I get the same problem and I had post a topic before.
It seems that it happens in the 1.1d and later versions.

No system reboot necessary. Only a restart of emule.

yesterday i did 1.1d fresh install on my friend's pc -> lowid on razorback2 -> e+ restart -> highid on donkeyserver2

can this be razorback2's fault?

edit: typo

Try connecting to Razorback2 manually (double-click on the servername in the serverlist).

both connection tries were manual ones (fresh install)

Happens sometimes when the server is very heavily loaded. Try again if you want to check, but DonkeyServers are very good too.

no no my idea was that other people's lowid problems can be server-side problems too :)

No, a LowID problem is when you ALWAYS have LowID.

someone try manually disconnecting from a server and reconnecting next time this happens (dont just restart emule).

Plus, didnt some people say that they HAD to restart windows?
What version of windows were they using?

Either its more severe in some versions, or its two bugs! (or one, or both of them, are false alarms... but i don't beleive so, I am just thinking of all the posibilities here)

I have had this problem increasingly lately. I leave emule running for anywhere from a few days to a week at a time. Every once in awhile i will return to find I now have a low id and the client had already tried connecting to all servers in the list before connecting with a lowid, often hours before I discover it. Still though, when I try to manually connect to a server, I am "stuck" in lowid.

Most times closing and restarting eplus fixes it, sometimes I have to use windows connection repair function to release and renew my ip connection and this always works. I have been using eplus for 2+ years, so of course all ports and forwarding are setup correctly, and I have a high-id 99.9% of the time.

forgot to mention, this happens even when I am not home and nothing else is running on the pc.

I reboot several times a day (not related to emule) so maybe I haven't seen this problem first-hand. I have encountered a couple of occasions where my client lost connection to a server and suddenly started getting LowID from the other servers. Usually after a few tries it starts getting HighID again, but for some users that condition might persist until a restart/reboot.

Can everyone who is having this problem please respond? There might be port/ adapter / application binding issues. Normally that's a good thing, but maybe under fault conditions the bindings are not being automatically destroyed as they should be.

I want to know:
1. your OS (XP SP2?).
2. your firewall (name and version).
3. connection type (LAN card, USB port, etc. - which is the physical port your computer uses to connect to the internet).
Thanks.

I can actually confirm this..

I have e+ running running at a place I only visit 1-2 times a week, and this machine does the same...

If WebServer had a "restart" option it woild be great

I agree, Fuxie. That would be a great feature as currently the webserver commands to close emule, shutdown pc and reboot pc are unrecoverable as far as the webserver interface is concerned.

There is a possible workaround: use startdelay to connect to the net and then start e+ at appropriate intervals after the pc is started/ rebooted. That should make e+ active again if the reboot option is used. Haven't had the time to test this yet.

But these are workarounds. What we want to know is why this is happening in the first place.

btw, does the webserver keep working when this happens, or does it also go bust? If it stays alive, does the option to connect to any server manage to connect?

Exactly..

Startdelay?? What's that?
BTW I dont' need to wait for the connection.. My router holds the connection to the internet, and even if the power was cut from both computer and router, the router (cisco 677) would have re-established the internet-connection before the PC was finished booting ..

...... and the how to fix it


Sure thing... Both WebServer and MobileMule are not dependant on eMule Plus being connected to a server.. Both work with HighID/LowID/No connection...

Fuxie: startdelay is a small utility that allows you to specify which programs should be started/launched after a start/restart of the computer with a configurable delay for each. An improvement on the Windows StartUp folder which creates a kind of free-for-all. If you put e+ in your startup folder, it will try to launch before the OS has finished loading, and the firewall might get stuck. With startdelay, you can start e+ say one minute after it is loaded on startup, which will ensure that the computer is ready when e+ is launched.

Now we know that the webserver port is not affected; only the ports used for the server seem to be getting blocked/ stuck on rare occasions.

@ muleteer

I fail to see why that should be needed...

I would recommend it as on startup the computer is fully occupied in normal bootup procedures (nearly 100% cpu and HDD usage). If e+ is launched at that time, it will have to compete with all the other tasks for resources. If it works for you, fine; it certainly won't do for me because my internet connection has to be initialized and authenticated before I try to use any app that connects to the net.

I'm talking about a "Restart eMule" feature...

The "Restart PC" feature is already included in WebServer and MobileMule..

So am I. The restart pc feature in webserver will only restart e+ if Windows is configured to automatically start e+ when the computer is booted. Sure, it can be done using the registry and temp files, but that is a minefield best left alone.

If you just want to restart e+ without rebooting the computer, I would still like to see it done using another application. This will allow e+ to unload completely, avoiding problems related to incomplete releasing of resources.

1. XP pro sp2
2. no firewall, linksys wrt54gs w/sveasoft alchemy
3. Onboard nforce3 nic

I have found one thing which seems to be helping me. I usually installed ipv6 tcp/ip stack on windows install for no reason really, on my last reinstall I forgot to do this. I didnt discover it until I was digging around trying to figure out what was going on, after installing v6 stack I was immediately connected to razorback2 (which I hadnt been able to do for 2 days) and have not dropped to lowid for a good while. Of course only time will tell if it stays this way. Could this be connected, or is this mearly a coincidence?

About delayed startup of emule on boot, I already do this. I use a program called DelayRun which starts emule and a couple other small things 60 seconds after desktop. I only do this so I get a usable desktop faster and everything is loaded before emule starts. I have done this for a long time, so I dont know what affect it would have otherwise.

the ipv6 shouldnt have anything todo with it but who knows - maybe that package really has fixed your ipv4, too.

Is it possible that there is a bug in the normal XP SP2 networking that gets fixed by the ipv6 update?

Well ipv6 doesnt fix it, it seemed to help for a bit, but its back. I am done guessing about what may be causing it since I dont know that much about such things, and ill trust you guys will continue to look into it to try and find out what is happening. Im considering trying the vanilla client to narrow down where the problem lies though, eplus or my system.