• Replies 9 replies
  • Subscribers 585 subscribers
  • Views 336 views
  • Users 0 members are here
Options
Related

Local I/O Server not starting/not able to be configured

Michael

Similar item in

"IO Server Processes Failing with Dual NIC"

but different.

Stand-Alone computer.

Citect SCADA Version 2018R2, Windows 10.

I/O, Alarm Servers configured (no trends or reports).

Dual NIC's - ond for corporate network, not involved with Citect.

(9) Comms devices over ethernet.

Project runs fine if I use 127.0.0.1 as the IP address for the server computer.

If I put the real computer addressof the NIC (192.168.1.150) in the Network Address, the I/O server is not recognized - in setup wizard.

I can ping the address just fine.  Can't see how the ports would matter if this is in the local machine.

System runs just fine if it is in single process mode and the 127.0.0.1 address is used.

Anybody with suggestions on why the 192.168.1.150 doesn't work?

Parents

  • Thanks for you sugestions.  I finally got the HOSTS file to take the edits.  Shortened the names and added to the HOSTS file.  Same results.  Pretty much at a standstill for ideas here, and I can't seem to get through to Citect Tech Support.  Falling further behind than making progress. 

Reply

  • Thanks for you sugestions.  I finally got the HOSTS file to take the edits.  Shortened the names and added to the HOSTS file.  Same results.  Pretty much at a standstill for ideas here, and I can't seem to get through to Citect Tech Support.  Falling further behind than making progress. 

Children
  • in reply to Michael

    After much trying (and a break from it, too), the next word here is that the single IP Address works fine.  Once the second address is added, most of the ports shut down.  IP Address is good, but pinging by port only shows 23, 80 and a few other miscellaneous ones opened.  The ones Citect needs to communicate are shut down.  Seems to be outside of Citect, but if someone has some network knowledge or has run into this before, I'd love to hear it.  Normally, this happens when using a managed switch and port blocking is on.  No switch in this situation.

  • in reply to Michael

    Have you tried disabling Windows firewall on this machine? I would think it has something to do with that or a switch/firewall in the field.

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.