You should be able to connect to streams without opening any ports.

IPv6 sounds interesting, if you want i can look at it using teamviewer or skype to find a solution.
(I think it should be possible to work with ipv6)

I guess there will be no solution, but maybe some one has similar problems.

My provider switched [glow=black]secretly[/glow]to IPv6. Seems I can not add the port number correctly. I spend 3 hours last weekend to figure it out. The only solution would be to ask my provider to switch back to IPv4. Not sure if I need to for only to watch or been watched teasing. Is there any other way to set the stream up with IPv6?

Ok, I can confirm that your stream shows up on the site and in my client, but connecting fails ("connecting to server" is displayed).

Edit: As I can see that you have a german provider. This provider has different options - if you have an contract with DS-Lite, Portforwarding will not work. Can you check if your public IP of the router starts with something like 91.xx.xx.xx? If it starts with 10.xx.xx.xx, you are busted :-/

That's the example - So yes, xxx.xxx.x.x[color=#FF8000][b]00[/b][/color] is my computer and xxx.xxx.x.x the router.
Of course I can connect to my local IP and see the chat, watcher count or video. The important thing is, noone can connect with my external IP.

So 192.168.0.200 is your computer? You should be able to connect to that while you are streaming.

[quote="dess"]
You can only connect to your local IP because of how NAT works (EX: 192.168.0.2).[/quote]
Taking these numbers as an example, then 192.168.0.2 is my gateway/router and I've forwarded the local IP / IPv4 192.168.0.200.

[quote="playsafe"][quote="dess"]
Next, when I'm connecting to my stream I can only see the crossed "Connecting To Server" window, requesting the cam doesn't do anything and writing in the chat won't be shown in the other chat window either - so this should be an issue with port forwarding(? See my screenshots on the previous page, where I've configurated the port fast forwarding with my Lokal IP)[/quote][/quote]

You can only connect to your local IP because of how NAT works (EX: 192.168.0.2).

[quote="dess"]
Can you view your own stream?

If you can't then your firewall might be the problem. If you can, then port forwarding is the problem.[/quote]
I can directly connect to my stream using the Local IP, but I couldn't see my stream in the list or connect to it directly using the external IP.
I'm using the antivirus software Kaspersky, which controls the firewall. Teaseviewer is in its trustworthy groups and I've stopped Kasperskys' security for several minutes to see if I could connect to or see my stream without avail.

[color=#FF8000]edit²[/color]:
When I'm disabling the firewall [b]IN[/b] Kaspersky, not stopping the whole program, then I can find my stream in the list!
I've added my Lokal IP as an exception under Kasperskys' "Web-Anti-Virus" using [url=http://www.instar.de/faq_kaspersky]this tutorial[/url] and I can find my stream, too. But isn't it a bit risky?

Next, when I'm connecting to my stream I can only see the crossed "Connecting To Server" window, requesting the cam doesn't do anything and writing in the chat won't be shown in the other chat window either - so this should be an issue with port forwarding(? See my screenshots on the previous page, where I've configurated the port fast forwarding with my Lokal IP)

The register API i wrote had some problems during the recent days, maybe it declined valid streams, dont know what caused this behavier because it worked pretty well until the release...
I disabled the check, maybe now some of your streams can be registered on our server.
This way we may find some dead streams in the list, i will clean the list each day or write a process which does so.

[quote="playsafe"]That's where I'm stuck, too.
The weird thing is, I think that I didn't make any mistakes in configurating the port forwarding, because I've read several tutorials over the past years, which never worked - eg for p2p online games and am guessing that other configuration do conflict.[/quote]

Can you view your own stream?

If you can't then your firewall might be the problem. If you can, then port forwarding is the problem.