Re: IIS6 + NLB - the network location cannot be reached



why not just use host header ?
you may have all website just under one ip (let's two, all under the nlb, and some on the server's own ip)

SSL can be also done with host header through a VBscript

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"fabio" <fabio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4F53C0B7-6189-4CFC-981C-0A89E1B8FB51@xxxxxxxxxxxxxxxx
hi experts,
my problem is quite strange&hard to solve for me, maybe one of you could
help me.
my configuration:
2 machines 10.1.1.15 and 10.1.1.16
each machine has 5 aliases .30 .31 .40 .41 .100
addresses .30 31 40 41 are used for a web site each, the .100 is used for a
cluster in network load balancing (nlb)
this configuration works well using httpcfg.exe by microsoft to do not
permit to the iis service to bind on all ip addresses.
but...
i must add 1 new website and my boss does not want it in cluster, just
standalone (wtf, damn' boss!)
so...
i have added one more ip address to the machine 10.1.1.16 (new address is
.23) and associated the new website to the ip address.
when i click on "start" to start my new website on IIS6, it says:
"the network location cannot be reached. for information about bla bla
bla...."
i post below some more informations
systems are win 2003
C:\Program Files\Support Tools>httpcfg query iplisten
IP : 10.1.1.30
------------------------------------------------------------
IP : 10.1.1.31
------------------------------------------------------------
IP : 10.1.1.40
------------------------------------------------------------
IP : 10.1.1.41
------------------------------------------------------------
IP : 10.1.1.16
------------------------------------------------------------
IP : 10.1.1.23
------------------------------------------------------------

if i bind my website to the .16 address but in a port *different* than 80,
it works!....
please help me
regards, fabio

.



Relevant Pages

  • 85010014 error - Exchange ActiveSync - Resolved
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.exchange.connectivity)
  • 85010014 error - resolved - ActiveSync Exchange Server
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.pocketpc.activesync)
  • Re: 85010014 error - resolved - ActiveSync Exchange Server
    ... Application Log on our server would be filled with those ActiveSync 3005: ... It basically all comes down to the basics of Windows DNS, how SSL ... and our Default Website could only properly respond to ONE IP ... SSL host header using port 443 with our SSL cert. ...
    (microsoft.public.pocketpc.activesync)
  • Re: IIS5.0 Argh
    ... create a brand new website with the root pointed at ... Change this website to have a host header of www.sprinklermonkey.com ... So requests containing the Host header www.sprinklermonkey.com will see ... Web Site directory. ...
    (microsoft.public.inetserver.iis)
  • Re: Windows 2003 IIS Possible bug - please verify
    ... Why do you think this is a bug in IIS6? ... Host header wasn't even specified so that the lookup can be attempted. ... You stop the catch-all website and then try to browse to a HTML without ... Using the IIS snap-in and stop the first web site. ...
    (microsoft.public.windows.server.general)