Re: One SBS server - two offices



An aspect you need to look at here is data use. One method establishes a VPN
between the sites and this works well where the data being manipulated
remotely is smaller files. If your users need constant access to large files
(eg, flat file database contact management systems) pulling the data across
a VPN is problematic at best and likely to cause corruption of the files.

If each site is able to work on files on the local network, with only
occassional use of 'remote' files then a server at each site to hold those
'local' files works well.

In the case where manipulation of large data files is common and
particularly where both groups of users need this it is often more reliable
to implement a Terminal Server at the same location as your SBS. Remote
users come into the TS so file access is at 'local network' speed, only
screen updates need to move between the sites. 25Kbps per user gives decent
TS performance.

Outlook 2003 can access Exchange 2003 via a new method (in comparison to
earlier versions), RPC over HTTPS. This is particularly useful in remote
office situations. Though there is an overhead due to the client-server
traffic being encapsulated in RPC over HTTP it is designed for remote
connectivity so often more reliable than 'native Exchange' connectivity
through a VPN.

When I next need to do this for someone I am seriously going to consider not
having any user workstation (well, maybe just the remotes) in the SBS
domain. Possibly using thin client computers to connect to the Terminal
Server, possibly using XP Home even. Moving the operation completely to TS.

"David Thielen" <david@xxxxxxxxxxxx> wrote in message
news:lchba2dkpnobhof9odinseo6b8tomm0leo@xxxxxxxxxx
Hi;

We have just opened a second office that is about 2 miles from the
first (needed more space). So I have 7 peopel at the original office
and will have 7 more at the new one.

I want to run the new office off of the same domain server, exchange,
etc. How can I do this? I figure my issues are:
1) Verify domain logins at the new office.
2) get to network shares from each office that are at the other
office.
3) Outlook connections from the new office to the exchange server at
the old office.
4) Anything else?

thanks - dave

david@at-at-at@windward.dot.dot.net
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com


.



Relevant Pages

  • Re: Remote Access and ISA Server in SBS 2003?
    ... I am glad to hear the Remote Access Wizard is working fine now. ... there is no difference in VPN between SBS 4.5 and SBS ... Error Message: VPN Connection Error 800: Unable to Establish Connection ... the external NIC of the SBS Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 sudden services problem over router based vpn
    ... I understand that your remote cannot receive POP3 emails through VPN ... SBS Server through routers. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... If you have more than a couple of remote workstations connecting to the SBS ... server via VPN, you really need to consider a Terminal Server in the main ... "Log in using a dial up connection" checkbox, ... roaming profile then synchronizes with the server over the VPN); ...
    (microsoft.public.windows.server.sbs)

Quantcast