Use the VPN to create an inroad into the internal network. For those 
bandwidth-hungry apps have the user connect to an RDP server; processing and 
storage will then all be local. The user can later copy whatever information he 
needs on his end.

And all this science I don't understand
It's just my job five days a week

Elton John "Rocket Man"

> On Oct 29, 2013, at 11:25, "Rankin, James R" <[email protected]> wrote:
> 
> Wouldn't something like Citrix XenApp offload the performance hit onto the 
> local network for your remote users? Granted, not your query, but it would 
> allow VPN users to use these apps without eating remote bandwidth...
> Sent from my (new!) BlackBerry, which may make me an antiques dealer, but 
> it's reliable as hell for email delivery :-)
> From: "Heaton, Joseph@Wildlife" <[email protected]>
> Sender: [email protected]
> Date: Tue, 29 Oct 2013 16:19:50 +0000
> To: [email protected]<[email protected]>
> ReplyTo: [email protected]
> Subject: RE: [NTSysADM] VPN and high bandwidth applications
> 
> Off the top of my head, it’s going to depend on the end users’ connection 
> bandwidth, and the bandwidth available through the VPN.  I don’t know of any 
> ISP offering bandwidth comparable to your internal network.
>  
> Joe Heaton
> Enterprise Server Support
> CA Department of Fish and Wildlife
> 1807 13th Street, Suite 201
> Sacramento, CA  95811
> Desk:  (916) 323-1284
>  
> From: [email protected] [mailto:[email protected]] 
> On Behalf Of Jon D
> Sent: Tuesday, October 29, 2013 9:10 AM
> To: [email protected]
> Subject: [NTSysADM] VPN and high bandwidth applications
>  
> I'm not an expert with VPNs...
> Is it possible to have end-users use any sort of VPN technology to access 
> high-bandwidth apps?
> Say if an app that is really chatty constantly talking back to a SQL 
> database, or an app that can at times burn 100+megs by itself. 
> And say 50-100 end-users could be hitting the app at any given time.
> 
> Am I missing something, or is this just not what VPNs were designed to do?
> 
>  
>  
> Thanks,
> Jon

Reply via email to