Overview
This article describes the Procedure for verifying whether the ACL is operating correctly during the initial setup of Mesh Network.
Notes
- Please check the required items according to the service and usage purpose.
- The content of this article is based on product information as of September 2026 and may be changed without prior notice.
- To verify connectivity, you must prepare at least two PCs or servers: a source and a destination.
Table of Contents
- Prerequisites
- Operation Test (When Not Using Subnet Linker)
- Operation Test (When Using Subnet Linker)
Procedure
Prerequisites
Confirm that all of the following requirements are met.
- The client is installed on the Target PC or server to be tested.
-
The client is running on the PC and is Connected.
-
Run ［ipconfig /all］ on the server and confirm that the Runetale virtual network adapter and IP address are displayed.
-
In the list of devices and resources on the Mesh Network management screen, the Target device or resource is displayed with a status of "Connecting" or "Connected."
-
An ACL containing the registered source and destination has been created.
[Mesh Network] Creating a New ACL (Access Control List)
Operation Test (When Not Using Subnet Linker)
Ping Connectivity Test
Open Command Prompt, PowerShell, or Terminal, then run the Ping command from the source to the destination and check the response.
- Run Ping by specifying the Mesh Network IP address (100.64.0.0/10) as the destination.
- Run Ping by specifying the Mesh Network FQDN (example: Servername.runea0b2c3d4.rt.net) as the destination.
- If Split DNS is configured, run Ping by specifying the FQDN (example: Servername.sample.com) as the destination.
If there is no response, check the following.
- Whether the OS firewall on the destination is configured to block Ping.
- Whether the server specified in Split DNS can be reached.
- Whether the DNS port is allowed in the Mesh Network ACL for the server specified in Split DNS.
- [Mesh Network] Confirming That It Is Operating Properly
Various Operation Checks
Connect from the source to the destination using the actual method to be used, and confirm that various services and systems can be used through Mesh Network.
【Examples of Operation Checks】
- Connect using Remote Desktop by specifying the Mesh Network IP address (100.64.0.0/10) as the destination.
- If Split DNS is configured, connect using HTTP/HTTPS by specifying the FQDN (example: Servername.sample.com) as the destination.
- If the ACL allows only specific ports, also attempt to connect to ports that are not allowed and confirm that they cannot be used.
If there is no response, check the following.
- Whether the OS firewall on the destination is configured to block communications.
- Whether the OS on the destination (such as its binding settings) is configured to reject connections using the Mesh Network FQDN.
- [Mesh Network] Confirming That It Is Operating Properly
Operation Test (When Using Subnet Linker)
If the destination is a server or device under a Subnet Linker, the destination will have a private IP address. Therefore, if both the source and destination are on the internal network and can communicate without using Mesh Network, communication will be established over the internal network without using Mesh Network, making it impossible to test connectivity for communication through the Subnet Linker. Before performing the test, place the source PC on a network different from the destination, such as by using tethering.
Ping Connectivity Test to Servers / Devices Under the Subnet Linker
Open PowerShell or Terminal, then run Ping from the source to the server or device under the Subnet Linker and check the response.
- Run Ping by specifying a private IP address (for example, 192.168.0.101) as the destination.
- If Split DNS is configured, run Ping by specifying an FQDN (for example, Servername.sample.com) as the destination.
If there is no response, please check the following.
- Ensure that the destination OS firewall is not configured to block Ping requests.
- Confirm that the server specified in Split DNS can be reached.
- Confirm that the DNS port is allowed by the Mesh Network ACL for the server specified in Split DNS.
- [Mesh Network] Confirming That It Is Operating Properly
Verifying Various Operations for Servers / Devices Under the Subnet Linker
Connect from the source to the destination using the method that will actually be used, and confirm that various services and systems can be used via Mesh Network.
【Examples of operation verification】
- Connect using Remote Desktop by specifying a private IP address (for example, 192.168.0.101) as the destination.
- If Split DNS is configured, connect via HTTP/HTTPS by specifying an FQDN (for example, Servername.sample.com) as the destination.
- If the ACL allows only specific ports, also attempt to connect to ports that are not allowed, and confirm that they cannot be used.
If you cannot connect to an environment that is expected to be accessible, please check the following.
- Ensure that the destination OS firewall is not configured to block communications.
- [Mesh Network] Confirming That It Is Operating Properly
Translation Disclaimer
This article has been automatically translated from the original Japanese version for your convenience.
While we strive to ensure accuracy, we cannot guarantee its reliability or completeness.
In the event of any discrepancies or questions regarding the content, the official Japanese version shall prevail.