Szenario: for external access we are using an high port 25655 on the tmg listener, internally the server is called with 443. some pages could be displayed and some not, like this above...so i suspect this is a authentication problem ? for internal use, there seems no problem at all. Authentication on weblistener tab set to basic authentication, but for test purposes i configured it to "no authentication" without success
From: Taylorville, IL
Make it port 443 across all of it. There is no security benefit to using an odd port,...the benefit comes from the SSL process itself,...not from the port being used. Using an odd port also adds to the complexity and makes finding the true cause more difficult.