Re: Configuring SBS to allow Remote Access

From: DoomSlayer (anonymous_at_discussions.microsoft.com)
Date: 04/18/04 

Date: Sun, 18 Apr 2004 15:12:25 -0700

Merv you are very helpful ... thank you :)

Now that I understand that a little better we most
definitely will continue to host the website elsewhere as
it is today ...

We have SBS2003 Premium. We don't currently have SMTP
mail in use - we use external POP email which we collect
in Outlook as we haven't got as far yet as figuring out
how to setup Exchange.

So just to recap on this RWW scenario ...

In order for my users to access the SBS using RWW I have
to ask my ISP to setup an MX record, an A record,
pointing to the SBS server. Our existing Satic IP may or
may not already be one of those so I've asked them to let
me know.

The next step would be to create or for that matter
recreate a certificate for the SBS server which is
already setup using for example ourteam.xyz.com. How the
heck do I do that?

After that I then just get my users to access the SBS
server via https://ourteam.xyz.com/remote. Is that
right?

>-----Original Message-----
>Port 80 does not need to be opened just to use RRW. You
would be using port
>443 for a secure connection (https://fqdn/remote).
>
>Port 80 is the number one attack port for hackers.
Since you have
>everything on one server (Exchange, company data, user
data, etc.) you could
>compromising your entire network. It would be much
better to have someone
>else host your web site or but the web site on a
separate server that is
>locate in a the DMZ behind your router.
>
>Do you want to host a web site on your SBS...
>http://www.sbslinks.com/HOSTING.htm
>
>Another question... do you have SBS 2003 Premium or
Standard?
>
>Accessing RWW... I'm assuming you have a static IP
address from your ISP and
>that you have an MX record and "A" record created by the
ISP so that you can
>use SMTP for email. When you create the certificate,
you can use:
>mail.abcdefgh.com
>or you can use the static WAN IP of your server
(xxx.xxx.xxx.xxx).
>Whichever you select, your remote users would have to
follow suit when
>accessing via RWW: https://mail.abcdefgh.com/remote
or
>https://xxx.xxx.xxx.xxx/remote
>
>If your are going to take the route of hosting your own
web site on your
>SBS, you would have your ISP set up an "A" record
pointing to your SBS
>server and you would use: bob.adgdefgh.com for the
certificate. RWW
>users would then enter:
https://bob.abcdefgh.com/remote or
>http://www.abcdefgh.com/remote in their web browser.
>
>You would also need to use port forwarding in your
router's setup program to
>forward ports to the external NIC on your SBS. (most
commonly 443, 444,
>4125; and port 80 for http:// traffic, if you host your
own web site on your
>SBS)
>
>--
>Merv Porter [SBS MVP]
>===================================
>"DoomSlayer" <anonymous@discussions.microsoft.com> wrote
in message
>news:088901c42540$a1cf2b60$a101280a@phx.gbl...
>> Hi Merv
>>
>> It would appear from reading the documentation that if
we
>> were to use Remote Web Workplace then we would still
need
>> to have Port 80 opened in which case we might as well
>> host our own website there.
>>
>> Here's something that I can't find out about.
>>
>> We have a website example: www.abcdefgh.com hosted with
>> XYZ.
>>
>> We also have ADSL services provided by QWERTY ISP.
>>
>> Our SB Server is called BOB and so we created a self
>> certificate during installation of BOB.abcdefgh.com.
>>
>> How do we then setup our SBS Server BOB for Remote Web
>> Workplace?
>>
>> ie. I can't get my head around this. Do we need to add
>> BOB.abcdefgh.com to DNS servers at our QWERTY ISP? I'm
>> not too techie when it comes to DNS and I can't find
out
>> what the heck I'm supposed to in any documentation
that's
>> in plain speak and makes sense.
>>
>> Thanks for your help so far.
>>
>>
>> >-----Original Message-----
>> >Is this SBS 2003 Premium or Standard?
>> >
>> >The help files in SBS 2003 are a good start. Also...
>> >
>> >Host website... this may not be the most secure setup
>> since all your other
>> >apps and data will reside on the same domain
controller
>> and port 80 must be
>> >opened. May be better to have your ISP or another
>> entity host your web
>> >site. Then you can update it as needed from behind
the
>> relative safety of
>> >your SBS.
>> >http://www.sbslinks.com/HOSTING.htm
>> >
>> >Remote Access... if the LAN workstations are WinXP Pro
>> and only one user is
>> >assigned to each workstation, Remote Web Workplace
will
>> allow secure remote
>> >control of the LAN workstation from any point on the
>> Internet. CEICW (and
>> >the help files therein) will set this up. Your router
>> need some ports open
>> >and/or forwarded:
>> >
>> >Table A: Ports that Enable Remote Access to SBS
Services
>> >http://www.winnetmag.com/Files/40832/Table_01.html
>> >
>> >Remote Web Workplace - How it works Part 1
>> >http://www.sbsfaq.com/news/getArticle.asp?
>>
MessageID=000000001A447390AA6611CD9BC800AA002FC45A0900E049
>>
B559A334DD479C5D360FB473600B0000000187180000E049B559A334DD
>> 479C5D360FB473600B0000000249E20000&path=News/
>> >
>> >TechNet Support WebCast: An overview of Microsoft
>> Windows Small Business
>> >Server 2003 Remote Web Workplace feature
>> >http://support.microsoft.com/default.aspx?scid=kb;EN-
>> US;833983
>> >
>> >Share Point can be published for external users:
>> >How to publish http://Companyweb to the Internet by
>> using ISA Server 2000 on
>> >a server that is running Windows Small Business Server
>> 2003, Premium Edition
>> >http://support.microsoft.com/?kbid=838304
>> >
>> >Publishing a SharePoint Site Accessible to External
Users
>> >http://www.microsoft.com/downloads/details.aspx?
>> FamilyID=B51DCB25-0C63-4561-B981-
>> 9A3C860B9F15&displaylang=en
>> >
>> >--
>> >Merv Porter [SBS MVP]
>> >===================================
>> >
>> >"DoomSlayer" <anonymous@discussions.microsoft.com>
wrote
>> in message
>> >news:016101c42406$8377b280$a501280a@phx.gbl...
>> >> This is our current config:
>> >>
>> >> SBS2003
>> >> Two NIC's installed
>> >> ADSL Modem/Router on one side connected to one NIC.
>> >> Internal Network on the other NIC.
>> >> ONE Static IP with our ISP.
>> >> Our own domain.
>> >>
>> >> We wish to allow Remote Access for various reasons.
>> >> Access to internal data for some company users.
Access
>> >> to Sharepoint Services Intranet for all company
users.
>> >> Hosting of our own website and access for all
internet
>> >> users.
>> >>
>> >> Could someone please explain where to begin? We're
not
>> >> complete tech heads but we understand our RAM from
our
>> >> ROM. :)
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • Re: Upload form
    ... shoots using my web site. ... My host uses a UNIX server. ... > transfer my site to a Windows server in order to get the upload form to ...
    (microsoft.public.frontpage.client)
  • Re: Web Server on XP Pro
    ... the Windows XP into the domain. ... features of the server versions. ... I wonder why you would host the web site on a Windows XP Pro ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs 2008 - no Internet access possible to 2nd server
    ... IIS can have security flaws and if your webserver gets compromised, it is better to have that server on its own network so the baddies don't get back to your LAN. ... I have had clients, in the past insist that I use the 'free' port forwarding setup. ... Agree with Larry that it is not a good practice to publish web site in the ...
    (microsoft.public.windows.server.sbs)
  • Re: public web site
    ... You'd create another A record for "www" and point it at your website IP, which you'll get from your website host company when you sign up. ... Windows Small Business Server 2008 Unleashed ... IP and change the A record to point to the IP of my web site? ...
    (microsoft.public.windows.server.sbs)
  • Re: Limiting RMI to localhost
    ... Then I bound the server socket to the local host and it stopped ... In the sample I implemented server socket factory so I'll be able to ... public abstract String sayHellothrows RemoteException; ... public Socket createSocket(String host, int port) throws ...
    (comp.lang.java.programmer)