Mldonkey too old? LowID?

[Dave M G]

Colin,

>Do try to get MLdonkey working with DHCP; it will spare you a lot of
>trouble. 
>
Okay, I believe you if you say that having DHCP is better.

I'm not sure why my router sometimes assigns a different local IP. I 
only have the one computer and one net card. The router itself seems to 
take 192.168.0.1, so the computer should get 192.168.0.2. But I reboot 
my computer almost daily (otherwise I can hear the fan while I'm trying 
to sleep, which is bothersome), and about a third of the time it assigns 
my computer 192.168.0.3, and once in a blue moon it will give it 
192.168.0.4. I've looked, but I can't determine if the router has any 
way on it's side of only assigning certain IP addresses.

But, let's assume that usually I get 192.168.0.2, so most of the time, I 
should have the appropriate ports assigned to the computer's IP.

 From the HighID wiki page, there was a page to test the ports. I have 
Mldonkey running, I have the ports mapped to my current IP, it should be 
working. Here are the results of that pages port test:
Error: TCP port 4662 is unavailable. Make sure your firewall or router 
is allowing/forwarding this TCP service port and your ED2K client is 
running (i.e. aMule, eMule).
Detailed Error Message
TCP Error 111 Connection refused
Error: TCP port 4672 is unavailable. Make sure your firewall or router 
is allowing/forwarding this TCP service port and your ED2K client is 
running (i.e. aMule, eMule).
Detailed Error Message
TCP Error 110 Connection refused
Success The TCP port 6346 is available. You should be able to use the 
ED2K P2P service without any problems.

So... my understanding of these results is that my Gnutella connection 
on 6346 is running fine, which indicates to me that the port forwarding 
on my router does work.

However, despite mldonkey being up and running, and I have double 
checked to make sure that the ports mldonkey is using are the same ones 
I've mapped (4662 and 4672), it's not connecting.

So would I be correct in assuming that the problem is a configuration 
issue with mldonkey itself?

And if so, can I probe or test mldonkey for problems?

--
Dave M G