mldonkey-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-users] Re: Funny mldonkey connection problem


From: Ian Sidle
Subject: [Mldonkey-users] Re: Funny mldonkey connection problem
Date: Fri, 28 Feb 2003 11:32:44 -0800

The problem is as follow:

I run mldonkey in my laptop on my house dialing to the internet by modem
and I can use it without any problem, but when I try to use mldonkey in
my office ussing the LAN connection I cannot connect to any server, and
the funny thing is that when I switch to Windows (I have both, Debian
Sid and windows on the same machine) and run Kazza I can download with
this software, so I think this is not a firewall issue (I'm not 100%
sure about this) I try to tell mldonkey that I'm behind a firewall but I don't found this option to test it. Or to use a proxy server to run some
tools like tcpdump and the like.
First - your problem is that mldonkey does *not* use the kazza (fasttrack) network. MlDonkey works with the edonkey2k/emule network. So thats probably part of your problem.

It really depends on how the firewall is setup on if it can work or not. For example, maybe the sysadmin uses kazza and so opened it up for himself but has everything else closed. Although really the admin should have made it only open it for his personal computer in the first-place. Perhaps you could go and talk to your sysadmin to open up the ports for you.

Of course, there is the moral/legal questions of if you should run any p2p programs at *all* at the workplace. Digest version - you are being paid to work there so you should actually be working instead of messing around.

Could you help me please to understand how mldonkey works and how to
make it work on my LAN?

I believe there is some flags you have to change in the config/ini files to allow it to connect to the network behind a firewall/NAT. I'm not at a machine that has mldonkey so I can't look them up.

-Ian Sidle





reply via email to

[Prev in Thread] Current Thread [Next in Thread]