View connection server dedicated for communication with the Security Server. ![]() View connection server dedicated for access from the inside. (a pretty picture of this can be seen in Part 2) Network LegĪll users connecting to our View environment. My network design was a fairly straightforward, 4 legged topology. Sometimes this is not always practical, but in this case, I found that I only had to make a few adjustments before things were working perfectly with all of the components. Since all of the supporting components of VMware View will need to communicate across network segments anyway, I suggest making accommodations in your firewall before you start building the View components. While the screen captures are directly from TMG, much of the information here would apply to other security solutions. For me, access to these segments are managed by a Celestix MSA 5200i, 6 port Firewall running Microsoft ForeFront Threat Management Gateway (TMG) 2010. This post is simply going to focus on the security rules to do such a thing. We are almost at the point of installing and configuring the VMware View components, but before that is addressed, the most prudent step is to ensure that the right type of traffic can communicate across the different isolated network segments. ![]() Part 2, I left off with how VMware View was going to be constructed in my environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |