virtual address (url) resolution for website

[Guest]

We configured our website on IIS 5.0 with a virtual url address eportal.abc.us which is load balanced with
two servers (pdx1 and pdx2). When we enter eportal.abc.us it goes directly to http://pdx1.abc.com/irj. We want users to display only the global url on address bar (ie. eportal.abc.us). Even after entering IP/Hostname on both pdx1 & pdx2 on C:\WINNT\System32\Drivrers\etc (filename: hosts), it still goes directly to http://pdx1.abc.com/ir
Our IIS has a default.asp, which redirects the page to /ir

Any ideas? We do not want users to bookmark the page and continuously going to pdx1, as this defeats our load balancing solution. We do not want users to know which server they are logging into. Should I create another virtual website on IIS called eportal

Thanks
ajloren

 

[*Vanguard*]

"ajloren" said in

We configured our website on IIS 5.0 with a virtual url address
eportal.abc.us which is load balanced with
two servers (pdx1 and pdx2). When we enter eportal.abc.us it goes
directly to http://pdx1.abc.com/irj. We want users to display only
the global url on address bar (ie. eportal.abc.us). Even after
entering IP/Hostname on both pdx1 & pdx2 on
C:\WINNT\System32\Drivrers\etc (filename: hosts), it still goes
directly to http://pdx1.abc.com/irj Our IIS has a default.asp, which
redirects the page to /irj

Any ideas? We do not want users to bookmark the page and continuously
going to pdx1, as this defeats our load balancing solution. We do not
want users to know which server they are logging into. Should I
create another virtual website on IIS called eportal?

Thanks.
ajloren

Other than some fancier and probably better under-the-cover solution
involving configuration of your load-balanced servers, wouldn't using a
frame to display the page on the other server result in the URL in the
address bar remaining whatever was the parent's URL (i.e., it would
remain http://eportal.abc.us although the frame that takes the entire
page size goes to http://pdx1.abc.com)?

The problem I see with this solution is that the user can disable or
prompt when navigating frames across domains. You are having them first
connect to the abc.us domain and then open a frame on the abc.com
domain. I have my IE's Internet security zone configured to prompt me
for "Navigate sub-frames across domains", and I rarely allow it even if
the source and target domains are known. Is there good reason why your
load-balancing hosts aren't on the same domain as the server proffering
the home page?