Forwarding hostname
am 21.08.2007 23:34:02 von Jl_G_0
Hey all, got a problem, hope there's some way to find out a solution
here.
I have a site configured at IIS at port 8089. It used to be a site
accessible via other server hostname but now it need to be at this
server instead.
I need a way to users access it via the old hostname, not
'sxserver400:8089', but 'sxweb' (the old hostname of a win2000
server).
I cant change the hostname of this server, and cannot use the
Default Web Site, so it gets harder...
It would be easy if I could add to the DNS too, but I dont have
access to it at my coporative network, so I need a workaround.
Anyone knows any service or something like that to make the new
server answer (and forward) to the old hostname ?
Running W2003 Server, with IIS6.
Thx.
Re: Forwarding hostname
am 22.08.2007 08:29:59 von David Wang
On Aug 21, 2:34 pm, Jl_G_0 wrote:
> Hey all, got a problem, hope there's some way to find out a solution
> here.
> I have a site configured at IIS at port 8089. It used to be a site
> accessible via other server hostname but now it need to be at this
> server instead.
> I need a way to users access it via the old hostname, not
> 'sxserver400:8089', but 'sxweb' (the old hostname of a win2000
> server).
> I cant change the hostname of this server, and cannot use the
> Default Web Site, so it gets harder...
> It would be easy if I could add to the DNS too, but I dont have
> access to it at my coporative network, so I need a workaround.
> Anyone knows any service or something like that to make the new
> server answer (and forward) to the old hostname ?
> Running W2003 Server, with IIS6.
>
> Thx.
If you cannot change DNS, or the old Win2000 server, or any proxy
servers used by your users, then what you want to do is impossible.
The "service" you are asking for can either be DNS, the old Win2000
server, or a proxy server used by all the users.
Usually in the corporate environment you only have control of the old
Win2000 server or new Windows 2003 server, so you're going to need to
configure the Win2000 server. Either configure it to redirect, at
which point users will see sxserver400:8089, or you need to install a
reverse proxy on Win2000 so that people *think* they are going to
sxweb when in fact it is proxied to sxserver400:8089. However, such
reverse proxy is pretty bad on performance and kills authentication
and SSL security, so the choice is up to you.
Personally, I think you should just redirect people to a new server
and forget about sxweb. In general, it is pretty much impossible to
have multiple users with different access rights partitioning a single
URL namespace on a logical hostname.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//