Quantcast
Viewing all articles
Browse latest Browse all 3822

Strange protocol direction problem

We have several TMG servers installed accross our network which are all used for simlar revers proxy solutions.

We have just installed 4 x new virtual (this is the first time we have used Virtuals) VMware servers which seem to define all the incoming traffic as an outbound protocol.

For this senario I need to reverse proxy a non-web protocol which we have done in the past. on our current working proxy setup if we run a telnet to the public facing IP it will be defined as the user defined 443 inbound protocol. However on our new proxy, the protocol gets automaticly defined as HTTPS (443 outbound). I have checked the packets using wireshark and I cant see how the packets are getting defined like this? the setup is nearly identical as the working solution yet we have the exact problem on all 4 VMs.

The VMs just have 1 hardware FW device above them and thats it. Nothing is interfering with the headers of the incoming data. Alll AV is switched off.

Has anyone else had this issue?


Viewing all articles
Browse latest Browse all 3822

Trending Articles