I’ve got a problem with the video streaming feature when trying to join a video stream in a private chat or group chat with a contact.
I’m trying to connect to the stream of my friend, but it says “Connecting…” far too long and after a little more waiting the “join” button on stream appears again, but when trying to join again, this time this error appears: “Failed to join stream: Screen Share session already registered”.
When closing ts6 and trying it again after a reopen, it still doesn’t work. This only happens with one of my two contacts. But this specific contact has the same problem with my stream.
My other contact is able to watch my stream without any problem and I also can watch his stream.
It seems the contact which hasn’t got the problem is also able to view the stream of my “stream-problem” contact and vice versa.
I’ve tried removing this contact, but after readding him again the problem still occurs.
I’ve also tried clearing the “%appdata%\Roaming\TeamSpeak” folder, but after logging in again it doesn’t seem to solve the problem.
Has anybody else got this problem? Can I do something on my side to fix this issue, or may this be a bug of the current build?
I know this ts6 beta just released, this issue isn’t critical at all.
I fixed the issue for myself, my fix might be different because of my network design but these are the steps i took to get it working, my firewall Pfsense rewrites source ports on both automatic and hybrid outbound NAT by default.
Name it teamspeak_screenshare or what ever you want
Change type to Port(s)
Paste 49152:65535 into the “Content” section
Give it a description if you want
Click Save
You can do this again and create a Host(s) alias for the device(s) running the TeamSpeak Client, that way you can screen share from all your devices without having to create additional NAT rules.
Navigate to Firewall > NAT > Outbound tab
Select Hybrid Outbound NAT
Click Save
Click Add with the up arrow to add a rule to the top of the list
Set Interface to WAN
Set the Protocol to match the desired traffic (e.g. UDP)
Set the Source to Single host or network and put the local IP address of the device you want to screen share from or select the alias if you created one before.
For Source Port select the teamspeak_screenshare alias
Leave Destination as any
Leave Destination Port as any
Set the Translation Address to Interface Address
Check Static Port to indicate that traffic matching this rule will retain the original source port
Click Save
Click Apply Changes
I didn’t have to do the steps before, but its possible you might have to. You can test screen sharing now, if you still have trouble first make sure the IP and ports match exactly as described here, and then try the steps below.
Navigate to Diagnostics > States
Enter the IP address of the device in the Filter box if a specific source was used in the rule
Click Filter
Click Kill
ORIGINAL SOLUTION
Navigate to Firewall > NAT on the Outbound tab
Select Hybrid Outbound NAT
Click Save
Click Add with the up arrow to add a rule to the top of the list
Set Interface to WAN
Set the Protocol to match the desired traffic (e.g. UDP)
Set the Source to match the local source of traffic, such as LAN Net or a specific device such as a game console IP address, or an alias containing multiple such devices
Leave the Source Port box empty, which indicates any
Set the Destination to match the traffic, if known, otherwise leave set to ‘any’
Set the Destination Port to a specific port or port alias, if it is known, otherwise leave the box blank for any
Set the Translation Address to Interface Address or an appropriate VIP if needed
Check Static Port to indicate that traffic matching this rule will retain the original source port
Click Save
Click Apply Changes
Navigate to Diagnostics > States
Enter the IP address of the device in the Filter box if a specific source was used in the rule
The issue was my firewall rewriting the ports for the p2p and STUN connections causing the connection failures, after forcing the the ports to stay the same as the source i can now stream with all my friends with no issues. Hope this helps!
New TS user here, just setup TS6 on my homelab server and so far it’s been great, except for screen sharing.
I’ve been testing with a friend who lives nearby, they’re on the same ISP as me, ATT.
I am not on a double NAT, and I have a static public IP, though I am using a domain and a reverse proxy. But afaik that doesn’t matter since screen sharing is P2P.
When I share something, and my friend watches, I get a red triangle error message on the screen share saying the fps is lower than target. When I look at the stream info I see that Quality (target) is 1920x1080 30FPS but Quality (current) is 0x0 0FPS.
I have the openH264 codec enabled, and HW acceleration enabled. I even tried disabling them and restarting the client, with no luck.
The same problem happens when my friend is screen sharing, and I try to watch, except on my end all I get is an endless ‘connecting’ spinner.
My client side setup:
OS: Windows 11 Pro 24H2 x64
CPU: Ryzen 7 3700X
RAM: 64GB
GPU: Nvidia 1070ti 580.97
After more research I believe this is because of my firewall, opnSense. I don’t have anything like NAT-PMP or upnp enabled, so TS won’t be able to punch holes through my firewall.
Anyone have experience setting up a TS client behind opnSense or pfSense without NAT-PMP, upnp?
Google was nice enough to link to a random post from that thread instead of the post marked obviously as the solution, but w.e.
I improved the directions a little bit to be more specific about what the NAT rule is doing.
Solution:
Navigate to Firewall > Aliases
Click the + icon to create a new alias
Name it teamspeak_screenshare or what ever you want
Change type to Port(s)
Paste 49152:65535 into the “Content” section
Give it a description if you want
Click Save
You can do this again and create a Host(s) alias for the device(s) running the TeamSpeak Client, that way you can screen share from all your devices without having to create additional NAT rules.
Navigate to Firewall > NAT > Outbound tab
Select Hybrid Outbound NAT
Click Save
Click Add with the up arrow to add a rule to the top of the list
Set Interface to WAN
Set the Protocol to match the desired traffic (e.g. UDP)
Set the Source to Single host or network and put the local IP address of the device you want to screen share from or select the alias if you created one before.
For Source Port select the teamspeak_screenshare alias
Leave Destination as any
Leave Destination Port as any
Set the Translation Address to Interface Address
Check Static Port to indicate that traffic matching this rule will retain the original source port
Click Save
Click Apply Changes
I didn’t have to do the steps before, but its possible you might have to. You can test screen sharing now, if you still have trouble first make sure the IP and ports match exactly as described here, and then try the steps below.
Navigate to Diagnostics > States
Enter the IP address of the device in the Filter box if a specific source was used in the rule
I just switched to teamspeak after using discord for some years. However im noticing that screensharing is not working when trying to screenshare to my German friend. (Im from Sweden)
It simply just loads forever saying connecting and I am wondering is there a good and simple fix for this in any way?
Any help is more than enough so please tell me what I could do!
Weird title but I do not know how else to explain it, people in the server cannot connect to view my stream. It stays at connecting for them, on my end I get some sort of error from the stream connection info when they attempt to watch. Judging by the caution sign it looks like an encoding issue, when going to the video encoding in video settings a selection is greyed out, that is not the case for a friend with a similar GPU and can stream just fine.
The stream setting is set to P2P, although I have tried every possible connection solution I could.
I have updated all the drivers I could like NVIDIA drivers, and completely reinstalled TeamSpeak 6 still with the issue occurring.
Any help is greatly appreciated.
Here is a photo showcasing the problem or what the error is saying.
This is very likely a connection issue. P2P connections are sometimes a bit tricky to initialize. Check out the solution in this topic, it seems to have helped a buch of people
Me and my friend is both experience the same issue when trying to screen share. When starting stream both streams are stuck in connecting and we can’t see each others screens and error stating “FPS lower than target (0<30).
Server selfhosted, but I guess that is not the issue.
Not to provide a “Reddit” answer and not sure if I can post links here, but you can search for TS6 Streaming stuck connecting and you will find a post where a guy covers the needed PFSense firewall config for the new client does P2P for connecting. (it covers the issue to a deeper level on whats being blocked) Its likely that one or both of your firewalls are not allowing the connection to happen. If you are on a dorm or some other provided network, until they implement “server” connection brokering, it’ll likely not work. Using UPNP on your firewall may also work… but id suggest not doing that without understanding what that feature does. Id triple check to make sure its not an OS thing… saw someone else talking about Linux to Linux streaming on the same network.
For over 24 hours now me and my friends are unable to see each others streams, when i click on a stream it just shows the image below and it stays like that. The streamer can see that their stream is live and working. My friends noted that they can sometimes enter a stream, seemingly by luck, but then it could stop working randomly or if more than one person tries to watch the same stream. Streams worked perfect before all that.
I tested streams in my own self hosted community, other servers and in dms. None work for me or my friends.
We also tried turning off hardware acceleration.
I’m not sure what the issue is. Are the servers just overloaded and this is the effect of it? Or are there other things worth trying for a fix? I havent seen any post about this and i cant tell if we are the only ones experiencing this or if this is affecting everyone.
I’m new to teamspeak and all this technical stuff. Any help would be appreciated. thank you.
(sorry if this is posted under the wrong topic)
This is the same issue as described here. Your friend that’s connecting to the stream has a firewall (either in computer, in router or by their Internet Service Provider) which then breaks the stream for any other person that’s trying to watch the stream.
I suppose if you can, use the Server instead of P2P streaming.
thank you for your response. so far none of our streams load for anyone else no matter who the streamer is. and when i try to use the server to stream instead of P2P it is greyed out and wont allow me to select it, this is true for all my other friends. is this a community free trial limitation?
The server does not handle screen share at the moment. A server sided SFU is not implemented yet, but we are working on it.
If a screen share session can’t be established it will in most cases be a network or firewall issue. Check out the solution here in this topic. This is the only advice I can give you right now regarding connection issues…
I’m having a problem with screen sharing on TeamSpeak and I would really appreciate some help.
Whenever I try to share my screen, anyone who joins my stream (my friends) only sees it loading forever. The same happens to me when I try to join their screen sharing — it just keeps loading infinitely and never starts.
Important details:
We are using P2P mode
We do NOT have server-side screen sharing enabled
We are using the official 10-user plan from the TeamSpeak website
Even if we set the stream quality to the lowest possible setting, the problem continues
It happens with any user, not just one specific person
We already tried lowering quality settings, but it didn’t change anything.
Has anyone experienced this issue before?
Is this a limitation of the P2P setup, a port issue, firewall problem, or something related to the 10-user plan?
Any help would be greatly appreciated.
Thank you!
We are all on Windows 11 and using the latest version of TeamSpeak 6.
Hello,
Same here on selhosted beta TS6 server with free license.
Since my friends and I are in Russia, I attribute this behavior to the country’s blocking of the STUN protocol due to the ban on calls to Telegram and WhatsApp. As I read somewhere here on the forum, TS uses its own external STUN server (hosted by TeamSpeak team) to establish P2P connection between two clients behind a NAT.
The screensharing stopped working for us this week or last week.
But if you’re in a free country without network blocking, something else might be going on.
the demo doesn’t work for me, a friend connects to me, and when he logs in, he has an unlimited connection and when he does a screen demo, I have the same thing, and I see this data from the screen demo
Hi,
I’m using TS version 6.0.0-beta3.4. When someone starts a stream in a channel, I unfortunately can’t watch it. I send a join request, it’s accepted, and then all I see is a spinning clock icon (see attachment) and nothing else happens. I’ve already scoured the internet for solutions, from time sync to settings in my Fritzbox and hardware acceleration, and I’ve tried everything. But nothing helps. I simply can’t watch any streams, no matter which of my friends is streaming. Others, however, can see the same stream.
Any ideas?
Currently experiencing issues that prevent me from viewing streams for longer than 10 to 20 minutes at a time before getting very bad lag spikes/freezing which results in losing complete connection to teamspeak and on occasion leads to this error
“failed to establish connection to teamspeak server!
too many clones already connected”
It also can lead to me being temporarily banned from the server. I have hardline ethernet and my ping doesn’t shift past 55 at most.
