Hi,
it looks like you’re now online via INA, yes.
This can be the case, if INA as online protocol is still activated (in Automation Studio 4), and ANSL is not (longer) reachable.
For example when using ArSim, Automation Studio will try to fallback to INA if ANSL is not reachable (this is what is prevented by /INA=0, but this does not change the availability of an ANSL connection).
If you have setup ANSL TLS with a SSL configuration and tranferred this setup.to the PLC, then you have to change your Automation Studio Online setting also to this new setup.
As I remember in a SSL setup you have to:
- change the destination port number from (default) 11169 to (default) 11179
- in a column in the online settings named “SSL configuration” (or similar) you have to set the path to the SSL configuration in your project that is used with this ANSL connection.
EDIT: I just created a small HowTo about setup and online connection.
If you additionally have an user role authentication setup, the user + password dialog will pop up earliest after a SSL communication to the PLC was established.
So from issue description, I would recommend to check the online settings in Automation Studio and set them to the parameters needed for a TLS online communication, if you’ve configured this on the PLC (I think so).
Best regards!
PS, independent of your actual issue: when securing an online connection to prevent unauthorized online access, you have then also to deactivate INA in the PLCs ETH interfaces parameters.