You need to create an alternate access mapping in SharePoint (so that it responds on the alternate name) I would also consider port translation at your border device (ISA Server or whatever) so that externally users can access port 443, and it is mapped to port 8043 on your internal machine.
Cheers Ken From: [email protected] [mailto:[email protected]] Sent: Saturday, 11 September 2010 4:03 AM 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 ~ 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 [email protected] with the body: unsubscribe ntsysadmin
