I have a test SBS2003 server I am playing with at the
moment. All is running OK apart from accessing
HTTP://company web remotely. The page cannot be displayed.
I have an lmhost file with the external ip address
against the server name and company web
am I missing something
J
BTW, you have ISA installed on the SBS?
On the remote location, are you accessing SharePoint behind an ISA server?
If so, please follow the steps below:
1. Open notepad and paste the followings text.
set isa=CreateObject("FPC.Root")
set
tprange=isa.Arrays.GetContainingArray.ArrayPolicy.WebProxy.TunnelPortRanges
set tmp=tprange.AddRange("SSL 444", 444, 444)
tprange.Save
2. Save the file as ISA444.vbs
3. Double click ISA444.vbs at the remote ISA server.
4. Restart the Microsoft ISA Server Control at the remote ISA server.
5. Try to access SharePoint using https://IP:444 or https://FQDN:444
283284 Blank Page or Page Cannot Be Displayed When You View SSL Sites
Through
http://support.microsoft.com/?id=283284
Ray Fong
Microsoft SBS Product Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Make sure port 444 is being forwarded if you have NAT Router/fwall in front
of the server.
If using the external IP works, then you want to add the Companyweb host
name to the HOSTS file and not the LMHOSTS file.
You want to also be careful if the machine is going to be used in the local
LAN since then Companyweb will resolved to the wrong IP (internally it
should resolve to the private LAN IP of the server).
Regards,
Damian
--
Damian N. Leibaschoff, MS IST, MCSE
Microsoft Corporation
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jason" <anon...@discussions.microsoft.com> wrote in message
news:0a1501c3bb7c$ad292700$a001...@phx.gbl...
Port 444 just needed forwarding from my firewall
Thanks again.
"Damian N Leibaschoff [MSFT]" <dam...@online.microsoft.com> wrote in
message news:e5T4g73u...@TK2MSFTNGP12.phx.gbl...