SNMP (Channel 5/Local PC) Comm Errors

Forum Home Forums Communicating with Devices SNMP (Channel 5/Local PC) Comm Errors

This topic contains 4 replies, has 2 voices, and was last updated by Mikhail Mikhail 10 months, 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #3309

    yotool
    Participant

    The entire content of my Line005.log file is as follows:
    ****************************************************************************
    2018-03-18 08:40:24 Communication session with the Device 51 “Local PC”, type: KpSnmp, call number: 127.0.0.1
    Get variables of the group “Group 1”
    Error getting variables: System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
    at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
    at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, UserRegistry registry, Socket udpSocket)
    at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver, Socket udpSocket)
    at Lextm.SharpSnmpLib.Messaging.SnmpMessageExtension.GetResponse(ISnmpMessage request, Int32 timeout, IPEndPoint receiver)
    at Lextm.SharpSnmpLib.Messaging.Messenger.Get(VersionCode version, IPEndPoint endpoint, OctetString community, IList`1 variables, Int32 timeout)
    at Scada.Comm.Devices.KpSnmpLogic.Request(VarGroup varGroup)
    ****************************************************************************

    …any ideas???

    Thanks.

    #3310
    Mikhail
    Mikhail
    Moderator

    > An existing connection was forcibly closed by the remote host

    It means, that the device closes the connection.
    May be the specified Read Community (password) is incorrect. Could you check it?

    #3311
    Mikhail
    Mikhail
    Moderator

    Also check firewall settings.

    #3317

    yotool
    Participant

    Duh!!!

    I had assumed that as the SNMP portion (comm channel) of Rapid Scada was installed by default, that the “answering“-side (the Windows SNMP service itself)was already similarly both installed and configured.

    …and we all know what is generally said about assuming :>)

    Thanks once again Mikhail. Your reply immediately lead me in the right direction to solve this Communicator Module SNMP Channel Error issue.

    It turns out that I

      DID NOT

    even have the SNMP services installed and running on the Windows 10 Professional host machine which is actually running the Rapid Scada platform.

    I therefore installed this Windows Feature and then created the required public Community Name and READ_ONLY rights>READ_ONLY rights.

    ..then after restarting the Communicator Module/Service, all was “well again under the sun”.

    …greatly appreciate your help.

    #3321
    Mikhail
    Mikhail
    Moderator

    I am glad that it works now ­čÖé

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.