Solved

Second IP address is not appearing as a binding choice in IIS 7.5

Posted on 2014-10-07
8
1,298 Views
Last Modified: 2014-10-08
Hi.  Currently, we have a test site up and running.  We are looking to add a second test site to our IIS 7.5 server.  I'm using these instructions:

https://www.youtube.com/watch?v=uhWZIlgiTk4

I have added another IP address to the ethernet adapter.  Everything seems to work, I can ping it from other servers, etc... but the ip address does not appear in IIS when I go edit the bindings.  It's not showing in the drop down.

I have tried restarting the service, restarting the server.   I also tried manually adding  it in, the site doesn't load.

One thing I noticed is if I do a netstat -a , it doesn't appear that ip is listening to anything.  so I added in this line: netsh http add iplisten xx.xxx.xx.xx (new ip), but it still didn't work, and it also took down the existing test site.  So, I deleted that iplisten line.

Any ideas?
0
Comment
Question by:paradigm_IS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
8 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 40367096
Can you provide an ipconfig /all for that server.

You can also just try resetting the TCP stack
netsh int ip reset c:\resetlog.txt


Also run:
appcmd list sites  

These details will help to identify the issue and find a solution.
0
 

Author Comment

by:paradigm_IS
ID: 40367244
the ip address exists when I do an ipconfig /all.

Tried resetting the tcp stack.  readded the ip's and rebooted.  Still doesn't show up in iis.

The results of the appcmd list sites command doesn't seem to help much:

SITE "Default Web Site" (id:1,bindings:http/xx.xxx.xx.12:80:testsite1.com,net.tcp/808:*,net.pipe/*,net.msmq/localhost,msmq.formatname/localhost,https/xx.xxx.xx.12:443:,state:Started)
SITE "testsite2" (id:2,bindings:http/xx.xxx.xx.13:80:testsite2.com,state:Started)
0
 
LVL 29

Expert Comment

by:becraig
ID: 40367256
Looks like this might be an IIS bug in the UI

See a previously answered question:
http://www.experts-exchange.com/Software/Server_Software/Web_Servers/Microsoft_IIS/Q_25347559.html

Just go ahead and enter the address manually in IIS when adding the new binding.
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:paradigm_IS
ID: 40367260
Hmmm... I already tried that.  see above:  "I also tried manually adding  it in, the site doesn't load."

Does something in the host file need to be edited?
0
 
LVL 29

Expert Comment

by:becraig
ID: 40367274
No host file changes need to be made to create a mapping to to an ip in IIS (unless the DNS name you are adding is not resolvable)

Try doing this from appcmd:
Set appcmd =C:\Windows\System32\inetsrv\appcmd.exeSet SiteName=Default Web SiteSet IP=192.168.0.1:80Set FQDN=www.contos.com

%appcmd% set site “% SiteName%” /+bindings.[protocol='http',bindingInformation='%IP%:%FQDN%']

Reprinted from:
http://blog.billbrockbank.net/2010/06/21/configuring-iis-7-site-binding-with-appcmd-exe/

It seems like something about your IIS might be hosed, but this command should help.


If your problem is that the site was created and manually bound to the IP and you are unable to call it using the hostname, then try running :
ping <host-header>

If that does not resolve, then you need a host file entry or DNS entry.
0
 
LVL 29

Accepted Solution

by:
becraig earned 500 total points
ID: 40367277
Also MS has a hotfix for this behavior not sure if it is applicable for your situation:
http://support2.microsoft.com/kb/2551090
0
 
LVL 25

Expert Comment

by:Mohammed Khawaja
ID: 40367312
You do not need a second IP if you are willing to use host headers.  What this means is that instead of IIS binding to an IP, it will bind to a FQDN name.  This way you could add multiple sites by using just one IP address.  Refer to technet article below:

http://technet.microsoft.com/en-us/library/cc753195(v=ws.10).aspx
0
 

Author Closing Comment

by:paradigm_IS
ID: 40368714
becraig.  That hotfix worked.  I also had to add the site to the host file with the new ip address.  After that, it was golden.

Thanks man.
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configuring network clients can be a chore, especially if there are a large number of them or a lot of itinerant users.  DHCP dynamically manages this process, much to the relief of users and administrators alike!
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question