I am having an issue getting screenshare to work properly. I have tried port forwarding for the STUN ports, and the standard Teamspeak ports, but neither of those work. If I place my PC in the DMZ, my friend can connect. What ports do I need to forward to get this working correctly?
We use WebRTC for screen sharing and it does not use a fixed port, instead it dynamically negotiates ports during connection setup. The ports that are used should be in this range 49152 - 65535.
3 Likes
Is there anyway to limit which ports are used or set a dedicated one? I would prefer to not keep my PC in the DMZ, and the method which is currently being used will not work with my ISP/Router
Unfortunately not that I am aware of. Have you tried using a VPN?
2 Likes
Yes, I have tried using NordVPN and unfortunately it does not work either. I think it would be a great feature if we could control the ports, because P2P streaming is an awesome idea.
1 Like
I’ll add that to our FR list and we will evaluate if this can be implemented from a technical perspective.
4 Likes
This was already indirectly requested in another post, but I wanted to give it a proper thread for this specific feature request.
Currently, screen sharing will just choose random ports to try and establish the P2P connection, presumably in the ephemeral port range. This does not work if someone is using symmetric NAT where ports are changed during the translation process.
TeamSpeak should provide two settings: screenshare host start port and screenshare client start port. When set, these will force the client to try the defined port first, then the next port up, and so on to establish a connection. This allows users to anticipate which port(s) will be used by the client and therefore create any necessary outbound NAT rules to allow static port mappings for that traffic.
Example:
This is already a thing I have configured for Parsec. My home network uses symmetric NAT and this breaks Parsec’s P2P connections. Parsec allows you to set a custom start port for inbound connections (when hosting) and a custom port for outbound connections (when being a client). With these set, I now know which ports it will use, and so I can create an outbound NAT rule to keep those ports static when they come from my PC. This allows the P2P connections to be made.
If TeamSpeak allowed a similar configuration, we would be able to anticipate the port it would use for screen sharing and we would be able to configure our firewalls accordingly.
This is admittedly not a big issue as most people’s networks aren’t as restrictive and symmetric NAT is somewhat silly in a home environment, but it’d still be nice to have and I’m sure it has some utility for admins trying to deploy TS in more restrictive networks.