Unable to connect with remote operator

[Paul Augood]

I am having occasional problems connecting with Remote Operator. 

What is going on when I get the error "No connection could be made because the target machine actively refused it xxx.xxx.xxx.xxx:20256 (where that IP would be in the xxx.xxx....)? 

Typically our units are still sending out emails when this occurs but we cant connect.  This has been resolved but simply unplugging and plugging the ethernet cable back in but our systems are quite remote and unmanned.

Could this physical action be reproduced through programming - re-initializing the ethernet port periodically or some other action?

 

[Saragani]

Are you connecting to the same port that is being used for sending the email? If not, what's the relation to sending email?

Is Closing Remote Operator and Starting it again solves the problem?

 

[Paul Augood]

Email goes out on a different port - different socket set up in the PLC. I mention it because it kept working (email could go out) but remote operator was giving the message I previously noted. I've had that message before when someone else has been connected but in this situation it continued indefinitely and was only fixed by unplugging and plugging in the ethernet cable.  previously.

Socket 0 TCP master (port 20258) for SMTP (email)
Socket 1 TCP RAW slave (port 80) for web server
Socket 2 TCP slave (port 20256) for programming
Socket 3 UDP RAW slave (port 20000) for DNS resolver
Socket 4 TCP slave (port 20257) for remote access

Yes have closed and opened remote operator many time - no change in behaviour form these two PLC (same programs on 50+ others).

[Saragani]

OK, 

Please contact our support team, so they will open a ticket on this issue, so it can be addressed. As far as I understand, the issue is not Remote Operator, but the PLC, that might be too busy for receiving the connection from the PC.