Environment
Novell BorderManager 3.9 Support Pack 2
Novell BorderManager 3.9 Support Pack 2 Intern Release 1
Novell BorderManager 3.9 Support Pack 2 Intern Release 1
Situation
After configure the reverse proxy in BorderManager, internal website is accessible. But if authentication is enable on the reverse proxy, it is not possible to access the internal site. No authentication screen is displayed, only a timeout error on browser.
Resolution
Taking a lan trace, it showed that browser was getting the log in redirection correctly but when trying to establish the new connection, no answer was seen.
Customer had an additional firewall between reverse proxy and the internet and the firewall was only forwarding port 80 to the reverse proxy. Once the ssl port using for bm authentication, in this case was 446, was also open on the upper firewall, reverse proxy authentication started to work.
Customer had an additional firewall between reverse proxy and the internet and the firewall was only forwarding port 80 to the reverse proxy. Once the ssl port using for bm authentication, in this case was 446, was also open on the upper firewall, reverse proxy authentication started to work.