publishing Terminal Server
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
Date: Wed, 18 Aug 2004 13:44:00 +0200
Hi,
I've managed to publish a Windows 2003 Terminal Server in ISA 2000. So far
so good. Now external users can connect to my terminal server without using
VPN. First of all... how safe is such a connection and second, what are the
benefits of connecting directly and not use VPN..
Bernard
Relevant Pages
- Re: router - firewall
... Adzap, VPN, OpenSwan, ... > connections several ways: ... > the connection is to the Terminal Server, ... > We setup most offices with a VPN into a firewall appliance, ...
(microsoft.public.windows.server.sbs) - Re: anyone using PPC for remote Network/Server Administration?
... If the Terminal Serveryour trying to connect to through the VPN tunnel use dotted address ... but when I connect through the VPN and launch the terminal server client ... >>>>>I have HP Ipaq 6215, and am using Terminal Server Client for remote administration, but the ...
(microsoft.public.pocketpc) - Re: router - firewall
... Adzap, VPN, OpenSwan, ... but because most users will have slow internet connections when ... the connection is to the Terminal Server, ... We setup most offices with a VPN into a firewall appliance, ...
(microsoft.public.windows.server.sbs) - Re: locking down Terminal Server in SBS2003 environment (regular users)...not a duplicate question
... Firewall-to-Firewall VPN between Richmond and each location. ... The users in the remote offices have a hard time connecting to documents ... they are connected to the terminal server (which is sitting right next to ... the Accounting Software is indeed installed on the SBS2003 ...
(microsoft.public.windows.server.sbs) - Re: VPNs and Hotels - Any travelers out there?
... The core technology is based on ... >> VPN access for individual users is currently legacy technology and nearly ... >> Microsoft MVP - Terminal Server ...
(microsoft.public.windows.terminal_services) |
|
