Connecting Master–Client ACTAtek Devices Across Different Networks (Regions)

1. Purpose

This guide explains how to configure ACTAtek devices in Master–Client mode when the devices are located in different networks or regions.

2. Prerequisites

• ACTAtek devices are powered on and accessible locally

• Internet connectivity is available

• Router access for port forwarding configuration

• Public IP address available (static or dynamic)

3. Step-by-Step Configuration

Step 1: Configure Remote Access (Port Forwarding)

Please refer to the official KB article:
https://www.jakinid.com/supportkb/knowledgebase.php?article=52

3.1 Web Access (Device Management)

This allows remote login to the ACTAtek web interface.

Configuration:

• External Port: 8080

• Internal Port: 80

• Internal IP: ACTAtek device IP

Examples:

• Master Device
  • Device IP: 192.168.1.9
  • Public IP: 10.190.120.203
  • Access URL: http://10.190.120.203:8080
• Client Device
  • Device IP: 192.168.1.11
  • Public IP: 15.170.120.207
  • Access URL: http://15.170.120.207:8080

3.2 Master–Client Synchronization Port

This is required for device communication.

Configuration:

• External Port: 8888

• Internal Port: 8888

Example Setup:

Step 2: Configure Master Device

1. Log in to the Master device web interface
   (Example: http://10.190.120.203:8080)

2. Go to:
   Terminal Settings → Master/Client Setup

3. Select: Master Mode

4. Enter:

   • Master IP: Public IP of Master device

   • Port: 8888

5. Click Submit

Step 3: Configure Client Device

1. Log in to the Client device web interface
   (using its public IP and port 8080)

2. Go to:
   Terminal Settings → Master/Client Setup

3. Select: Client Mode

4. Enter:

   • Master IP: Public IP of Master device

   • Port: 8888

5. Click Submit

The client device will begin registration to the master device.

4. Verification

• On the Master device, check Client List

• The client device should appear with status Connected

5. Important Notes

• Ensure both ports 8080 and 8888 are open

• Public IP must be accessible externally

• Dynamic IP users should consider DDNS

• Ensure correct network routing and firewall rules

6. Troubleshooting

Unable to access device webpage:

• Check port 8080 / 8888 forwarding

• Verify public IP

• Ensure HTTP port (80) is correct internally

Client not registering:

• Check port 8888 forwarding

• Confirm Master public IP is correct

• Ensure no firewall blocking

Attachments:
master_client_WLAN.png