Cannot Access Webapp behind TMG

[rpgowned]

I am not too versed with Apache at all so bear with my question if it is easy..

We have a webapp "OTRS" which is a help desk ticket system that uses apache on a windows server 2008 box

our network is behind a Microsoft Threat Management Gateway (TMG)(basically the newish ISA server)running on the following 10.1.2.10:8080 internally

I can access the webapp internally on the network via servername or internal ip address just fine

if i attempt to access the site via external ip(209.175.158.152) or domain name hd.ocusd.net it does not work i receive the error below back on the TMG.. I also cannot ping the external ip or dn (request timeout)..

Log type: Web Proxy (Forward)
Status: 10050 A socket operation encountered a dead network.
Request: GET hd.ocusd.net/

It is a vanilla 2.2 install as far as i know.. (I am not sure it came with the OTRS package) I have not set up any reverse proxies or anything like that and i wouldnt know where to start to do that if that is what I need to do..

I have set up other sites on IIS and they work fine so I am pretty sure there must be something in apache i need to do to get it to work

If anyone at all can help or has any advice i would greatly appreciate it

 

[RhythmAce]

I know nothing about Windows stuff. In my opinion they should get out of the server business. That being said, apache uses the Listen directive to bind it to a particular address or port. By defaul it is all addresses on port 80 (Listen *:80). If you are using name based addressing, you should have the NameVirtualHost directive uncommented and changed to the port you want to use (NameVirtualHost *.8080). The iport should also be in the vhost directive. For example: <VirtualHost *:8080>. Other than that, I would suspect that TMG is messing up the header but since IIS gets the request with no problem, that is more than likely not the case.

 

[itsp1965]

Are u attempting to access the public IP from your internal network or you having the problem from outside as well? If it is internal it probably has nothing to do with the proxy itself but how routing is setup on your internal network