ok great! I had trouble with mine as well, for some reason unless I had a static IP it would forward the port
naw I use cableone
still no joy
got it to work - with port forwarding - putting that here for the record
with the tool http://www.yougetsignal.com/tools/open-ports/, i get "Port 8905 is closed on 1xx.5.1xx.3". I will have to now check how can i open this port 8905. But even the standard http tcp port 80 also shows as closed, then how can i receive web data if its closed.
T Z Pardi
@yogk You can receive data over the HTTP protocol in your browser because the browser app sends data to the listening port in the web server as a TCP client, and then it receives the message back on the very same socket. So that is a send-receive topology on the TCP client socket. In order to receive data over the HTTP protocol (browser) you don't need a TCP listener, but you use a TCP client. (See my post and proposal about the WS problem in the Google group, which describes how to use such TCP client). So to get web data in your browser you never open a listening port. So don't be confused from that TCP client and TCP listener sockets are different things. For a P2P application you need a TCP listener socket. What you wrote clearly indicates that your TCP listener is not operational. I suggested this could be the issue. If you forward your port on your router then the Streembit client will be reachable by other peers. Thanks for trying :-) let us know if you need anymore help.
@zsoltpardi I tried streembit by running the exe file provided, however i am getting upnp port mapping error, for which i have disabled my firewall, even though i am getting this error. Please tell me where i am going wrong and what should i do next?