I was using Windows 2000 Pro or the past and BitComet runs without any problem. However recentlyy system got messed up so I formatted and installed Windows XP Pro, and BitComet runs smoothly except one problem : it can’t connect to the DHT. I have enabled all the DHT related stuf in the preferences, but still the DHT status remains grey and can’t connect to the DHT network. What could be the problem?
Ok, what service pack are you running? Do you have a firewall running?
if you are using the firewall that comes with windows xp, go to Control Panel → Windows Firewall → Exceptions (tab) → tick the boxes for BitComet.
I’m using SP2, and McAfee VirusScan + Agnitum Outpost Firewall, the same as on my old Win2000 system. I have added BitComet rules in the Outpost Firewall to allow all TCP and UDP communications. Currently everything else (downloading files through BT, browsing the web, previewing, etc.) is working fine except the DHT. 
From what I have read in the FAQ’s; it says that is only used as a backup router/tracker. If the BitComet s/w is running correctly it says we should never need it. I have the same on my display too!
McAfee is one of the best Virus Scanners around, this is confirmed by tests I’m not just being a fanboy.
Outpost on the other hand is known for causeing trouble. If you’re already running McAfee you should try McAfee personal firewall or Kerio which is also very good.
well, BC has run flawlessly under Win2000+McAfee+Outpost in the past, and currently un WinXP it also runs flawlessly EXCEPT DHT. Also I have tried disable Outpost and uninstall it, and reboot the system, but the problem remains, the DHT status at the bottom just remains grey and not connected, everything else seems fine. I wonder what might be the cause of the problem?
Um, did you turn DHT on in the settings?
Yup, I have the enable public DHT network setting turned on, and I have tried the “turn off, restart, then on” method suggested in the FAQ, it just remains grey XD
Have you disabled Windows Firewall? Are you using a private .torrent maybe?
nope
I have the exact same problem
I’m Running bitcomet 0.70 stable on winXP with built-in firewall
i checked all the exceptions in the firewall and bitcomet.exe was there
i checked all the connection boxes including enable DHT
but it still doesnt work…
Here is my Log
Default tracker optimization rules file loaded.
IP rules file: ipfilter.dat loaded, 0 entries.
Start Listening at TCP Port:1024
Start Listening at UDP Port:1024
BitComet 0.70 is running on:
CPU : Intel® Pentium® D CPU 2.80GHz 2942 MHz
RAM size : 511.48 MB
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Windows XP ICF Status: Firewall TCP port is opened.[Local Area Connection]
Windows XP ICF Status: Firewall UDP port is opened.[Local Area Connection]
Windows XP WF Status: TCP Port is not opened in Windows Firewall.
Windows XP WF Status: add TCP port in Windows Firewall Succeed.
Windows XP WF Status: UDP Port is not opened in Windows Firewall.
Windows XP WF Status: add UDP port in Windows Firewall Succeed.
Update Local IP: 192.168.2.109
Windows XP ICS Status: cannot find working ICS.
UDP tracker report: WAN IP = 24.84.xxx.xxx (no hacking for u)
Windows XP UPnP Status: device not found!
You need to find out whether your listen port is open for UDP packets.
Reading and folllowing the instructions for UDP, test it here.
If it’s blocked, then a firewall somewhere is blocking it, and you’ll need to figure out which one.
DHT is absolutely not necessary. It’s nice to have because it gets you more peers if the tracker isn’t giving you enough, or is unresponsive, but in the normal course of things it’s not needed at all. It is also disabled on many torrents, which is the choice of the torrent creator and can’t be changed.
Hm, well reading from yeya’s post, he has read our FAQ on this Not Connecting to DHT issue, which also incorporates the UDP solution.
Hm, did you try uninstalling Version 0.70 and trying version 0.64 or the BitComet Beta releases?
If any more users can tell us that the DHT Network isn’t really enabling itself on 0.70, we may need to fix for 0.71 release.
The UDP port is opened all okay.
I have tried BC0.64 and the latest 20060824 beta, and this is the result :
BC0.64, same problem, the DHT status just remains grey.
20060824beta, the DHT status shows green, but it says “DHT connected : 0”, and when downloading (from public tracker), the trackers window shows “DHT : n/a” :unsure: