Broadband Tech > Filesharing Software > eMule & Zonealarm Configuration

eMule & Zonealarm Configuration

Don't forget UDP port 4672
I set them both in the Internet Zone and Trusted Zone Security.

reply to WildGod

reply to WildGod
Right on. Now I get it. I was able to do what you suggested and now I'll see if it makes a difference.

Thank you.

reply to WildGod
You talk about a timely post. Not 10 minutes ago I started having terrible problems signing onto any server and when I did it was a lowID. The mule had been running for about 5 hours at this point. I started getting paranoid that my ISP had done something, so I nabbed a new IP. Still lowIDs. So I started the mule over again and Allowed access in ZA and everything worked again. Somehow ZA lost some of the eMule settings. Weird. Think I may go with ZAP.

reply to WildGod
How low is your ID? I've been having trouble myself after installing the software 3 days ago. I've kept it running for 2 days, sharing a variety of what I thought to be attractive files. It now says: "01/23/03 17:50:46: Creditfile loaded, 233 clients are known"

Could my problems be simply low credits? Do I need to let it run for months and months before I get to a point where I can actually download?

What I get now is a ton of sources, all with the status of "Too Many Connections". Is it just that I don't rank high enough to warrant a connection?

reply to WildGod
Wow just happened again. Started having problems finding servers and when I did they were low ids. I think I may be going back to version 24b.

reply to Norville

said by Norville:

---

What I get now is a ton of sources, all with the status of "Too Many Connections". Is it just that I don't rank high enough to warrant a connection?

---

reply to WildGod
I can't seem to find a spot where I can raise my "UDP Request Limit" Is that the same as UDP port, which is set at 50? I'm running V0.25b

Thanks!

reply to Norville
carn..this has nothing to do with ZAP..but i wanna give ya a tip after you got that figured out.

Since your just starting..Pick a VERY popular file from sharereactor or filenexus..something like chicagX(on filenexus..ton of sources) or anything thats extremely popular and somewhat recently posted .

At first it might start off slow..wait a while till you have downloaded about 10mb-30mb and it will soon pop up in your shared window. Once there in your shared window right click it and put it on "release". Now you will get MANY credits for the same file your downloading(a credit loop). Your speeds should pick up. Dont download anything else but that one file at first. And the most important is to put that file on "release" in your shared window.

[text was edited by author 2003-01-23 22:12:54]

reply to Norville

reply to WildGod
storm64007, I tried your tip. I couldn't figure out what kind of file chicagx was so I just picked something new with lots of sources. I will let that go and see what happens. Thanks for all your advice.

somebodeez, thanks as well. You're right, it does look different. But it makes sense now.

Hopefully I'm on my way.

Storm knows his eMule stuff
Hope it works out for ya.

Maybe one of you experts can help me. I have Zone Alarm Pro on an ICS/NAT server (WIN2k) connected thru ADSL/PPPoE. I am running eDonkey on another computer on the internal LAN.
I've opened the ports in ZAP as described here, plus did "port forwarding" on the outside TCP/IP connection on the ICS server, for the appropriate ports.

After all of that, still the inbound connection isn't working. Connection test claims the computer is still on "stealth".

Is there a systematic way to tackle this?
TIA

I think you have things a little confused. The hosting machine's use of ZA should not make a difference to the client machine wanting to run eDonkey. It would make a big difference if the client machine was running ZA. In that case make certain the client setup is as discussed above in this thread.

My guess is that the ports 4662 and 4672 are not properly forwarded by ICS. Just be certain that when you forwarded the ports at the ICS server/host that the local i.p. was that of the client machine, and not that of the server; e.g. not 127.0.0.1, or the Gateway address. If it would be possible to use uPnP, then do so.

On a final note, the fact that you have ports forwarded does not automaticly mean that a port scan by a security scanner is going to show the port as "open." Remember that the scan is taking place on the Public WAN IP and not the individual LAN IPs of your various networked computers. NAT routing 'protect' those LAN-side addresses. Furthermore, if you have ICMP traffic disabled, then the best that they could appear is 'stealthed.' This has nothing to do with a valid edonkey connection. To test your edonkey/emule connection, use the connection test utility at www.edonkey2000.com.

[text was edited by author 2003-03-22 05:53:30]