Quote from: nemo1618 on June 08, 2015, 07:21:11 PM

Quote from: Sebastien256 on June 08, 2015, 06:54:27 PM

Quote from: nemo1618 on June 08, 2015, 04:02:35 AM

In order to become a host, peers need to be able to connect to you on your host port. If you're behind NAT (and most of you are), you need to set up port forwarding on your router. Most routers have a web interface available at 192.168.0.1 or 10.0.0.1 where you can configure port forwarding. There are lots of guides for how to do this, e.g. www.portforward.com.

You can use this site to test your connectivity: http://www.yougetsignal.com/tools/open-ports
Enter your host port (default is 9982) and hit "Check." If it says that the port is closed, you cannot become a host until it's open.

Port forwarding is a pain and it would be nice if you didn't have to do it. This is where technologies like UPnP and NAT-PMP come in: they automatically forward your ports so you don't have to monkey around in your router settings. We are working to add UPnP to an upcoming release, but we don't have a precise ETA yet.

Why do I also get this annouce error? But both port 9981 and 9982 on my computer are correctly forward and pass the test of that webpage. Any possible reasons? Thanks for helping.

Hmm. It's possible that you need to open the port on your firewall as well. Failing that, the only thing I can think of that would prevent connectivity is that the timeout for the test is only 1 second. If your latency is so high that it's taking more than a full second to ping yourself, you may see the "cannot announce" error.
I will extend the timeout in the next release. In the meantime, I can create a special win64 binary with an extended timeout. Let me know if you're willing to test the fix.

Ho, forget to tell, I also tried with firewall off and I still get the error. So firewall is not the cause.

I would test the fix.