Client Citect SCADA cannot connect to server

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

  • 1. After changing your network type, did you make sure to check again if the firewall was off for private networks?
    2. Did you disable the firewall on both machines?
    3. After changing firewall settings, have you rebooted the machine? Normally not needed, but you never know...
    3. Can you ping from both machines to each other?
    4. Are there any other firewall devices in your network (switches, routers etc.)?
    5. Do you have anti-virus or anti-malware software enabled that can block or filter network traffic?

    When you get it working eventually, please try to re-enable everything you turned off, step-by-step. Better to add the ports that need to be open to your firewall exception rules, than disabling the firewall altogether.

    Regards,
    Patrick
  • as some paranoid first steps:
    1) Confirm via studio that the ports haven't been manually set to something else.
    2) Confirm from runtime manager that the process is running.
    3) go to CMD and use Netstat to make sure that the process is listening on the port you think it is (Netstat | find "2082") or (Netstat -a -o | find "<PID of the IO server process>")
  • Hi Sir thank you for your reply
    Plz fin my answer below each question:
    1. After changing your network type, did you make sure to check again if the firewall was off for private networks?
    Yes it was Off
    2. Did you disable the firewall on both machines? yes i did
    3. After changing firewall settings, have you rebooted the machine? Normally not needed, but you never know...
    No i didnt i thought its not necessary
    3. Can you ping from both machines to each other?
    Yes i can ping both sides
    4. Are there any other firewall devices in your network (switches, routers etc.)?
    No just a regular unmanaged switch
    5. Do you have anti-virus or anti-malware software enabled that can block or filter network traffic?
    yes i have anti-virus Trend Micro Security but it was Off.
    There is no way to try to know wich application is blocking those ports?
    By the way im using windows 10

    When you get it working eventually, please try to re-enable everything you turned off, step-by-step. Better to add the ports that need to be open to your firewall exception rules, than disabling the firewall altogether.
    yes i will do it step by step thank you for you advice

    Regards,
    Patrick
  • Hi willem thank you for your help:
    1) Confirm via studio that the ports haven't been manually set to something else. yes in the configuration the port fields is left blank so its the default ports
    2) Confirm from runtime manager that the process is running. yes everything is running
    3) go to CMD and use Netstat to make sure that the process is listening on the port you think it is (Netstat | find "2082") or (Netstat -a -o | find "<PID of the IO server process>") yes i did it normaly listening
  • Hi every one
    I used the application portlistener to simulate the port 2082 and the command telnet 192.168.10.112 worked well so the firewall does not block the port.
    Maybe im missing somthing in the Citect SCADA server configuration.
    I configured the server to run on Network configuration. thats the only parametre on the server that i changed to run Client-server architecture.
    Is there anything that im missing out?
  • 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.
  • Hi Mr Patrick
    Thank you again

    the project configuration is very simple
    I have a USB key License with CITECT SCADA View Only CT103099 and I want to connect it to a server equipped with another USB key with License CT101113 1500 Pts Full server .

    Server IP adresse: 192.168.10.112
    Client View Only IP adresse: 192.168.10.113
    Both PCs are equiped with windows 10 and connected via a simple switch and configured "Networked"

    In the client side i made the changes in the Citect.ini
    [Client]ComputerRole=2
    [Client]ReadOnly=1
    [Client]FullLicense=0

    I specified in the client the adresse Network of the server: 192.168.10.112 for the IO Server, alarm server...
  • Hello AO

    Maybe in the Setup wizard you have a configure Server password or try to use that to create a trusted network between the machines.

    Regards
  • Hi Sir
    Yes i configured a Server Password on the server and on the Client
  • Click Start / RUN / type in Configurator (Also available from Start Programs as selectable) Once here if you are running 2018R2 you may have the new security features on be default, so you will want to make sure you have set this up on Both the Sever and Client to ensure you have the same Trusted network and TLS1.2 encryption setup properly between the nodes. Make sure you don't have any configuration errors showing in this Configurator utility.