It looks like the network related issue. Is 192.168.1.150 a static IP address? If yes, is DNS configured? If this IP is configured with ipAddressManipulator as a virtual address, it should be bound with the DNS name from the corporate network.

Have a look at the following article and see if it would help you resolve the issue.

https://support.solarwinds.com/SuccessCenter/s/article/Edit-the-host-file-to-add-static-entry-for-hosts-that-are-not-resolving-by-DNS-EDIT?language=en_US

Using Citect SCADA Version 2018R2, Windows 10

With my dual NIC setup the server "network addresses" is the Corporate Address. 

"Computers" uses Corporate DNS name.

Unfortunately, I cannot put the corporate DNS name in Citect - it is too long and it won't compile due to dashes in hte name.

Without the DNS name and IP Address correlation, I don't think editting the hosts file will help.

This also does not work on my test setup, without the corporate network hooked up. 

"ROUTE PRINT" shows the IP address as local.

My main point of confusion is how setup wizard will not recognize it.

I can run the test setup in single process mode, but the I/O server fails.

Could you try to

• Temporarily disable the "Corporate" NIC
• In command line, ping hostname (ie, the machine name)

If 192.168.1.150 is not returned, you may have to define IP/DNS mapping in host if your project is configured to run in the encrypted mode. The certificate is bound with hostname not IP. 

OK - I'm not on the corporate network, but tried on the test bench.  Not running in encrypted mode (nor mixed).

Went through the routing table and kept removing routes (they are unused) until pinging the computer name came up with 192.168.1.150. 

Had to force the pinging to IPV4.

Tried to enter the local computer name and the IPV6 address into the Network Address in Citect, but "Network Address can be no longer than 15 characters"on compile.

Although I have the option of doing it on the test bench, I can't change the computer name on the computer in the plant (policy, not skill set).

Anyway, result is still the same.

Working on editing the Hosts file - apparently is locked down.

I recommend reaching out to AVEVA technical support to troubleshoot this issue.

It looks like the computer name length exceeds 15 characters. In general, Windows does not allow computer names (NteBIOS names) that exceed 15 characters. This rule may have changed because DNS names could have up to 63 characters.

I hope you will resolve this issue soon.

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. 

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.

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.