Dear All,
I have already seen several cases, but looks like I did not get through the resolution of my problem.
I have two Sharepoint 2010 applications under internal sharepoint machine called internal.local. On the machine I have 2 separate web Apps, one on standard http port 80, one on port 8080.
There is a TMG which is used to present to the outside world the applications.It has also another function, to enable Form Based Authentication which was not originally configured on Sharepoint 2010. As you may understand, for us it is crucial to use TMG to avoid risks on the application side. And I cannot simply byPass TMG since it has a real function in my environment.
For the application on port 80 there is no problem, it shows the form with login and password and it goes straight to the web application. From internal network everything is fine as well, from TMG I can see all the applications (both on port 80 and 8080, from the TMG server as well).
The second application (the one on port 8080) was added few weeks ago and there my problems started. I tried creating a new rule, a new listener, and using the bridging to diverge every call on port http://www.mywebsite.com:8080 to http://internal.local:8080. What I get from external is that the resource is not reachable. Strange, I understood that the reason why bridging is there is when I want to diverge http to https, or, like in my case, when I want to reach a destination on port 8080 on the other side (or any other port would be of interest).
I understood from other posts that in principle TMG may not be not capable do to this operation. Am I right? Am I trying to do something which is impossible by design?
In order to make it more "complex" I created also a new protocol (http_over_8080) which is used in order to enable web proxy. So I had a web service configured with the new protocol, the new listener on port 8080, the bridge enabled, and all from/to rules settled properly.
Again... Resource is unreachable..... Damn....
Checking looks like the listener is not capable to intercept the port: how is it possible? In principle the listener is the same with the exception of the incoming port which is 8080 instead of 80.... Here I had a doubt: is it possible IPV6 is creating any issue? Believe or not, if I try the bridge to port 8080 from the rule set on port 80, you will reach the right server.
Am I missing something? as told, the rule on port 80 works perfectly, but this new service is driving me crazy. Do you have any idea what I may have done wrongly? Any paper/case study/document to read?
I was oping that TMG was a bit easier with Microsoft Application Servers as MOSS is, but I start to have doubts. Today I started to look for something else, I like the products, but if I need to invest hours in trying configuration which will not work "by-design" this will be a bit frustrating. Unfortunately we face with similar cases many days a week.
Happy to receive any suggestion or any additional input, and happy to try once again to re-do the config from scratch if somebody can suggest a methodology of few steps which may solve my issue.
Thank you everybody in advance.
Stefano