Failed to join stream: Screen share session is stuck on loading

TeamSpeak 6 Client
, , , ,
1

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.

18

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!

101

Hello, I’m the owner/admin of an Official TeamSpeak Community, running TS6 6.0.0-beta7. According to the support article “Current Community Options,” Official Community servers should include “all the latest TS6 features like Screen Share functionality.” However, we can’t get this working properly. The person sharing their screen starts the stream normally without issues. But whenever someone tries to join/view that stream, it gets stuck indefinitely on “Connecting…”. We’ve tested this with different people sharing their screen (not always the same person), and the result is the same every time, only the viewer/joiner side gets stuck, never the sharer. I also checked the Server Settings and noticed the “SFU Endpoint” field (used to enable server-side streaming) is empty, with no visible way to configure it from the myTeamSpeak Community management panel. We’re currently limited to P2P mode. Has anyone else run into this specific issue, the viewer being unable to connect to an active stream? Is this a known P2P connectivity bug, or could it be related to the missing SFU endpoint? Thanks in advance!

102

Hello,

I am experiencing a very inconsistent issue with screen sharing in TeamSpeak 6.

When I start sharing my screen, the stream may work normally for some time, but then suddenly drops to 0x0 resolution, 0 FPS, and 0 Kbps upstream. At that point, the stream essentially stops sending any data.

The behavior is extremely inconsistent and I have not been able to identify a reliable pattern. It can sometimes even change when I interact with the TeamSpeak client itself. For example, simply moving the TeamSpeak window to another monitor can sometimes cause the screen stream to stop working.

I have also noticed that the behavior can sometimes vary depending on the number of people in the channel, although I cannot confirm that this is directly related to the issue.

I have already tested different encoders:

  • NVIDIA NVENC

  • Intel encoder

  • Internal Software encoder

The issue occurs with all of them.

I have also tested different bitrate settings, ranging from 640 Kbps up to 10,000 Kbps, and the problem still occurs. Because of this, the bitrate itself does not appear to be the cause.

What makes this more interesting is that other users on the same TeamSpeak server are also experiencing screen-sharing problems, including users who appear to be on different computers and networks. This makes me wonder whether there could be an issue related to the screen-sharing/P2P connection itself, rather than something specific to my system.

I also found this existing thread describing a very similar issue:

https://community.teamspeak.com/t/failed-to-join-stream-screen-share-session-already-registered-screen-share-session-is-stuck-on-loading/55152

In particular, the reports of the stream getting stuck at 0x0 / 0 FPS / 0 Kbps seem very similar to what I am experiencing.

Could this potentially be related to the P2P/NAT/connection handling used by TeamSpeak 6 screen sharing?

Has anyone experienced similar behavior, or is there any logging/debugging information I can provide that would help determine why the screen-sharing stream suddenly stops sending data?

Thank you!

103

Im having the same issue as you. Im also self hosting a server.

voice connections works fine, but screen sharing is loading infinitely.

104

Hey, with the next update you will be able to set a custom port range for streams:

Maybe that will fix your problems.
In the future, there will also be an SFU that routes the streams through the server instead of via P2P.

105

0x0 suggests there’s a problem with the decoder. Or that no viewers have joined the stream yet. What’s the situation on the viewers’ end? Do they just see a gray screen, or are they still trying to join the stream and are stuck there? Have the people watching tried different decoders yet?

This is what a stream info looks like when no one is watching yet. Is it the same for you, or is the “target” at the top already 0x0 for you?
image

With the next update you will be able to set a custom port range, maybe that helps until the SFU releases (if the problem is p2p related and not encode/decoder specific)

106

I’m actually experiencing all three situations.

Sometimes the viewer sees a gray screen, sometimes another person just gets stuck loading, and occasionally someone can actually see my screen, but then the stream suddenly freezes. When that happens, the stream goes to 0x0, 0 FPS, and the bitrate drops to 0 Kbps or fluctuates between around 10–100 Kbps.

And regarding your screenshot, yes, mine also shows 0x0 and 0 FPS even when nobody is watching my screen.

Screenshot 2026-08-18 025313

107

Hello, is there any release date for this version?

108

I can’t view shared screens in TeamSpeak 6. When I click to watch, it just stays stuck on “connecting” indefinitely. I tested the screen sharing feature on another network and it worked, but for some reason, it simply doesn’t work on my main network. Here are some things I’ve already tried:
. Disabled the network/Windows firewall
. Changed the DNS
. Disabled the router firewall
. Disabled the router’s ALG

Nothing seems to work. I can hear others via voice chat, but I’m unable to use the screen sharing function. Can anyone help me?

109

If it works on another network, then TeamSpeak itself is probably not the main problem here. I would guess something on your home network is interfering with the P2P connection. Maybe try a hotspot or VPN once and see if it connects normally there.

110

on connection info

Screenshot 2026-08-23 202736
Screenshot 2026-08-23 202736675×685 43.3 KB

its saying Quality (current ) 0x0 0fps and target bitrate 0 kbps

111

Hello @sydbot and welcome to the TeamSpeak Forum,

Since you can watch other people streaming, I would first check the local screen share settings. Maybe try a different source, restart the client, update your graphics driver, and take a look at the screen share hardware acceleration / encoder settings in TeamSpeak 6. You could also try switching to another available H.264/AV1 encoder, reset the encoder settings, or temporarily disable hardware acceleration to see if that changes anything.

Could you also share your OS, GPU and TeamSpeak client version? It would also be helpful to know if this happens with every source or only with a specific window or monitor?

112

im tried all, and my graphics driver are updated. but i’ll try to reinstall them.

My OS is WIN1, GPU AMD RX 9060XT, client version is 6.0.0-beta4.1

113

Could you open Settings → Video and expand the advanced hardware backend settings?

I am mainly interested in which encoder TeamSpeak is using for H.264 and AV1 with your RX 9060 XT. If possible, post a screenshot of that section.

114

image
image946×604 46.2 KB

115

Could you ensure your logging is set to Debug or Trace in the Developer Tools (Search for Developer Tools in the global search bar in the top left).

Then, could you provide the logs just after someone joined your stream (so we can see any failures for the newly spun up encoder that should encode the video stream)?

(You can also just send me via PM the whole log)

116

How do i get my logs, i set to trace but i can’t find where my log is

117

You can find them here:

%localappdata%\TeamSpeak\Logs\Default

118

Screen sharing does not load

I have captures that show the times. And this is still ongoing.

More than 5 minutes (and counting) to TRY to open the screen sharing. Please fix that!