Forum Discussion
Question about connection Microsoft Teams behind Firewall NAT device use Single IP Address
Hi Folks : We use the Foritgate as Firewall , Provide NAT function let internal network user (About 80Users)to connect to internet. We have config Fortigate use a single Public Internet IP address ...
- There is no limitation about concurrent connections behind a single IP address. What I believe that you are seeing is simple "not enough bandwidth" Screen sharing is one of the most network intensive things that you can do, and you see the results.
If you are looking at routers or other devices to measure the throughput, then be careful with what they are measuring. They are often measuring usage over a period of time, like 15 minutes, which isn't going to answer your needs.
Also, it is possible that it isn't your Internet connectivity alone, it could be the Fortigate or any other devices in the path.
Hi Chris , Thanks for reply and great Blog article
I also have been read the document you mention.
I think My issue is not relative to PAT or NAT address pool size.
Because my internal user only have 80 User. The NAT Address pool size can support
up to 5,000 User.
Anyway Thanks.
I also have been read the document you mention.
I think My issue is not relative to PAT or NAT address pool size.
Because my internal user only have 80 User. The NAT Address pool size can support
up to 5,000 User.
Anyway Thanks.
Donnei_Tsai1128 I would be suspicious of the Fortinet doing any kind of inspection, the volume of Teams media traffic typically quickly overwhelms any capacity on any firewall. Specifically Microsoft recommend against and won't support any inspection of media traffic.
I would simple allow 3478-3481 outbound without any interference on the firewall, the only supported way to make Teams work well.
Hi Steven. Thanks for reply!
Yes. Our FortiGate Firewall have config Policy to allow Microsoft Teams traffic pass quickly
don't use any SSL Inspection, Security Inspection.....and UDP port 3478-3481 is work
our last to doubt was Ascenlink (WAN Load balance device)
We will try to let Teams traffic not pass through this device and monitor the result.
