"Dweeberella" <Dw*********@discussions.microsoft.comwrote in message
news:13**********************************@microsof t.com...
Thank you Mr. Arnold for your proposed security solution.
My network consultant proposed activating VPN which he says is already
available in Windows server. Why is Citrix VPN better than that?
<http://74.125.45.104/search?q=cache:1DFCgafThkwJ:www.seceidos.de/fileadmin/media/documents/Citrix_Access_Gateway_7-0_Enterprise_Edition_-_Technical_Presentation__englisch_.ppt+citrix+vpn+ session+with+browser&hl=en&ct=clnk&cd=4&gl=us>
The client on the other end is using a *browser session* to login into the
Citrix Terminal server with a VPN connection and using NT authentication to
login to the NT based O/S server running Citrix Terminal server. I would
assume that the NT server O/S machine running Citrix Terminal server would
be on a local NT domain.
That means the user uses a Citrix browser VPN client session to login to the
Citrix terminal server desktop to run your Windows Desktop solution, with
your desktop solution using a user-id and psw to log into your Windows
desktop solution using .Net role-based security to authentication the user
logging into the desktop solution, after he or she logged into the Citrix
Terminal server.
>
You propose using VB.Net rather than ASP.Net. For VB.Net, we don't need
IIS activated, right? It sounds to me like a more secure solution is to
keep
IIS deactivated and use VB.Net rather than ASP.Net. What do you think?
ASP.NET Active Server Pages is using IIS and VB.Net or C#.Net as the Code
Behind file solution language.
With a VB.NET Windows Desktop solution running on a terminal server such as
Citrix or other VPN solution is a more secure solution for your internal
company solution that must be run by other users outside of your local NT
domain, and your desktop solution doesn't need IIS.
>
How does SSL fit in with this? We don't need an SSL certificate if we
use
VB.Net rather than ASP.Net, right?
With Citrix software, one can be in a SSL session with a client Web browser
and the Citrix terminal server.
The thing you should recognize is that the user is using a browser session
to access the Citrix Terminal server and running the solution on the Citrix
Terminal server desktop as if the user was running it from his workstation
desktop, with the connection between the Citrix Terminal server and the
user's Citrix terminal client session being in a secure connection.
I am just giving you more options. However, I have seen Citrix being used
internally across multiple company NT domains, and by users in remote
locations using dial-up, BB, and DSL within the same company infrastructure
to access a solution on a global wide bases used by internal company users.
It just happened that the solution was running on 20 Citrix terminal servers
in a Citrix terminal server farm. You may not get to that capacity. :)