Re: VPN versus Terminal Server for remote workers



Hi Kevin:

Hoping you can help here. With the "solid" hardware that supports VPN that
I have used, you have to have either a corresponding piece of that same
flavor hw at both ends, or a mobile user software client from that mfg, say
Watchguard or NetGear.

If all the remote users are in one, or even two places, the hardware to
hardware route seems perfect. But if there are 15 single users at 15
distinct locations, this has proved impractical for our folks. The mobile
software that I have used and tried is a pita to configure and maintain, and
when it is active you can only use the tunnel, not your browser
independently.

Please tell me there is a better way and that I have missed it.

--
Larry


"Kevin Weilbacher" <kw@xxxxxxxxxxxxxxxxxxx> wrote in message
news:E8F65A78-3F6D-453A-8AA3-D7F10D5B8ADF@xxxxxxxxxxxxxxxx
for 10-15 users, if you wanted to go VPN, then I would say look for a
solid hardware box that supports VPN.

as far as using Term Server, the question really is: does the app that
they will be using work in a term server environment? the advantage of
Term Server is that the remote users are connecting to a separate server,
and not directly to the SBS server.

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
*

"Orlando Bob" <OrlandoBob@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3907BC27-BE28-40E7-8E54-91C1061AA639@xxxxxxxxxxxxxxxx
What are the pros and cons of using VPN versus Terminal Server to support
10-15 remote workers? The primary application is a .NET Windows Forms
application that seems to run fairly well over a VPN connection. I am
inclined to use VPN unless there are compelling reasons to set up a
Terminal
Server.



.



Relevant Pages

  • Re: VPN versus Terminal Server for remote workers
    ... If one wants to cross the river and gets into a secure tunnel, ... this does not really help me understand why the hardware will allow ... By default and intention 'split tunneling' of VPN connections is not ... as far as using Term Server, the question really is: ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN versus Terminal Server for remote workers
    ... do not allow one to use both the tunnel and the default gw at the ... With the "solid" hardware that supports VPN ... they will be using work in a term server environment? ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN versus Terminal Server for remote workers
    ... called GlobalVPN client. ... With the "solid" hardware that supports VPN ... they will be using work in a term server environment? ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN versus Terminal Server for remote workers
    ... GlobalVPN client. ... With the "solid" hardware that supports VPN ... they will be using work in a term server environment? ...
    (microsoft.public.windows.server.sbs)
  • RE: h/w vpn reco that works well with sbs 2003
    ... I understand that you want hardware VPN for the SBS ... 2003 with 3 remote users. ... Microsoft can make no representation concerning ...
    (microsoft.public.windows.server.sbs)