When the Clients meets same meeting in One NAT IP

%3CLINGO-SUB%20id%3D%22lingo-sub-2005940%22%20slang%3D%22en-US%22%3EWhen%20the%20Clients%20meets%20same%20meeting%20in%20One%20NAT%20IP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2005940%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EBecause%20we%20use%20a%20closed%20internal%20network%2C%20we're%20seen%20externally%20with%20a%20single%20NAT%20IP.%20We%20have%20confirmed%20that%20the%20connection%20is%20not%20good%20when%20a%20few%20users%20currently%20use%20the%20internal%20network%20connect%20to%20the%20teams.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EHow%20many%20users%20with%20a%20single%20NAT%20IP%20for%20MS%20teams%20might%20experience%20disconnection%20during%20use%3F%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EIt's%20not%20that%20the%20connection%20isn't%20completely%20off.%20When%20one%20side%20is%20connected%2C%20the%20other%20side%20is%20often%20inaccessible.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EI%20checked%20the%20security%20equipment%2C%20but%20it%20doesn't%20seem%20to%20be%20related%20to%20it.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2005940%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2006678%22%20slang%3D%22en-US%22%3ERe%3A%20When%20the%20Clients%20meets%20same%20meeting%20in%20One%20NAT%20IP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2006678%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F908202%22%20target%3D%22_blank%22%3E%40heungall%3C%2FA%3E%26nbsp%3BTeams%20doesn't%20use%20that%20many%2C%20but%20you%20do%20need%20to%20think%20of%20all%20the%20other%20applications%20that%20use%20them.%20Outlook%20can%20commonly%20have%203-10%20connections%2C%20each%20web%20site%20that%20a%20client%20has%20open%20can%20have%20a%20connection%2C%20and%20then%20Teams%20can%20have%20some%20connections.%3C%2FP%3E%3CP%3EA%20single%20IP%20can%20provide%20about%2060%2C000%20connections%20(each%20connection%20uses%20a%20different%20port).%20which%20means%20that%20around%205%2C000%20users%20can%20wipe%20out%20a%20NAT%20pool.%20Your%20router%20should%20be%20able%20to%20support%20multiple%20IP%20addresses%20assigned%20to%20a%20NAT%20pool%2C%20of%20course%20that%20means%20that%20you%20have%20multiple%20external%20IP%20addresses%20available.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Because we use a closed internal network, we're seen externally with a single NAT IP. We have confirmed that the connection is not good when a few users currently use the internal network connect to the teams.
How many users with a single NAT IP for MS teams might experience disconnection during use?
It's not that the connection isn't completely off. When one side is connected, the other side is often inaccessible.
I checked the security equipment, but it doesn't seem to be related to it.

2 Replies

@heungall Teams doesn't use that many, but you do need to think of all the other applications that use them. Outlook can commonly have 3-10 connections, each web site that a client has open can have a connection, and then Teams can have some connections.

A single IP can provide about 60,000 connections (each connection uses a different port). which means that around 5,000 users can wipe out a NAT pool. Your router should be able to support multiple IP addresses assigned to a NAT pool, of course that means that you have multiple external IP addresses available.

@heungall 

 

As @Ed Woodrick suggested, most firewall NATs support a number of users between each source and destination.  Could you tell us what issues you're experiencing?  Does Teams stop working for other users? What errors are you seeing? Are there performance issues such as call quality problems?