1) More NAT capabilities. I want to be able to configure NAT translations just like Checkpoint.
2) Better Publishing functions. I want to be able to publish a HTTPS server and access that publishing rule from internal clients too. As for today it is not possible for HTTPS. I assume it has something to do with my first wish..
I have a very complicated environment behind the ISA. I don't think there are many environments like this one arround. Think about an ISP environment where ISA is the main firewall which all clients go through to the Internet. Clients are companys networks. Each client has its own Active Directory, with Exchange and other servers. The ISA publishes many Exchange servers for different AD Forests, Each has it's own IP ranges, own ISA network and no one has access to each other. All the networks have NAT relationship with the Internet (By ISA) and no relationship with each other. With DNS, I can solve for each client the access for its own servers. BUT: What happens if one of the clients is physicaly visiting a collegue who happens to be another client behind the same ISA, and the first client wants to access his OWA. Here I have a problem which has only one solution as for now: Make relationship between the two networks...(Which I can't because of contract limits). The only solutions I think of is using the same Publish rule that I use for the internet, and access the OWA by its external IP. But what do you now.... HTTPS don't work.... (every other protocol works by the way) Any idea ?