Thursday, October 7, 2010

IIS7 and Multiple IP Addresses That Won't Bind

Recently one of my clients asked to put a Tomcat Server on the same box as their SharePoint 2007 WFE. 

1) Add the IP address (Local Area Connections --> Properties --> Advanced --> IP Address Add...)










2) Stop IIS  (cmd --> iisreset -stop)
3) Set binding information in Tomcat
4) Set binding information in IIS
          (IIS Manager --> Right Click Site --> Edit Bindings --> Edit Port Binding --> Select IP from drop down) 




5) By default, IIS7 binds to ALL port 80 IPs, so we have to disable this behavior for the IP in IIS 
      (cmd --> netsh http add iplisten ipaddress=xxx.xxx.xxx.xxx)


6) Restart IIS (cmd -->  iisreset)



Warning!!!
If you have created Custom Web Services, running the Net Shell command will bind your Custom Web Services to the IP address and cause them to stop working.  This will give you an error of:  Not Able To Connect To Remote Server.

3 comments:

  1. The first phase the preparation should, theoretically, be uninfluenced by the intended intensity and duration of the sound which is subsequently produced. In fact, however, so quickly are the three phases accomplished that the pianist rarely has capacity to think, in performance, of each phase separately. www.lemigliorivpn.com

    ReplyDelete
  2. I am appreciative to the essayist for composing this.
    192 168.0 1

    ReplyDelete
  3. Hello, this weekend is good for me, since this time i am reading this enormous informative article here at my home. https://192-168-i-i.com

    ReplyDelete