Re: SharePoint 3.0: problems with external access

Costas,
I followed your advice again, and everything is working now, both externally
and internally.

Thank you very much !

"Costas" wrote:

Charles,

Glad to hear external access worked. As far as editing directly the IP
address in IIS, that is something that isn't recommended with SharePoint
sites. Anything you need to do, you must do from within Central
Administration.

If the application didn't work internally, having as IP address the 'All
Unassigned', that most probably means, that you didn't provide a host header
name when you created the application. If a host header is defined, IIS
knows where to router the requests for 'http://mysite'

--
Costas


"Charles" <Charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEBDDCE0-1ADB-4407-B003-D6B4F80C03ED@xxxxxxxxxxxxxxxx
Costas,
Many thanks, this is exactly the input I needed. So the port number one
needs in the external address is in fact the port used by SSL! Of course
of
course. So I did exactly that and...it works externally, great !

I had an issue with internal access as a result of the changes, but I
think
I will able to solve it on my own (or so I hope-;): under the SP 3.0
website
in IIS, I had to tweak the IP address under properties (from undetermined
to
192.168.16.2) so that I regained internally access. Any thoughts on that?
Correct you think?

Unfortunately I cannot test external access right now because I am on the
LAN and that my computer at home is not available for VPN (btw, do you any
easy way to test remote access other than VPNing a specific computer off
the
LAN?)

Anyway I will keep you posted on external+internal access but the hardest
part is behind me now, thanks again
"Costas" wrote:

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: SharePoint 3.0: problems with external access
    ... As far as editing directly the IP address in IIS, that is something that isn't recommended with SharePoint sites. ... needs in the external address is in fact the port used by SSL! ... Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ...
    (microsoft.public.windows.server.sbs)
  • Re: Repost: Help required with SSL & ISA
    ... //My Main Web Site (Using Port 80 and Host Headers) ... If I setup this up without SSL it works - but I dont wish to proceed without ... It maps the external domain name to the internal site and ... >>Internet Security and Acceleration Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Proxy errors for internal web links
    ... ISA Server is not configured to allow SSL requests from ... >> port. ... > Microsoft Internet Security & Acceleration Server: ...
    (microsoft.public.isa)
  • Re: Changing the way IIS answers to PASV commands?
    ... it's not an IIS FTP issue. ... translating address and port from external request to ... I can add my internet IP address as a secondary IP harmlessly ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: Linux als Router
    ... # Enter all trusted network interfaces here. ... # which should be available to the internet and set FW_ROUTE to yes. ... space separated list of ports, ... # Packets to silently reject without log message. ...
    (de.comp.os.unix.linux.misc)
Loading