Re: SharePoint 3.0: problems with external access

Charles,

Let's say that your Internet facing side responds to: https://remote.domain.com (in other words in order to access RWW you type https://remote.domain.com/remote)

In IIS, go to the web site that SharePoint is using and create a certificate that listens to port 8000 (as per your example). Make sure that next to SSL, it shows 8000, in the Properties section.

Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your application,type: https://remote.domain.com:8000

Open the port 8000 on the firewall and forward it to the server's internal IP.

That should do it

--
Costas


"Charles" <Charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:64EB8D07-F5FA-43C8-9BEE-DC5764A67553@xxxxxxxxxxxxxxxx
Hi all,
We have SBS 2003 standard SP2 behind a Sonicwall TZ 180.

We installed SharePoint 3.0 side-by-side with SP 2.0, no problem during
installation, we followed the MS instructions for SP 3.0 on SBS 2003.
Everything works fine internally. We like SP 3.0, which we find a great
improvement over SP 2.0. So far so good.

The trouble is with external access, which we find incredibly complex to set
up and so far does not work. Here is what we did :
- Under SP 3.0 Central Administration/Operations/Alternate Access
Mappings/Public Zone URLs, we have 1) under «default » the internal url ; 2)
under « internet » https://ip-address:portnumber, where the port number was
the one allocated to the site during the initial set up of the intranet
following the MS intructions (ie "25364") and the ip-address is our static
external address (also used to access RWW without difficulty, for example).
- Under IIS, we found the SP 3.0 web site created during setup, but with no
Certificate, which we then added (we used the existing cert also used for
RWW), and specified a SSL port different from the TCP one (which is the above
25364, so that the SSL is, for example, 8000). I think that I don’t really
understand how the SSL port works and what it is for, so I suspect that I am
doing something wrong here.
- In the Sonicwall, we opened both the 25364 and the 8000 ports
After trying different combinations of the above (for example : no
specification of the SSL port… ?), the SP 3.0 site still does not work
externally.
What I am doing wrong or missing ?
Thanks for your help
Charles


.

Relevant Pages

  • Re: companyweb from RWW
    ... "Could not open connection to the host, on port 23: ... internet should tell the tale, ... Les Connor [SBS Community Member - SBS MVP] ... This site is the default web site. ...
    (microsoft.public.windows.server.sbs)
  • Re: SharePoint 3.0: problems with external access
    ... Port 443 won't work because it is already used by the Default Web Site. ... The steps to publish WSS 3.0 applications behind ISA 2004 are the same as those that I posted earlier. ... Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ...
    (microsoft.public.windows.server.sbs)
  • Re: Publish External Websites Securely (ISA 2004)
    ... However, SSL to ... Enable SSL on this web site. ... select Directory Security tab, click Server Certificate button. ... you can access the web site from Internet thru ...
    (microsoft.public.windows.server.sbs)
  • RE: SSL Publishing to WEB Server and Disable Binding
    ... To answer your concern, you can feel to publish this SSL web site, and the ... Socket pooling causes Internet Information Services ... pooling won't impact the default web site on the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: companyweb from RWW
    ... Les Connor [SBS Community Member - SBS MVP] ... "Could not open connection to the host, on port 23: ... internet should tell the tale, ... This site is the default web site. ...
    (microsoft.public.windows.server.sbs)
Quantcast