How does AppGate handle the ambiguity of a client signing in from a foreign network that uses the same private ip range and network mask as that of the network from which the AppGate server is serving apps, shares, email, etc? Say a client is at an internet cafe and from DHCP gets an ip address of 192.168.1.2 with a network of 192.168.1.0/24 and logs into an AppGate that has a file sharing function from a server where the internal ip address of the server is 192.168.1.2 and a network of 192.168.1.0/24.
If you're running in port forwarding mode (i.e. the IP tunnel driver isn't installed/used - probably the case in an internet cafe) you'll have no issues since the system works like a proxy in this case. All requests are redirected to localhost where the system intercepts them.
If you're running in IP tunnel mode you may have problems from this but only if you have direct clashes between internal servers and servers you need to access on the "cafe" network (as in your example above). The work-around in that particular scenario would be to renew your lease in order to get another IP on the "cafe" network. With a bit of tweaking you should be able to get 192.168.1.3 for example and then accessing 192.168.1.2 won't be a problem.