Routing

From: SLE (info_at_NOSPAM.dataworx.be)
Date: 01/12/05 

Date: Wed, 12 Jan 2005 07:42:52 +0100

Hi there,

Incoming traffic on port 80 is being routed to our Windows 2003 box running
IIS. This works fine for our primary domain which is configured in the
"Default Web Site" space listening on port 80. However, we have registered 2
different domains and I wonder whether it's possible to configure IIS to
have domain x.com routed to the first IIS site and have domain y.com traffic
to another IIS site (which will be listening on a non-80 port I suppose).

Can this be achieved transparently by configuring IIS only? Or do we need 2
IIS boxes?

FYI: our external router/firewall is not capable of filtering HTTP headers
[I think]

Thanks, 

--
SLE

Relevant Pages

  • Re: Remote Desktop web connection does not work outside my local N
    ... The web based method, using IIS, still requires you to port forward the RDP protocol to each PC ... > screen opens with the external ip of my router on the title. ... But I cant connect to any other machine on my network even ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Win2003 Upgrade Broke SSL?
    ... there WAS a single process using port 443. ... management software was starting before the IIS would start, ... > The reason I say that the upgrade did not break SSL is because IIS has no ... > anything to do with IIS nor general upgrading process of the OS, ...
    (microsoft.public.inetserver.iis)
  • Re: Save As saves link to WMV instead of video file
    ... for IIS HTTP to WMS HTTP on the same IP address. ... Both services cannot share the same port and IP address ... or to every playlist (WMS) for that to work - a world of pain. ...
    (microsoft.public.windowsmedia.server)
  • Re: Win2003 Upgrade Broke SSL?
    ... The reason I say that the upgrade did not break SSL is because IIS has no ... problems relating to port 443 being occupied suggests that you did something ...
    (microsoft.public.inetserver.iis)
  • Re: The process cannot access the file...
    ... listener on port 80 on an IP that was not bound to IIS. ... IIS 6.0 could not start ANY of the web sites and gave the 'cannot ... > bind to only one particular IP instead of binding to 0.0.0.0:80. ...
    (microsoft.public.inetserver.iis)