Mldonkey too old? LowID?

[Zach]

it is not a had and fast rule that 4662 TCP is the tcp port for the
edonkey protocol.  That just is usually the port most clients are set
to use by default (in addition to 4672 udp).  However most clients can
be configured to use any ports (above 1024).  When you configure your
edonkey client to use a particular port, it will advertise that port
when it connects to the server to get a list of other edonkey clients.
 That way the other edonkey clients will know what port to contact
your edonkey client on.

Steve Gibon's (GRC) database probably wouldn't know about edonkey
ports since (a) they can be configured to be any port and (b) I doubt
there is an RFC defining the edonkey protocol.

At any rate--as I mentioned earlier have you tried configuring your
edonkey client and port forwarding to use different ports other than
4662 TCP and 4672 UDP?  Perhaps 34662 TCP and 34672 UDP?  Just as a
troubleshooting measure.

Also, check the amule wiki posted earlier in this thread.

On 2/2/06, Dave M G <martin at autotelic.com> wrote:
> Zach,
>     I tried the test again, as I noticed there was another button that
> said "look up specific port information".
>
> Here are the results of the ports I have tried to unblock:
> 6346 (Has TCP and UDP): gnutella-svc
> 4662: The GRC port database does not currently contain any specific
> information about this client port. (See below for a discussion of
> "client" ports.)
> 4672:    rfa, Purpose:  remote file access server
>
> So, 6346 and 4672 seem to have something there. But 4662...? Does the
> message mean that it's not recognized, or that nothing is there?
>
> --
> Dave M G
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
If you reply to a message I posted to a mailing list,
and you want me to see your reply, be sure to put my
address in the 'To:', or I might not see the message.