We help IT Professionals succeed at work.

IIS bindings issue

Neal58
Neal58 used Ask the Experts™
on
Hi, hopefully a quick and easy one! system crash has caused our IIS to be a little bit iffy. Now if "Default Web Site" is started, "SBS Web Applications" isnt able to start with the error:
 
This Web Site cannot be started. Another Web site may be using the same port.

default and sbs web apps are using the same ports, but if i change the port or stop the default web site then all the outlook clients flare up with password requests and can't reconnect to exchange, but without sbs web app's there is no activesync / remote access!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
Create a Host header for other SBS Web Applications so can have same both sites on port 80

Author

Commented:
sbs web apps has a host name on port 80 for remote.servername.com, it doesnt let me add one for https 443.

default web site has no headers at all on either 80 and 443, what do you suggest the best headers for these would be?

Commented:
Are you accessing app on port 443 as you have headers  for port 80

Author

Commented:
owa and all run on https 443

Commented:
Do you have proper certificate on SBS Web Apps site

Author

Commented:
yup, certificate showing for remote.domain.com

Commented:
You can stop default web site and then add headers for port 443 on SBS Web Apps site and then start deafult web site.

Author

Commented:
It still wont let me add a host name on 443 for sbs web app.

if i try and remove https 443 out of default web site, it is coming up with a warning saying the certificate is assigned to another sites binding, deleting htis will cause the https binding of the other site to become unusable.

this same warning comes up if i try and change default web site 443 to another port

Commented:
ok Is your application working  fine on port 80
Commented:
Not quite sure what version you are running of SBS, but it seems to be either SBS 2008 or 2011. If that is the case it would be my strong recommendation to run the 'Fix my Network Wizard' in the SBS console. All versions of SBS rely on the wizards to function correctly. SBS is doing a lot in the backend that you never see-and because of this, when trying to set it up as normal server, you will run into problems.

The issue above seems to be one of those issues. When you attempt to start doing manual binding and the changing of ports you will in essence break SBS. Because there is a wizard that will most likely do what your trying to do-it's most likely not the best practice way of doing it.

If you could confirm what version of SBS we will be able to assist you better.

-Jared

Author

Commented:
ash007 - which application do you mean? owa, activesync etc all need 443 to work.

jaredr80 - sorry, should have said in first post, sbs2008. running fix my network, found a pile of probs with itself have told to fix. Still no change for the port numbers

Author

Commented:
changed port on default web site https, recreated certificate, so far so good