Bryan is correct that security best practices dictate not using split
tunneling. Were it enabled, whenever a user VPNed into UVM, they would
effectively be creating a bridge between the Internet and the internal
UVM network...not good.
Re: wireless network printers, I can see the challenge, but it's still
going to be tough for the same reason I gave above. If at some point
there becomes a way to mitigate that exposure, we could certainly
entertain it. Until then, it remains a pain in the butt for you, me and
On 10/14/2010 04:26 PM, Bryan Fleming wrote:
> The VPN supports the ability but my understanding is that the ability
> is specifically disabled by the network group due to security concerns.
> I wonder with home network printers becoming more prevalent (a good
> number of the ones in staples tout their wireless abilities these
> days) if that is something that may have to be reevaluated in the
> On 10/14/2010 3:43 PM, Jim Lawson wrote:
>> As far as I know, the VPN (both the old Cisco IPSec kind, and the new
>> AnyConnect client) don't allow "split tunneling", meaning that when you
>> are connected, all your traffic must go to UVM. If you can't print to
>> your home network printer when you're at UVM, you won't be able to print
>> to it while you're connected to the VPN, either.
>> Direct-connected printers (eg USB) still work fine, though.
>> On 10/14/2010 03:39 PM, Helen Read wrote:
>>> I recently set up a home wireless network, now that broadband has
>>> finally arrived in my neighborhood, and uninstalled / reinstalled my
>>> printer as a wireless printer connected to my router. One issue I've
>>> been having is that I cannot print when I'm connected to the VPN. Is
>>> this a bug or a feature? Is there any way around it? I'm connected to
>>> the VPN a fair amount of the time when I'm working at home, so that I
>>> can access mapped network drives (cems and zoo). It's a bit of a
>>> nuisance to have to continually disconnect and reconnect to the VPN
>>> just to print something.