RE: Remote Access to Sharepoint VIA RWW

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hello Jenny,

Thank you for the information.. I think this is the answer.. however, I ran
into a problem creating the Server Publishing Rule. I'm getting "the IP
address is not defined on this array". We were issues 5 external IP's from
our ISP (xxx.xxx.xxx.33 through xxx.xxx.xxx.37) with .33 being used by the
server now.

What do you think?

Thank you!

""Jenny wu [MSFT]"" wrote:

> Hi,
>
> Thanks for your detail description. I do understand your scenario now. I
> have researched the solution and you can see my steps below to see if it
> helps.
>
> The companyweb is based on the Share Point service which has some known
> issues when working with the ISA's SSL bridging. That's to say, if you are
> using the ISA Server 2000 to implement SSL to SSL bridging, some sub-pages
> may not work properly. The only way we can do in the SBS environment is to
> use the SSL tunneling to publish the companyweb.
>
> To do it, we can perform the following steps:
>
> I. For illustration, let's assume that 1.1.1.1 and 1.1.1.2 are two public
> IP addresses of your SBS Server which can be reached by internet users, and
> 192.168.1.1 and 192.168.1.2 are two internal IP addresses of your SBS
> Server. First, let's register two FQDN at the ISP side:
>
> https://www.company.com
> https://intra.company.com
>
> Note: the URL https://www.company.com is for RWW/OWA and the URL
> https://intra.company.com is used for companyweb. The first URL should be
> resolved to 1.1.1.1 and the second one needs to be resolved to 1.1.1.2.
>
> II. Configure the companyweb virtual directory to listen to the additional
> internal IP address 192.168.1.2 on port 443. (while the OWA/RWW is
> listening on 192.168.1.1)
>
> III. Create an ISA server publishing rule to publish the companyweb site
> (Note: not the web publishing rule) as following:
>
> Rule Name: Publishing companyweb
> IP address of internal server: 192.168.1.2
> External IP address on ISA Server: 1.1.1.2
> Protocol Settings: HTTPS Server
> Client Type: Any request
>
> IV. Check the VD of the companyweb on the IIS, make sure the
> publishing.domain.local certificate has been bound to the site.
>
> After performing the above steps, now you will be able to access the
> companyweb via https://intra.company.com and get rid of the port 444.
>
> Hope above information helps! If you have any unclear about information I
> provided please let me know. I am happy to be of assistance to you.
>
> Have a nice day!
>
> Sincerely,
>
> Jenny Wu
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> 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 e-mail notifications when there are
> any updates in your thread. 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 CSS 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.
>
> --------------------
> >Thread-Topic: Remote Access to Sharepoint VIA RWW
> >thread-index: AcYgU2slCxsKTRADTBm783Xw1rH5eg==
> >X-WBNR-Posting-Host: 67.149.107.195
> >From: "=?Utf-8?B?SG90U2l6emF1Y2U=?="
> <HotSizzauce@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <4877E2BD-9BF3-43E3-BD6E-984E7DFA87FB@xxxxxxxxxxxxx>
> <AdG7#i$HGHA.3696@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Remote Access to Sharepoint VIA RWW
> >Date: Mon, 23 Jan 2006 11:30:07 -0800
> >Lines: 191
> >Message-ID: <8FC0E915-4012-4B5F-AD15-606B09F5F76A@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238725
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hello Jenny,
> >
> >The reason I need to do this is because one of the sites our engineers
> >travels to will not open port 444 for us to communicate. So I need to add
> >another Ip and assign the companyweb to port 443. If you look at Chad
> >solution, it entails this but not enough detail for me to feel comfortable
> >performing it on the server. What I need is a more detail. Here is what
> Chad
> >wrote:
> >
> >Obtain an additional public static IP from your ISP. You will want to
> >bind another private IP to the LAN nic in your server, update your
> internal
> >DNS so that companyweb resolves to this new private IP, and change the
> host
> >headers in IIS for the companyweb site to listen on this new private IP.
> >From there, have your router (whether hardware device on the LAN or ISA on
> >SBS Premium) forward requests from the new public IP to the new private
> IP.
> >This will break the companyweb link from the RWW main page, and I'm not
> sure
> >if it could be fixed easily or not. Best solution would be to create a
> new
> >A record in your public DNS (something like intranet.company.com) that
> >resolves to this new public IP. That way your remote engineers would
> access
> >your companyweb via https://intranet.company.com ; instead of via the RWW
> >main page.
> >
> >I have been able to modify the RWW main page to allow access to the
> company
> >web.
> >
> >Can you help?
> >
> >Thanks!
> >
> >
> >""Jenny wu [MSFT]"" wrote:
> >
> >> Hi,
> >>
> >> Thanks for using the SBS newsgroup.
> >>
> >> I am sorry for the delayed response due to weekend. Please understand
> that
> >> the newsgroups are staffed weekdays by Microsoft Support professionals
> to
> >> answer your systems and applications questions. Your understanding is
> >> greatly appreciated!
> >>
> >> From your description, I understand that you want to know how to
> configure
> >> users access the Companyweb site through RWW from internet. If I am off
> >> base, please don't hesitate to let me know.
> >>
> >> To access the companyweb site through RWW from internet, you just need
> >> publish Companyweb site and RWW site to internet (I am not unclear why
> you
> >> need another public FQDN to host the companyweb). You can run CEICW
> >> (Configuration E-mail and Internet Connection wizard) to open related
> ports
> >> in firewall (80,443,444, 4125)
> >>
> >> *Note: If you have installed any hardware firewall or router outside the
> >> network, you need manually open related ports (80, 443,444, 4125) on the
> >> hardware firewall or router.
> >>
> >> 1. Expand Standard Management | To Do List.
> >> 2. Click Connect to the Internet in the right pane.
> >> 3. Navigate the wizard to Firewall and then select Enable firewall. In
> the
> >> next page, make sure items you want to publish services are checked in
> >> services configuration page.
> >> 4. Click Next and then select Allow access to the following web site
> >> services from the internet.
> >> 5. Make sure Windows Sharepoint Services Intranet site and Remote Web
> >> Workplace are selected and click Next.
> >> 6. Click Create a new Web services certificate (input your FQDN as the
> web
> >> server certificate) and then click Next.
> >> 7. Following the wizard to finish it.
> >>
> >> It is recommended you take a look at the following KB article to get
> detail
> >> steps to configure network connection:
> >>
> >> 825763 How to configure Internet access in Windows Small Business Server
> >> 2003
> >> http://support.microsoft.com/?id=825763
> >>
> >> Then please try to access the Companyweb site through RWW from remote
> site,
> >> what is the result? If not, what is the exact error message? Please help
> me
> >> collect some screen shots when reproduced the issue. Please paste the
> >> images in the newsgroup or mail to my working mailbox:
> >> v-yanniw@xxxxxxxxxxxxx
> >>
> >> Also please try to access the Companyweb site using the URL:
> https://public
> >> FQDN, what is the result?
> >>
> >> If it is not the situation, please let me know more detail information
> >> about your scenario.
> >>
> >> Hope above information helps! I am happy to be of assistance to you and
> >> look forward to your reply!
> >>
> >> Have a nice day!
> >>
> >> Sincerely,
> >>
> >> Jenny Wu
> >> Microsoft CSS Online Newsgroup Support
> >> Get Secure! - www.microsoft.com/security
> >> ======================================================
> >> This newsgroup only focuses on SBS technical issues. If you have issues
> >> regarding other Microsoft products, you'd better post in the
> corresponding
> >> newsgroups so that they can be resolved in an efficient and timely
> manner.
> >> You can locate the newsgroup here:
> >> 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 e-mail notifications when there
> are
> >> any updates in your thread. 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 CSS 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.
> >>
> >> --------------------
> >> >Thread-Topic: Remote Access to Sharepoint VIA RWW
> >> >thread-index: AcYe+e66Y2OIOhz1RgaLsR8X0BJ8aw==
> >> >X-WBNR-Posting-Host: 67.149.107.195
> >> >From: "=?Utf-8?B?SG90U2l6emF1Y2U=?="
> >> <HotSizzauce@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> >Subject: Remote Access to Sharepoint VIA RWW
> >> >Date: Sat, 21 Jan 2006 18:17:02 -0800
> >> >Lines: 33
> >> >Message-ID: <4877E2BD-9BF3-43E3-BD6E-984E7DFA87FB@xxxxxxxxxxxxx>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >> >Newsgroups: microsoft.public.windows.server.sbs
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:238434
> >> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >> >
> >> >Hello,
> >> >
> >> >Our company has engineers who travel extensively and work remotely
> behind
> >> >other companies domains. I have one company in which our employees
> can't
> >> >access our "companyweb" because this company has it's ports set to
> stealth
> >> >mode.
> >> >
> >> >Chad Gross has made this recommendation that would change the
> dependency
> >> of
> >> >Companyweb from port 444:
> >> >
> >> >Obtain an additional public static IP from your ISP. You will want to
> >> >bind another private IP to the LAN nic in your server, update your
> >> internal
> >> >DNS so that companyweb resolves to this new private IP, and change the
.

Relevant Pages

  • Re: companyweb from RWW
    ... accessing the companyweb url from internal. ... I checked IIS and found the following websites on the SERVER: ... Internet and from a client PC on the LAN. ... Les Connor [SBS Community Member - SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • RE: Move Companyweb to member server 2003
    ... password login box; I would like for our clients and employees to login by ... The webserver is not a backup domain server, nor anything else (ie DNS, ... I understand that you want to know if the Companyweb ... published to internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: CompanyWeb
    ... I understand that the client computers can not access ... and internal NICs'' DNS of SBS server will be both pointed to internal NIC ... 825763 How to configure Internet access in Windows Small Business Server ... the Companyweb site? ...
    (microsoft.public.windows.server.sbs)
  • Re: Companyweb will not load.
    ... Microsoft Small Business Server Support ... Properties of the companyweb site in the IIS mmc.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Company Web Question
    ... Acceleration (ISA) Server so that external clients can connect via RWW. ... c Internet Information Services - assign web certificate to Companyweb ...
    (microsoft.public.windows.server.sbs)