MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS 2007 and IP binding

  Asked By: Aiesha    Date: Aug 19    Category: MOSS    Views: 947

I'm having a heck of a time trying to get IP binding to work in my new MOSS
environment. Does anyone know if this is a supported method (thinking back
to pre SP2 for v2) or are we stuck with using host headers?

Right now, whenever I add a new IP to the stack and apply it to any of the
IIS sites, it totally hoses access to all IIS sites. I've had to start from
scratch once already, thinking that it was something I had setup incorrectly
but this happened again and I am much more confident that I set it up as it
should be.

Anyone else experiencing similar activity?



3 Answers Found

Answer #1    Answered By: Lesley Tate     Answered On: Aug 19

I believe the only real issue with using IPs as the way to differentiate
websites (IP binding) is that SharePoint Central admin automatically creates the
Web Application to use all IPs on a box. To do IP binding you would always have
to create the base website first in IIS manager, then create your Web
Application using the existing website. If you ever create a Web Application
after this using Central Admin directly you will break the whole thing.

Answer #2    Answered By: Vinay Thakur     Answered On: Aug 19

I was assigning the IP address after the site (Web
appplication) was provisioned.

Answer #3    Answered By: Lynn Mann     Answered On: Aug 19

I use SSL on all of my sites and had to figure this out as well. What
you need to do is:

- Add IPs to server.
- Create the Web app via the CA using Host headers that match your URL
and leave the default port.
- Restart IIS on WFEs
- Bind IP on WFEs via command prompt using adsutil specifying the port
you want to use
- Check setup in IIS manager.

Didn't find what you were looking for? Find more on MOSS 2007 and IP binding Or get search suggestion and latest updates.