• Replies 11 replies
  • Subscribers 585 subscribers
  • Views 591 views
  • Users 0 members are here
Options
Related

Client Citect SCADA cannot connect to server

AO

Hi all

I tried to connect Citect SCADA Client to my Server.

The client hardware alaram shows "No IO Server Could Be found" same the thing for server Alarm and Report.

i find some document that say if you get "No IO Server Could Be found"  you should open ports (2082, 2083...) in the fire wall to connect client to the server. I tried to connect to IOServer Port 2082 Via Telnet but it dosent work.

When i usethis command on the server: Telnet 127.0.0.1 2082 its fine but when i change 127.0.0.1 by The server IP adresse 192.168.10.112 on the same machine its not working. i disabled the firewall but still not working. Then i made my local network private but still not working.

Can you plz help me

Thank you all

Parents
  • I'm almost out of tips to give you without knowing your project configuration, but you could check the following things, although it will not likely be the source of your issues:

    - Complete the Computer Setup Wizard on both machines and specify "Networked" (like you described already) and make sure to use the same default server password in the wizard on both machines.
    - Try monitoring communications with WireShark on both machines.
    - Make sure to define a valid network address in Citect (netaddr.dbf). That is: a valid host name or IP adress of the server, do not use 127.0.0.1.
    - Check the Windows IP configuration (IP conflicts, subnet configuration, invalid gateway, etc.)
    - Check the windows 'hosts' file in C:\Windows\System32\drivers\etc\ for entries that may re-direct your client to an unwanted IP address.
Reply
  • I'm almost out of tips to give you without knowing your project configuration, but you could check the following things, although it will not likely be the source of your issues:

    - Complete the Computer Setup Wizard on both machines and specify "Networked" (like you described already) and make sure to use the same default server password in the wizard on both machines.
    - Try monitoring communications with WireShark on both machines.
    - Make sure to define a valid network address in Citect (netaddr.dbf). That is: a valid host name or IP adress of the server, do not use 127.0.0.1.
    - Check the Windows IP configuration (IP conflicts, subnet configuration, invalid gateway, etc.)
    - Check the windows 'hosts' file in C:\Windows\System32\drivers\etc\ for entries that may re-direct your client to an unwanted IP address.
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.