Internet Explorer in refresh loop, looking at 2X Web Portal

Hi all, I'm wondering if there is a fix for this:

My 2X environment is working great, internally and across the Internet via the Web Portal. Because I do not have a static IP at my house, I redirect a subdomain of one of my domain names, back to the dynamic DNS address at my house (rather than doing a true DNS forward, since I cant do it by IP address). This works great, so my users can just go to http://2X.domainame.com rather than http://very.long.dynamicdns.name.com:81, and also allows me to mask that long dynamic DNS name.

All works well when going to 2x.domainname.com in Firefox and Chrome, but in Internet Explorer 8, it gets stuck in a loop, where it flashes the 2X Web Portal page for about 1/2 a second. My suspicion is it has something to do with the way Internet Explorer is checking for the 2X Client software, and also that the actual domain name it is being sent to is being forwarded, so it's probably some goofy security provision.

When I point Internet Explorer to the actual http://longdynamic.dns.name.com site, it works just fine.

Anyone else encountered this, and found a way around this?

 

what version are you using ?

 

2X Access Portal

Module Version
2XWebPortal 7.3.753.0
2XWebService 7.3.753.0
2XAppList 7.3.753.0

 

do you manage to log to the access portal or the problem happens when the logon page is being shown.
BTW there is a new beta version 8.0, might be worthed to give it a try.

 

I will try the beta version to see what happens there. The issue only presents itself when accessing the Web Portal from the domain via a subdomain redirect. When I access the actual site directly, it doesn't happen in any browser.

 

Can you elaborate a little bit more on "subdomain redirect". How is everything set up?

 

Sure. Here's my setup, let me know if this makes sense:

I have a typical DSL line with DHCP, so I use a free Dynamic DNS service. The provided DNS name is rather lengthy and not a professional looking address, for our sake lets call it http://dynamic.dns.com. Therefore to connect to my 2X Web Portal, I go to http://dynamic.dns.com:81

I own a domain through Go Daddy, and within the settings there, you can redirect subdomains anywhere you want, and also mask the destination, so the viewer 'thinks" they're still on that domain. Lets say for example it's mydomain.com, so I have the subdomain "2x" forwarded to "http://dynamic.dns.com:81".

The net result is, if I go to http://2x.mydomain.com I hit my 2X Web Portal. All is well in Chrome and Firefox, but IE 6, 7, and 8 will all just "loop", flashing the 2X logon screen for about 1/2 a second. I've found if I manually go in and add the dynamic.dns.com address as a trusted site, everything works normally.

Based on this, it seems the issue is that IE has an issue with the way I am masking the domain (understandably so; I'd like to know if I go to a site but I am secretly redirected somewhere else!). But, I'm wondering if there is a way to correct this server-side, so users do not have to deal with anomalies like this?

 

I am having similar issues.. Any update to this problem or any other suggestions?

Let me know, I'd really appreciate it.

Thanks in advance,
-Jim

 

Hi Jim,
Since then I ordered a block of static IP's and am using my registered domains with real SSL certs, so for my purposes I am no longer encountering that issue. This issue is actually not a 2X issue per se, it is an IE security issue. It is preventing you from potentially encountering a site you did not intend to visit, when you are redirected to a site other than the one you entered. There may be a way to put IE in a more "relaxed" security mode to circumvent this issue, but that would be a per-workstation fix, as opposed to a server-side fix, which is never good.

I think I would have to say that if you are hosting serious enough applications to need this fixed, you may have to go the route I did with ordering a static IP from your ISP, and also a cheapy $29.99/year GoDaddy SSL certificate, so your application presentation is more professional. Just my two cents, I hope this makes sense. If you have other solutions or suggestions, I am all ears!

 

Please check the latest version