Best practices with Terminal Services
From: Matt (matt@businesscomputing.com.au)
Date: 08/30/02
- Next message: Jason Penn: "Re: Expiration Date of Sub-CA's won't change."
- Previous message: Kyle: "rpcss.exe and msgsrv32.exe"
- Next in thread: S. Pidgorny [MVP]: "Re: Best practices with Terminal Services"
- Reply: S. Pidgorny [MVP]: "Re: Best practices with Terminal Services"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Matt" <matt@businesscomputing.com.au> Date: Thu, 29 Aug 2002 18:04:52 -0700
If connecting to a sbs 2000 server via terminal services
client or remote desktop is that enough security or
should we also be connecting by using vpn aswell?
But then vpn adds more steps for users to connect to the
server.
Is there a way (if using vpn is recommended) where say
remote desktop establishes the vpn automaticly when
connecting to the server?
Currently if we are to setup a vpn aswell the steps
needed are
1.connect to internet (not needed if on broadband)
2.click on vpn connection icon
3.click on remote desktop icon
but then when using vpn things like viewing websites on
your local pc's ie6 and recieving emails on your local
copy of outlook isn't possible, or is it?
thanks to anyone who can help
Matt
- Next message: Jason Penn: "Re: Expiration Date of Sub-CA's won't change."
- Previous message: Kyle: "rpcss.exe and msgsrv32.exe"
- Next in thread: S. Pidgorny [MVP]: "Re: Best practices with Terminal Services"
- Reply: S. Pidgorny [MVP]: "Re: Best practices with Terminal Services"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|