Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Sneaking up on a solution 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • It may be easier than you think...

    do a: "route print" at a command line and look at what Windows thinks your routing should be... then connect to your vpn and check again.

    I'd bet you still have a route to your local network... it just has a lower precedence.

    Your printing probably uses broadcasts to find the printer... which sends the packets over the VPN.

    You can solve this (usually) by setting up the printer as an LPD or direct IP printing type device. Then, it doesn't use a broadcast to resolve the pri
    • No joy. I really appreciate the suggestion, but (and I just tested this to be sure) the companies I VPN into turn off local LAN access when connected with the VPN client (Cisco, in one case, Lucent "Contivity" in the other).

      I wonder if I could just run a regex looking for Ctrl-Z (the DOS/Windows EOF marker) from the pipe.

      Frustrating.

      • That's a bummer... but, I wonder where in the stack they grab the packets...

        If you can print to a serial or parallel port... perhaps you could use a "net" command to map LPT1: to your network printer...

        I don't have a WinBox handy, but I think it would be something like this:

        net use lpt1: \\systemname\printsharename\

        Then you print to lpt1: and the OS sends it to the mapped printer.

        Thier coding may have been sloppy enough that this would fool the VPN software...

        I guess, worst case, I'd just print to a f
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.