Failed to join stream: Screen Share session already registered // Screen share session is stuck on loading

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.

6 Likes

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.

Solution :

REWRITTEN by @gouthamravee

  • 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
  • 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
  • Click Filter
  • Click Kill

Source: https://docs.netgate.com/pfsense/en/latest/nat/static-port.html

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!

6 Likes


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?

best regards

1 Like

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.

Same is happening to me, also using a Fritzbox. Could it be related to the router?

Hello all,
I’m jumping into this thread to ask for some information. I have a Fritzbox router too. Is this a matter of enabling certain ports? Has anyone managed to fix this?

An error pops up in the top-right corner of the screen share: “Quality (current) - 0x0 fps,” “Target bitrate - 0 Kbps.”

Hi, I’m having an issue with screen sharing in TeamSpeak 6. When I start a screen share, it shows in the connection info that capture time is 2ms and preprocessing time is 2ms, but the encoder field is completely empty and current quality shows 0x0 0fps with 0 Kbps outgoing. No packets are being sent at all.

My friends trying to connect to my stream get stuck in infinite loading.

What I’ve tried:

  • Disabled Cisco OpenH264

  • Switched H264 encoding from NVIDIA NVENC to Internal Software

  • Disabled hardware acceleration completely

  • Added firewall rules for UDP ports 9987 and 2010-2020

  • Full reinstall of TS6 including AppData folder cleanup

  • Forcing TS6 to run on NVIDIA GPU via NVIDIA Control Panel

My setup:

  • Laptop with Intel integrated GPU + NVIDIA GeForce RTX 4060

  • Windows 11

  • TS6 latest version

  • Server: eu-east-1

  • Other users on the same server can share screen fine