Actually, we’re suggesting that you downgrade to 1.22 and see if the problem goes away. You’d have seen that in the main thread. That’s why it’s a good idea to keep conversations in a single thread rather than scattering them all over. Any further traffic on the issue should go in that thread.
The trouble with textbook lessons is that you can’t just read the first chapter and forget about the rest. The problem is a lack of understanding on your part about how ports are used in Internet traffic under TCP and UDP.
BitComet uses one “listen” port for its bittorrent function. This is a port which is unblocked by any firewall. It’s purpose is to allow peers (this is peer-to-peer) to contact you directly.
Almost all other internetting that you do, does not require an open port.
Instead, you and your computer initiate all those other contacts. The other computer, usually a server, replies to you. This is how web surfing, email, chat, ftp, newsreaders, and just about everything else functions. You initiate, a server replies, then a conversation ensues until one of you doesn’t stops.
When your message goes out, it includes the port number on which the other party is to reply. Your firewall will accept a reply from that server on that port, but not from anyone else and not from that one on any other port. Unsolicited incoming traffic is blocked while solicited traffic is allowed. This is what a firewall does.
The message that you get from the server likewise includes the port number on which it is expecting your next transmission in this ongoing conversation. (Bear in mind that, although state is IMPLIED, it does not actually EXIST. The connections are all stateless. Many new people come to grief on grasping this point.)
Bittorrent, or your email client, or your web browser or your chat client, thus “uses” many ports. There is no exposure here because your firewall(s) block any traffic from any other source or incorrect port, allowing only the expected replies through.
You have doubtless studied that port number 80 is the conventional default for web servers. This is so because there needs to be a single port on which a web server can be found listening for new incoming connections. Once the connection is established between the web server and somebody’s browser, the traffic usually moves off of that port and onto others.
Thus, your browser, or chat client, or email client, or bittorrent client can and will “use” many ports, depending on how many connections each makes, how many each needs, how many each maintains, and finishes with/closes.
The answer to this question,
how many ports in real are needed for bitcomet to work fully ?
is “False”.
You need one open listen port for incoming bittorrent connections. You will also need a port for incoming eMule connections if you are using eMule or the eMule plugin. These are basically separate applications, and processes can’t share ports under Windows. HTTP and FTP downloads under BitComet do not require a listen port and are not peer-to-peer.
The number of closed, firewalled ports that your bitttorent client, or your email client, or your web browser or your chat client will use is effectively indeterminate. Not “unlimited”, there are only 65,000 ports, but constantly varying.
You may have multiple rules set up in your router, but if those rules are not active, then the ports they involve are not being opened by them. You only need multiple rules in certain rare cases, where the router requires you to choose either TCP or UDP, but not both, for a given rule. There, you need one for each. This is imposed by the router not supporting both protocols in one rule. Some don’t, most do.
Names for rules are for humans. You can name a rule anything you please, or nothing at all if the router allows that. The router doesn’t care, doesn’t ever reference the name. All that mattters is the IP address and the port number. Having multiple rules that open the same port to the same IP address is just silly. The port’s either open or not, and the second rule can’t do anything the first one didn’t barring the one special case of differing protocol
BitComet backup is fairly simply, modulo dealing with Virtual Storage. You need to locate the settings directory, which will nominally be in %appdata%, one way or the other. See the FAQ. Once you find that directory, simply copy all of the .xml files you find there. That’s all there is to it. Nothing in the registry, or elsewhere. Your settings and the current task list are there. The program and its configuration files + task list shouldn’t take up more than 18 MB or so. This varies because BitComet also stores a copy of the .torrent files for tasks in progress in a torrents subfolder in that path, so the total size can vary a little.
The actual tasks in progress are, of course, stored in their respective download directories.