my personal choice would be to provide a linux
(router/gateway point) at each end that you wish to
service. These machine would be connected by t1/t3
whatever combination you wish and can afford and VPN
to connet the two Lans. these machines act as
security, connection, print, and file servers. Of
course, you can always get more complicated, adding
redundency, fail-over, monitoring facilities, dynamic
online disaster recovery and such... just more money:)
Good luck
Rob
--- pwgrant <pwgrant@cssi-fl.com> wrote:
> It would be used for "general business use." I
> understand many of the high
> level aspects and some of the more granular topics.
> A client wants to print
> to a printer across the wire ad file access on a
> central server. For the
> printing purpose I might be more in favor of
> dropping PDF files for pick by
> a client workstation and the remote office. The
> traffic to one site in
> intra-state and another would be inter-state.
>
> A more elegant solution might be to have enough
> bandwidth to support LAN
> traffic and voice or IP.
>
> -----Original Message-----
> From: slug@lists.nks.net
> [mailto:slug@lists.nks.net]On Behalf Of Matt
> Miller
> Sent: Friday, March 14, 2003 2:16 PM
> To: SLUG List
> Subject: Re: [SLUG] Links LANs
>
>
> On Fri, 2003-03-14 at 13:46, pwgrant wrote:
> > How would "you" recommend linking LANs?
>
> 2 cups and a string.
> OR
> 4 cups and 2 strings. (for redundancy)
>
> :)
>
> --
>
> Matt Miller
> Systems Administrator
> MP TotalCare
> gpg public key id:
> 08BC7B06
>
> --
> The tree of liberty must be refreshed from time to
> time, with the blood
> of patriots and tyrants. -- Jefferson
>
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:59:39 EDT