We use VMware SRM to replicate VMs to a second site. With a TMG Server at either end of the VPN. SRM management traffic uses HTTP port 80.
I have unstable communication between SRM servers because of TMG web proxy filter. Disabling the proxy filter for HTTP object in TMG and works no problems.
But rather than disable web proxy for HTTP across the board I created a user-defined object copying HTTP (port 80 outbound etc) but bypassing web proxy filter, and using this in the particular rule for the SRM traffic.
Now SRM comms simply do not work at all with the user-defined HTTP object (HTTP 500 error). But as I say work fine with the pre-defined HTTP object and web proxy disabled.
I can however, get the user-defined object working by using the associate standard protocol dropdown and selecting HTTP in there but then this requires the pre-defined object to have web proxy disabled as well! Defeating the purpose!
I do have another application which I am using a user-defined HTTP object bypassing the proxy successfully but SRM is refusing to work with it.
Has anyone else encountered issues with a user-defined HTTP object?? What is different between the pre-defined and just creating a user-defined object and giving it port 80 outbound etc?
I am going to gather info using Wireshark this afternoon to see exactly what is in the HTTP header but will be interested to hear others experience here.
Regards,
Steve