tidal breach
The "port 16262 closed" error is specifically caused by the 16262 UDP port not being correctly opened either on the server owner’s router or in their firewall. I can only recommend making sure that you correctly port forward the UDP protocol 16261 and 16262 ports to your Local IP. Alternatively, it will show up if you use the "Use Steam Relay" option when connecting to a dedicated server. In which case it can be ignored, if the Steam Relay provides better stability over the direct connection.
Here are some good guides for it as well:
https://www.noip.com/support/knowledgebase/general-port-forwarding-guide
https://www.windowscentral.com/how-open-port-windows-firewall
If doing that still does not work, I can only recommend contacting your Internet Service provider to make sure that they allow hosting a server on your IP and that they do not block the 16262 port themselves.
mild osprey
