IP Access Control

IP Access Control

Introduction

Define outbound network rules and related controls required for ScreenMeet Remote Support. This article consolidates allowlisting, protocol support, and verification steps.

Required egress allowlist

Create rules using FQDN/domain allowlisting as shown above. Apply to agents and end‑user devices that participate in sessions.

Network and protocol requirements

• IPv4 only: Connections over IPv6 are not supported.

• Environment model: Designed for single‑user environments; multi‑user environments are not supported.

TLS/SSL inspection

If TLS inspection is enabled, users may see “not secure” warnings due to certificate pinning, and Beam (unattended) will not connect. Bypass decryption for *.screenmeet.com. See the “TLS/SSL Inspection” article.

Example firewall objects

# FQDN objects
FQDN: *.screenmeet.com
FQDN: *.scrn.mt

# Egress policy (simplified)

ALLOW to \ service tls-443-tcp
ALLOW to \ service tls-443-udp 

Verification

1. From an agent workstation, sign in to console.screenmeet.com and start a test session.

2. From an end‑user device, join the session and confirm screen view/control as configured.

Operational notes

• Apply the same allowlist to VPN and proxy egress policies.

• Place allow/bypass rules above broad decryption or block rules.

• Re‑test after security stack changes or certificate updates.

Conclusion

Allow outbound 443/TCP and 443/UDP to *.screenmeet.com and *.scrn.mt, operate on IPv4, and bypass TLS inspection for reliable Remote Support connectivity.