9.3.3 sec is not working due to architecture design...path difference...
if only admin user should have access, then you can try to export filters from system 9. and try to import it in 220.127.116.11 by replacing other users with admin.
Actually thats also not needed Admin user should or bound to have total access . so just copy object files and load data as a part of upgrade that should be fine.
Just create a fresh install of 18.104.22.168 and use the EAS migration wizard to migrate the apps, migrate data using export/import
Actually that probably wont work if you are nort installing EAS on 22.214.171.124, seems strange not be installing EAS with Essbase.
Yes, I believe that should work.
but is it possible to use EAS 9.3.3 to manage Standalone Essbase 126.96.36.199 applications with Native Security?
Also, from EAS Help :
Essbase Administration Servers and Essbase Servers cannot be converted back to native security mode. When a server runs in EPM System security mode, you use the SharedServices Console to perform all user management tasks.
I updated my post, I would push for EAS to be installed in 188.8.131.52 if essbase is being deployed, it is possible to go back to native security though you lose everything in the sec file because it has to be deleted.