Re: Accessing a Secured Internal Web Site link from Companyweb
- From: v-bpeng@xxxxxxxxxxxxxxxxxxxx ("Bill Peng [MSFT]")
- Date: Thu, 23 Aug 2007 02:46:41 GMT
My pleasure.
After you use RRAS or ISA to publish the site, you can use
http://public.domain.name:442 to access the web site.
If you need further assistance, please feel free to post back.
Sincerely,
Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
The public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate newsgroup
to get most qualified responses.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive notification. When responding to
posts via your newsreader, please "Reply to Group" so that others may learn
and benefit from your issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Ex-Engineer" <Ex-EngineerNOSPAM@xxxxxxxxxxx><u8W2nUl4HHA.2108@xxxxxxxxxxxxxxxxxxxx>
References: <uSqtbqj4HHA.5316@xxxxxxxxxxxxxxxxxxxx>
<uAT8Hv84HHA.5980@xxxxxxxxxxxxxxxxxxxx>
<UcaRgcI5HHA.6140@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Accessing a Secured Internal Web Site link from Companywebprovide
Date: Thu, 23 Aug 2007 08:35:16 +1000
Lines: 127
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Message-ID: <Oz8t5yQ5HHA.2108@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: 203-206-5-169.dyn.iinet.net.au 203.206.5.169
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:58358
X-Tomcat-NG: microsoft.public.windows.server.sbs
Thanks Bill - an excellent "how to".
Great Support!
Yours appreciatively,
Ex-Engineer
""Bill Peng [MSFT]"" <v-bpeng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:UcaRgcI5HHA.6140@xxxxxxxxxxxxxxxxxxxxxxxxx
At this point, it's an expected behavior. This is because you're not able
to access the internal server via Server Name on the internet. There're 2
workarounds.
Method 1. Please establish a VPN connection to the SBS site, and then
you're able to access the internal server via Server Name.
Method 2. You can publish the internal server's SSL port, and access it
from the internet.
If you're using RRAS (without ISA):
On the SBS server, open the Routing and Remote Access MMC from
Administrative Tools. Expand your server, IP Routing and select NAT/Basic
Firewall. On the right panel select your external/network connection and
open the Properties. Go to the Services and Ports tab, click Add,
thea
name, select TCP as the protocol, the incoming port (442), the IP address
of the server behind SBS and the outgoing port (442). Click Ok to save
changes. This should allow the port to come into the server through the
SBS
server.
If you're using ISA 2004:
1. Open ISA Management.
2. Right click Firewall Policy -> New -> Web Server Publishing Rule.
3. Name it.
4. Choose Allow.
5. Choose the computer.
6. Key in the domain name.
7. Click New to create a new web listener.
8. Listen on External network, and choose "Enable SSL" on port 442, and
select the certificate that matches your public domain name.
9. Follow the instruction to finish the wizard.
I hope the above info helps.
Sincerely,
Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
The public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate
newsgroup
to get most qualified responses.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive notification. When responding to
posts via your newsreader, please "Reply to Group" so that others may
learn
and benefit from your issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
From: "Ex-Engineer" <Ex-EngineerNOSPAM@xxxxxxxxxxx><u8W2nUl4HHA.2108@xxxxxxxxxxxxxxxxxxxx>
References: <uSqtbqj4HHA.5316@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Accessing a Secured Internal Web Site link from Companyweb
Date: Tue, 21 Aug 2007 18:17:52 +1000
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-RFC2646: Format=Flowed; Response
Message-ID: <uAT8Hv84HHA.5980@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: visp.inabox.net 203.49.193.210
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:57967
X-Tomcat-NG: microsoft.public.windows.server.sbs
Hi Simon,
Thanks for responding. Yes it does. We have set it up with our existing
self-signed certificate and placed the SSL port at 442; works fine
internally!
Cheers
Ex-Engineer
"simon" <news@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u8W2nUl4HHA.2108@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Does the link reference an internal url ?
simon
ex-engineer wrote:
We have set up an internal web site for a specialised application, all
works well with internal HTTP and HTTPS connections. We have placed a
link to this site on companyweb which internally also works well.
However, when we access Companyweb externally, the link on companyweb
returns a Page Not Found error.
What have we missed?
Regards,
Ex-Engineer
.
- References:
- Accessing a Secured Internal Web Site link from Companyweb
- From: ex-engineer
- Re: Accessing a Secured Internal Web Site link from Companyweb
- From: simon
- Re: Accessing a Secured Internal Web Site link from Companyweb
- From: Ex-Engineer
- Re: Accessing a Secured Internal Web Site link from Companyweb
- From: "Bill Peng [MSFT]"
- Re: Accessing a Secured Internal Web Site link from Companyweb
- From: Ex-Engineer
- Accessing a Secured Internal Web Site link from Companyweb
- Prev by Date: Re: 2 Exchange mail boxes on 1 domain account
- Next by Date: Re: mail not sent outside to smart host
- Previous by thread: Re: Accessing a Secured Internal Web Site link from Companyweb
- Next by thread: Re: mail not sent outside
- Index(es):
Relevant Pages
|
