[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

Trying to establish a way for users to connect to SBS with Outlook calendars at the remote location

Two Linksys BEFVP41 one North and one 50 miles away at South office.
Cayman 3546 DSL in bridge mode at North office in front of Linksys.
2Wire DSL in bridge mode at South office in front of Linksys.
SBS 2003 R2 server at North office. Both sites have internet access and SBS working normally.
I want users at the South office to join the SBS domain and be able to get Outlook Calendar updates and Sharepoint access like internal users.  I also have a second member server at the South office I want to join the domain as well.
I can not see the domain when the VPN connection is established or even tell it is working other than Linksys shows it is connected in the admin screen.
Can someone give me some insight, can I acomplish the goal?  How can I tell the VPN is really connected to the North office since I can not see any resources?  Browsing for Network resources does not work.
  • 2
  • 2
2 Solutions
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If all you need for them to access is Outlook and SharePoint, the computers don't necessarily need to join the domain, nor do you need to have them connect via VPN.

For Outlook 2003, use RPC over HTTPS.

This feature must be enabled in the Configure Email and Internet Connection Wizard (CEICW -- which is linked as Connect to the Internet in the Server Management Console > To-Do List) by checking the box on the Web Services Configuration Screen for "Outlook via the Internet".

A visual how-to is here:  http://sbsurl.com/ceicw

Port 443 must be open on your router/firewall.

Then RPC over HTTPS client configuration instructions are on the server's Remote Web Workplace main menu -- linked as "Configure Outlook via the Internet" -- access the RWW Main Menu by going to http://localhost/remote from on your server.  (See http://sbsurl.com/rww for more info on RWW).

A full overview for SBS based RPC/HTTPS configurations is here:  http://sbsurl.com/rpc

For SharePoint, they can either access it via the RWW main menu, or directly at https://server.domain.com:444

Port 444 must be open on your router/firewall, and Windows SharePoint Services Intranet Site must be enabled on the Services Configuration Screen of the CEICW.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
FYI, if you've created a VPN Tunnel between the routers, then there would not necessarily be any direct access between the remote office and the domain because you would still need domain authentication.  If you want the second member server at the remote office to join the domain, that would best be done by having that server attached locally to your SBS and then deploying it in the remote location after you've set it up properly as a secondary domain controller.

There are a number of resources on setting up a branch office DC for an SBS Network.  One of the best can be found at www.smallbizserver.net (membership required though for those articles:  http://www.smallbizserver.net/Articles/tabid/266/articleType/CategoryView/categoryId/61/Branch-offices.aspx).

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Your two offices will be on separate IP ranges.
You will need to configure the VPN Router into RRAS with pointers to the respective IP range of the OTHER
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Your two offices will be on separate IP ranges.
You will need to configure the VPN Router into RRAS with pointers to the respective IP range of the OTHER office.
You should then be able to ping each other across the VPN assuming that it is tunnelled correctly.
To join the S. office server, bring it up and DCPromo it into the SBS domain after running the server setup wizard on the SBS box. If W2K3 R2, then Adprep /forestprep and adprep /domainprep on the SBS box from the W2K3 R2 CD which is in the SBS box's CDROM.
Note that the IP setup on the W2K3 box will need to be changed when on the SBS network, and then changed back. If it is server DHCP, then the service will need to be set to manual before firing it up on the SBS domain so as to not cause SBS fits. ;)
You will then be able to DCPROMO.
Set the new DC as Global Catalogue after you bring the box back the S. and reconfigure the DHCP on the box with the appropriate settings for the VPN box, and verify the static route in RRAS on both boxes.
You should now have AD and DNS replication going across the VPN, along with Exchange, and Companyweb.
For WSUS, install it locally on the S. server, setup an OU on the SBS box for all of the computers at the S. location, and set them via Group Policy to gather their updates from the local server. This saves on bandwidth. You can set the S. WSUS server to gather updates late at night directly from MS to save on VPN bandwidth as well.
That is it in a nutshell.
There are lots of steps in between but this should give you the outline you need to get things working.

i need a little more information here....

if you are creating a VPN between the two routers, then you will have a link between the two sites. But you need to make sure your IP addressing is correct. Generally through VPN tunnels created by 'home' routers DNS will not work very well through them, so you may have some problems connecting to the domain as this relies on DNS....

You may be better of using RRAS within Windows server to get the VPN connection setup...


Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now