How to Optimize Your OWS Connection Method

Try a Different DNS Server

1. We typically recommend using Google’s DNS due to its innate ability to crawl cloud services. IPs are as follows:

   • 8.8.8.8

   • 8.8.4.4

2. In some cases you may need to Flush DNS: How to Flush DNS

Evaluate your OWS Connection Method

1. Local IP Connection - If the recorder and client are on the same LAN, using a Local IP Connection would be the fastest connection method. To use a Local IP Connection, you can direct into the IP address of the recorder, or through OWS LAN Smart Forwarding: LAN Smart Forwarding

2. Direct Connection / Port Forwarding - You can set up a direct connection to the recorder for optimal remote connection speeds. This will have no relay timeout. More information on Direct Connection found here: Advanced Network Management

3. Peer to Peer - Enabling Peer to Peer will enable Web Services to provide the client and recorder information needed for the client to connect directly to the recorder. This allows video to be streamed direct.

4. OWS/Relay - This is the Standard Connection method. This connection method will utilize the relay servers for a connection to the recorder. This will have a Relay Timeout. More information found: Relay Timeout

Web Connect Region

By default, our recorder's OWS connection settings have it automatically pick up which relay to use. Sometimes selecting the most applicable option can be advantageous to secure a connection. Sometimes even selecting another region than the most applicable can kick the connection into gear. If looking at a customer account, go to Management>Recorders>Recorders, then to Remote Network Settings. The last option labeled Web Connect Region is what you’re looking for.

Antivirus and Popup Blockers

Occasionally, users will have issues interacting with the thin client and the issue can be traced back to either an antivirus or a pop-up blocker. Typical issues are not being able to login, being met with unneeded login screens when navigating, and camera views/grids not loading correctly. Try disabling antivirus/pop-up blockers and see if the issue persists.

Packet Inspection

Ensure you’re not dropping packets or that the connection isn’t being refused somewhere along the line. If either of those turns out to be true, it may be worth looking into allowlisting. You can find our allowlisting requirements here: OWS Network Requirements