Plant SCADA 2020R2 - client cannot establish comms to server

i am close to the end of a Citect 2018 to Plant SCADA 2020r2 upgrade. all clients have been upgraded to 2020R2 update 31 and primary server the same . secondary server still on 2018 update 37 and on duty for last few weeks and all clients running without issue.

yesterday i shutdown the secondary 2018 server placing the 2020 Primary on duty and system was fine except for 1 Client machine which cannot establish coms to the primary? both are 2020r2 ? when the secondary was duty server (2018) it was ok. i get the following error

what do i look for. i checked configurator and all seems fine, it only failed comms since the duty server changed to 2020R2 ? and only on 1 client all 7  others are fine?

Parents
  • Looks like the hostnames are used in the project configuration instead of IPs. 2020R2 starts supporting IPv6 and introduces two new parameters

    Check these parameter setting on the client's citect.ini. The symptom appears that this client talking to 2018 server uses IPv4 and fails to talk to 2020R2 in IPv4. 

    You could do

    • Launch cmd on this client machine
    • Ping 2020R2 server machine name (FB4CE148CKCF?)
    • Confirm if IPv4 or IPv6 address is returned (then set those two parameters accordingly)

    Maybe consider disabling IPv6 in the system. 

Reply
  • Looks like the hostnames are used in the project configuration instead of IPs. 2020R2 starts supporting IPv6 and introduces two new parameters

    Check these parameter setting on the client's citect.ini. The symptom appears that this client talking to 2018 server uses IPv4 and fails to talk to 2020R2 in IPv4. 

    You could do

    • Launch cmd on this client machine
    • Ping 2020R2 server machine name (FB4CE148CKCF?)
    • Confirm if IPv4 or IPv6 address is returned (then set those two parameters accordingly)

    Maybe consider disabling IPv6 in the system. 

Children