IIS - SSL Help

Asked By Rya

29-Jul-07 04:14 PM

The IIS on my SBS2003 box currently has listed the following web sites, not
of which are public:
1. Default Web Site - TCP Port: 80 / SSL Port: 443
2. Office Terminal - TCP Port: 80 / SSL Port: blank
3. Microsoft Sharepoint Administration
4. SharePoint Central Administration
5. companyweb - TCP Port: 80 / SSL Port: 444

I need to add SSL and then a certificate for the Office Terminal so that my
office employees can send payment information to our online merchant
gateway... how do I go about doing that... the SSL part??? I've tried simply
adding the SSL port number 443, and turning off the Default Web Site, but
then I get 'page not found' when trying to navigate to a page using the https
protocal. Confused... first time doing this so please help. Thanks in advance.

30-Jul-07 01:18 PM

To add to what I already wrote...

companyweb ip = 192.168.1.1
default web site ip = (All Unassigned)
office terminal ip = 192.168.1.2

I need to set up ssl for the office terminal web site, but I keep getting
the error asking me to select an unused port. Should I just pull a number out
of thin air and use it there instead of 443 & 444, or is there something I'm
missing that will allow me to use 443 or 444.

30-Jul-07 10:29 PM

If you choose random numbers, you will likely get random results.

Please calm down and explain what you are trying to do. Especially
since this is the first time you are doing this.

If you just make random changes, then be prepared to reinstall the
SBS2003 server. It is no fun troubleshooting random configuration
changes.

To be clear, you don't need to setup SSL unless you want to encrypt
traffic from the browser client coming TO this website. You don't need
a certificate to send payment information to the online merchant
gateway unless they require client certificate authentication.

If you just turn off "Default Web Site" and add "443" to "Office
Terminal" website, how are you certain that:
1. Your request is actually routed to the correct website
2. The website actually has a page that you are navigating to? They
were different websites likely pointing at different content, so if
you are not certain what you just did, the "page not found" error is
likely to be legitimate.

The IIS log file for that website's request will tell everything --
whether your request arrived at the right website and what was the
request processing result. If you do not look at the log file, you are
simply assuming that you can guess the correct answer on the first
time.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//