Looks like an issue in your firewall settings.
Does IIS have any logs that show how the requests are being routed and any errors that it encounters when trying to pass the request to the runtime?
Thats a hard question to answer remotely ;-).
Changing the trigger port to 80 is no problem, as long as xas/* requests are still forwarded to your 8082 port. That should be achieved using rewrite rules in IIS.
I still think I am doing "stuff" wrong when deploying, but I now am at least gettin my application visible online in our "own" cloud.
Points of notice:
I cant answer myself here can I ? Ahh I guess I can 9-)
Right an update on the issues after a very helpfull session with Mendix
integrated security op een 64-bits server, maar ik meen me te herinneren dat het te maken heeft met welke dll je moet gebruiken. Deze site zegt daar iets meer over: http://msdn.microsoft.com/en-us/library/ms378428(SQL.90).aspx.
Ik denk dat het vooral om deze “note” gaat: If you are running a 32-bit Java Virtual Machine (JVM), use the sqljdbcauth.dll file in the x86 folder, even if the operating system is the x64 version. If you are running a 64-bit JVM on a x64 processor, use the sqljdbcauth.dll file in the x64 folder. If you are running a 64-bit JVM on a IA-64 processor, use the sqljdbc_auth.dll file in the IA64 folder.