Not sure of your infrastructure, but you might also want to consider port forwarding from the external IP with standard SSL ( 443 ) to the internal at port 8043.
Don’t know if better than what you plan, but maybe just a different way to attack the same problem. Erik Goldoff IT Consultant Systems, Networks, & Security ' Security is an ongoing process, not a one time event ! ' From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Friday, September 10, 2010 4:03 PM To: NT System Admin Issues Subject: Sharepoint Services question I have a client with Sharepoint Services 3, running an internal site on port 8043. The site internally is name sp.domain.com which is hosted locally on their server as a cname. To access their site internally you would open http://sp.domain.com:8043 They want to make this site external. Once they install the SSL cert for the external name they want to use, is it as simple as adding it to the alternate access name list as https://sp.domain.com and making sure in IIS the host header is pointing to the IIS site that is running that site. Its not in the default web site. Thx I have done this a few times before, but all of them have been in the default web site. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
