Skip to main content
日本語 简体中文 繁體中文

[Mesh Network] Confirming That It Is Operating Properly

Question

I installed the client or agent, but it is not working as expected.
Please tell me how to verify that the client or agent is operating properly.

Answer

Items to Check in the Mesh Network Administration Console

Checking ACL Settings

Verify that the intended ACL settings have been configured.

  • Check the ［ACL］ settings and verify that ［Source］, ［Destination］, and ［Protocol/Port］ are as intended.

For details, see the following article.
[Mesh Network] Editing ACL (Access Control List)

Checking Subnet Linker Settings

If the Target is a subnet linker, check the following items.

  • The Target subnet linker has the intended advertised routes
  • Hosts included in the advertised routes (such as servers and multifunction printers) can be reached on the intended ports from the subnet linker server

For details, see the following article.
[Mesh Network] Changing a Subnet Linker

Checking Split DNS Settings

If you have configured Split DNS, check the following items.

  • The registered domain name is correct
  • The IP address registered as the name server is correct

For details, see the following article.
[Mesh Network] Editing Split DNS

Items to Check on Clients and Servers

For Windows Server

  1. Launch ［Services］ and verify that the Runetale service is running.
    Screen for checking the Runetale service in the Windows Services screen
    If it is not running, try the following:
    • If ［Startup type］ is set to "Manual," change it to "Automatic" or "Automatic (Delayed Start)," then restart the server.
    • When attempting to start the service, verify whether it starts successfully.
    • Launch PowerShell with administrator privileges and verify whether it can be started by running the command listed in ［General］－［Path to executable］.
      Path to executable in the Runetale service Properties window

  2. Run ipconfig /all in PowerShell and verify that an IP address has been properly assigned to the Runetale adapter.
    Screen for checking the IP address of the Runetale adapter in the Windows ipconfig command output
    If a link-local address (169.254.x.x) is assigned, launch PowerShell with administrator privileges and run the following command to check whether the situation changes.
    For details about the command, see the following article.
    [Mesh Network] Runetale Agent Command Collection 

    > runetale up

  3. Launch PowerShell with administrator privileges and run the following command.
    Verify that the response includes the intended destination devices and resources.
    For details about the command, see the following article.
    [Mesh Network] Runetale Agent Command Collection 

    > runetale status

For Linux Server

  1. Run the following commands to confirm that the runetaled service is running and configured to start automatically.
    If it is not running, start the service.
    Screen for checking the runetaled service status on Linux

    systemctl is-enabled runetaled
    systemctl status runetaled

  2. Run ip addr and confirm that an IP address has been assigned correctly to the Runetale adapter.
    Screen for checking the IP address of the Runetale adapter in the Linux ip addr command output
    If a link-local address (169.254.x.x) has been assigned, start PowerShell and run the following command to check whether the situation changes.
    For details about the command, see the following article.
    [Mesh Network] Runetale Agent Command Reference 

    > runetale up

  3. Start PowerShell and run the following command.
    Confirm that the response includes the intended destination devices and resources.
    For details about the command, see the following article.
    [Mesh Network] Runetale Agent Command Reference 

    > runetale status

For Windows PCs

  1. Open ［Services］ and confirm that the Runetale Daemon service is running.
    Screen for checking the Runetale Daemon service status in the ［Services］ window
    If it is not running, try the following:
    • If ［Startup type］ is set to "Manual," change it to "Automatic" or "Automatic (Delayed Start)," and then restart the server.
    • When attempting to start the service, confirm whether it starts successfully.
    • Start PowerShell as an administrator, run the command shown under ［General］－［Path to executable］, and confirm whether it starts successfully.
  2. Confirm that the Runetale client is running and that you are signed in.
    Also confirm that the IP address information and the signed-in account are as expected.
    Screen for checking the sign-in status and IP address in the Runetale client
  3. Run ipconfig /all in PowerShell and confirm that an IP address has been assigned correctly to the Runetale adapter.
    Screen for checking the IP address assigned to the Runetale adapter

  4. Start PowerShell as an administrator and run the following commands.
    Confirm that the response includes the intended destination devices and resources.
    For details about the commands, see the following article.
    [Mesh Network] Runetale Agent Command Reference

    >cd 'C:\Program Files\runetale\'
>.\runetale.exe status

If the issue persists after completing the above steps

Restart the Target device or resource and check its operation.
If it does not operate as expected after restarting, please contact us.
[Mesh Network] Information to Provide When Contacting Us

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.