Indeed, setting up a VPN can play havoc with the routing table, for
example. I was hoping my reply would help to bring such issues to light.
Roops
On Mon, 29 Jul 2019, 16:23 Paul Gilmartin, <
0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 29 Jul 2019 13:51:07 +0100, Rupert Reynolds wrote:
> >
> >It depends on where your VPN endpoint is. If you VPN to the site where MVS
> >is running, then you should have an IP address on that subnet, as well as
> >the public IP address you started with. Any traffic through that tunnel is
> >encrypted as far as the endpoint.
> >
> I have used VPN provided by such a site where the required desktop client
> completely usurped the desktop's IP stack, preventing all the desktop's
> connection to the Internet other than through VPN and the site's firewall
> and proxy. This was to prevent any bridging of the site's intranet to the
> Internet. It was particularly frustrating to users who couldn't use their
> local network printers while connected to VPN.
>
> Of course while they connected to that VPN their public ("home PC") IP
> addresses were inaccessible from the Internet.
>
> -- gil
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
