How do I prevent IIS from binding to a second IP address on my server?
March 20, 2008 8:42 AM Subscribe
Running IIS, I have multiple IP's assigned to the server. I need to stop IIS from binding to all of them. Any suggestions?
It's a Windows Small Business Server and I'd really like to be able to host a third party FTP and web app on it. The trouble is that IIS seems to be taking all of the IP addresses assigned to the server, even when the IP addresses are specifically bound to specific sites.
Some detail:
- The server is hosting the standard "default web site" on which just about every web-enabled SBS service is dependent, and it is also hosting the public facing website, using a host header. No problem there.
- The server also hosts an IIS-based FTP service that I am replacing with an FTP server that has an HTML-enabled front end.
- The new FTP application needs an IP with ports 80, 443, and 21 available to it.
I have assigned two IP addresses to the server on the private LAN, one is its primary IP. That primary IP has been set, in all IIS services, as the specific IP for all sites in IIS (I changed all of them from "all unassigned" to the specific IP). The default site is working fine.
I'd like to keep the other IP completely out of IIS' reach, unfortunately it not cooperating - any attempt to start the third party software dies with "the port is in use by some other server". Stopping IIS corrects the issue, therefore I am inclined to believe IIS is the culprit.
Thanks in advance for any suggestions you may have.
It's a Windows Small Business Server and I'd really like to be able to host a third party FTP and web app on it. The trouble is that IIS seems to be taking all of the IP addresses assigned to the server, even when the IP addresses are specifically bound to specific sites.
Some detail:
- The server is hosting the standard "default web site" on which just about every web-enabled SBS service is dependent, and it is also hosting the public facing website, using a host header. No problem there.
- The server also hosts an IIS-based FTP service that I am replacing with an FTP server that has an HTML-enabled front end.
- The new FTP application needs an IP with ports 80, 443, and 21 available to it.
I have assigned two IP addresses to the server on the private LAN, one is its primary IP. That primary IP has been set, in all IIS services, as the specific IP for all sites in IIS (I changed all of them from "all unassigned" to the specific IP). The default site is working fine.
I'd like to keep the other IP completely out of IIS' reach, unfortunately it not cooperating - any attempt to start the third party software dies with "the port is in use by some other server". Stopping IIS corrects the issue, therefore I am inclined to believe IIS is the culprit.
Thanks in advance for any suggestions you may have.
Best answer: See this article, it sounds like what you need. (First Google result for "stop iis binding to ip address", by the way.)
posted by kindall at 8:47 AM on March 20, 2008
posted by kindall at 8:47 AM on March 20, 2008
Response by poster: Really? REALLY? That simple. Worked the first time, kindall, thank you.
I am at a client site where it is perfectly acceptable to sit at a keyboard and type questions into Metafilter, but the boss here believes that googling is a waste of time.
Ah, customers.
posted by disclaimer at 9:28 AM on March 20, 2008
I am at a client site where it is perfectly acceptable to sit at a keyboard and type questions into Metafilter, but the boss here believes that googling is a waste of time.
Ah, customers.
posted by disclaimer at 9:28 AM on March 20, 2008
« Older Is there any good info in Publishers Weekly? | What should I do in southern Vermont? Newer »
This thread is closed to new comments.
posted by stovenator at 8:46 AM on March 20, 2008