Remote Communicator Error

Forum Home › Forums › Runtime Bugs › Communicator Bugs › Remote Communicator Error

Tagged: , ,

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • January 25, 2023 at 6:26 pm #12016
    TroyV23
    Participant

    I setup a test RapidScada environment on one machine to make sure my modbus configuration was correct, and everything worked perfectly. Now I am trying to separate the Server from communicator, and run them on 2 different computers.

    Computer 1: RapidScada Server, Webstation,
    Computer 2: Communicator

    When I run communicator on Computer 2, I get an error: saying no endpoint listening at 192.XXX.XXX.XXX:100000/ScadaAgent/ScadaAgentSvc/

    There is a firewall between the machines, and have opened ports 10000 and 100002.

    I have confirmed Agent running on both machines.

    Does this arrangement require the RapidGate module? (I don’t have it installed)

    January 25, 2023 at 8:02 pm #12017
    manjey73
    Participant

    Not required. You have a PC with a Communicator should be in a separate instance, in which the server address should be specified in the Communicator settings – the 1st PC

    January 26, 2023 at 11:19 am #12019
    Mikhail
    Moderator

    In what moment did you get that error?
    You should install Agent on computer 2 to be able to upload configuration to it using the Administrator app.

    January 26, 2023 at 6:07 pm #12023
    TroyV23
    Participant

    I have Agent installed in both places and it is confirmed to be running in task manager. Is there any other configuration I may be missing? The error appears as soon as I try and upload configuration. It is never able to run communicator.

    Not required. You have a PC with a Communicator should be in a separate instance, in which the server address should be specified in the Communicator settings – the 1st PC

    I have defined the server address in Communicator, does the server need to know the address of the communicator as well?

    • This reply was modified 2 years, 10 months ago by TroyV23.
    January 27, 2023 at 8:41 am #12032
    Mikhail
    Moderator

    does the server need to know the address of the communicator as well?

    No.
    Make sure that you try to upload configuration to the proper instance.
    Also try to connect to the remote Agent by a utility, like telnet using IP and port 10002.
    Check the Agent connection in the instance profile. Port should be 10002.

    March 28, 2023 at 6:48 pm #12299
    TroyV23
    Participant

    Thank you, it turned out to be a firewall issue between 2 networks.

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.