Got K2 on the case with this, but anyone else here able to offer some suggestions on how to get this working:

We want to mask the Server name off on a new server so users are unable to see it and want this to work for users who have AD accounts and authenticate via Windows, we have No need for anonymous users and need this working both internally and externally to the workplace.

Despite everything we've tried, it just doesn't work

Here's what i have:

Server name: K2Server

Runtime site in IIS set to Windows Authentication only and uses NTLM provider (as default)

Got a DNS entry called Masked.myplace.com

Added 3x Realm entries for the DNS fpr runtime, designer and viewflow in the below format:

http://Masked.myplace.com:81/Runtime etc etc

In IIS i've also added a Site Binding on the K2 site to go to http Port 81 and Hostname: Masked.myplace.com

TEST RESULTS

If i try to access INTERNALLY - using URL: https://Masked.myplace.com/Runtime/Runtime/Form/MyForm it does one of two things:

redirects and shows the following in the browser: https://K2server/Runtime/Runtime/Form/MyForm - so the server name is exposed.

OR it just sits on the login asked for the login credentials, which even when entered correctly, still stays on the login

if i try to access EXTERNALLY - using same URL: https://Masked.myplace.com/Runtime/Runtime/Form/MyForm - it just times out and says Page not found.

On our old production server all the above settings work fine as we use TMG.

Now that TMG is dropped, we are trying to get the same working on WAP without any success so far.

Any suggestions?

K2 suggested a Second Runtime site, but how will that work? I've done a Second Runtime site before for testing anonymous access, but that won't help mask the server name off will it or fix the issues with External access for AD users.

Any help deeply appreciated...