Outline · [ Standard ] · Linear+ eMule Plus 1.1 suddenly goes LowID

[muleteer]

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

[eorg]

both connection tries were manual ones (fresh install)

[muleteer]

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

[eorg]

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

[muleteer]

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

[taltamir]

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)

[rgreen83]

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.

This post has been edited by rgreen83: Jun 11 2005, 22:27

[muleteer]

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.

[Fuxie - DK]

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 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

[muleteer]

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?

[Fuxie - DK]

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.

Exactly..

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.

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 ..

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

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

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?

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

[muleteer]

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.

This post has been edited by muleteer: Jun 12 2005, 14:19

[Fuxie - DK]

@ muleteer

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

[muleteer]

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.

[Fuxie - DK]

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

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