system
5
This brings another possible issue into the mix when doing it that way. Our remote clients often work from the local network and also work from remote locations. I believe that if I could get the client to first check for the local AMS IP, if failure, then check for public IP of AMS. If the local IP is detected as the AMS then it will display the clients local IP properly to the ADNM. If the local AMS IP is not found and has success on it’s public IP, then the clients’ public IP would be properly displayed in the ADNM. I get the feeling that this is completely possible. I’ll check and see if this can be set through the client policy options in ADNM.
While I’m checking, do you have a different suggestion or would you agree with me on the aforementioned method?