DHT: waiting for identification - utorrent

pasterma Posted messages 383 Registration date   Status Membre Last intervention   -  
pasterma Posted messages 383 Registration date   Status Membre Last intervention   -

Hello,

I have scoured this site, the internet, and many discussions but nothing works...

For a few days now my uTorrent is stuck with a DHT waiting for identification, whereas everything was going perfectly until now.

I have a Freebox Pop, and my uTorrent version is 3.6 on Windows 10.

I tried a port forwarding with Freebox OS - did I do it right?...

uTorrent is indeed checked in my firewall.

Anyway, I don’t know what to do anymore and hope someone can tell me where this is coming from and what the solution is.

Thank you all.

Georges

3 réponses

Bruno83200_6929 Posted messages 705 Registration date   Status Membre Last intervention   167
 

Hello,

You need to check your settings in uTorrent and double-check the port forwarding on your Freebox. I will give you the steps to follow:

Checking network settings in uTorrent


Listening port: Make sure the port used by uTorrent for incoming connections is properly configured. You can check this in the Preferences of uTorrent:


Open uTorrent and go to Options > Preferences > Connection.


Check the port used for incoming connections (by default, something like 6881). If the port is not open, it could prevent DHT from working correctly.


Enable the UPnP and NAT-PMP options in the settings, so uTorrent can automatically request port openings from your router (Freebox).


Checking port forwarding on Freebox OS


It’s possible that the port forwarding you attempted is not correctly configured. Here’s how to check this on Freebox OS:

Access the Freebox OS interface via your browser: http://mafreebox.freebox.fr.


Go to Settings > Advanced mode > Local network > Port forwarding.


Check that the port used by uTorrent (as seen in uTorrent settings) is correctly forwarded to the local IP address of your PC.


Example configuration:


Protocol: TCP/UDP


Source port: The port you set in uTorrent (for example 6881)


Destination IP: The local IP address of your PC (which you can obtain by typing ipconfig in a Windows terminal)


Destination port: Same port (6881).

If this is not enough, after checking the firewall, you can try temporarily disabling IPv6.


Some users have reported that disabling IPv6 can solve pending DHT issues. To disable IPv6:

Go to Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings.


Right-click on your network connection (Ethernet or Wi-Fi) and select Properties.


Uncheck Internet Protocol Version 6 (TCP/IPv6).


Restart your computer and see if that resolves the issue.

If it still doesn't work, you can also reset the DHT settings in uTorrent.


Sometimes a corrupted configuration file can cause issues with DHT. You can try resetting the configuration file:


Close uTorrent.


Go to the following folder: %APPDATA%\uTorrent.


Delete the files dht.dat and dht.dat.old.


Restart uTorrent and let the DHT file recreate automatically.

If it still doesn’t work, I don't see.


1
pasterma Posted messages 383 Registration date   Status Membre Last intervention   1
 

Dear Bruno,

Thank you so much for this incredibly complete, precise, and detailed response.

But I'm not going to do any of that because... everything is working again like before!

I didn't do anything more, and suddenly after yet another restart of uTorrent, I saw 486 nodes and it's back up and running.

I don't know why it bugged for 2 days, nor why, in the middle of all this, the issue disappeared.

And I'm not going to look for it either... I've already spent so much time trying to resolve the issue in vain.

In desperation, I came to ask for help here.

In any case, I will keep all your information and procedures carefully just in case.

Once again, thank you very much for your time :))

See you soon,

Georges

0
pasterma Posted messages 383 Registration date   Status Membre Last intervention   1
 

Good evening

Well here it is...

I thought it was resolved... but no

It's starting again, I have exactly the same situation as initially described.

During the first appearance of the issue, I tried a lot of things without any results.

And then suddenly it worked again without me doing anything.

So here I am back to square one again

I just want to understand but that's not happening

0