Mailinglist Archive: opensuse (4348 mails)
| < Previous | Next > |
RE: [SLE] VPN to Windows 2000 Server Over The Internet - How?
- From: "L. Mark Stone" <LMStone@xxxxxxxxxxx>
- Date: 22 Oct 2002 07:49:54 -0400
- Message-id: <1035287395.1974.13.camel@bronxville>
Rowan,
Thanks for your reply.
I'm OK with the concepts you mentioned, it's the Linux "How-To" that I'm
missing. The home Linux box in question dual boots W2K, and I can VPN in
to the server when booted into W2K just fine.
The published Linux How-Tos regarding VPN's and Masquerading give a
detailed background into the concepts, and that's OK. But what I need is
an implementation guide written for CIOs, not CTOs or network engineers.
I guess I'm truly surprised that such a guide doesn't exist. With the
increase in WAN networking, telecommuting, and Linux devotes interest in
weaning users away from Microsoft, I would think that a good migration
plan would be to enable users to migrate to Linux on their desktops,
while their employers can continue to wring maximum value out of their
$$$ investment in Windows server licenses, Exchange CALs, etc. In other
words, it always seemed to me that it would be easier to migrate the
desktops to Linux first as these get replaced or upgraded more
frequently, and then migrate the servers later, after the investment in
MS licensing has been fully amortized.
So, if I can get this thing working, and if the implementation guide I
mentioned doesn't exist, I'd be happy to document what I've done and
write my own How-To.
Can anybody help?
Thanks!
On Sun, 2001-10-21 at 11:40, Rowan Reid wrote many things:
<snip>
>
--
______________________________________________
Another Message From L. Mark Stone
http://www.lmstone.com
Thanks for your reply.
I'm OK with the concepts you mentioned, it's the Linux "How-To" that I'm
missing. The home Linux box in question dual boots W2K, and I can VPN in
to the server when booted into W2K just fine.
The published Linux How-Tos regarding VPN's and Masquerading give a
detailed background into the concepts, and that's OK. But what I need is
an implementation guide written for CIOs, not CTOs or network engineers.
I guess I'm truly surprised that such a guide doesn't exist. With the
increase in WAN networking, telecommuting, and Linux devotes interest in
weaning users away from Microsoft, I would think that a good migration
plan would be to enable users to migrate to Linux on their desktops,
while their employers can continue to wring maximum value out of their
$$$ investment in Windows server licenses, Exchange CALs, etc. In other
words, it always seemed to me that it would be easier to migrate the
desktops to Linux first as these get replaced or upgraded more
frequently, and then migrate the servers later, after the investment in
MS licensing has been fully amortized.
So, if I can get this thing working, and if the implementation guide I
mentioned doesn't exist, I'd be happy to document what I've done and
write my own How-To.
Can anybody help?
Thanks!
On Sun, 2001-10-21 at 11:40, Rowan Reid wrote many things:
<snip>
>
--
______________________________________________
Another Message From L. Mark Stone
http://www.lmstone.com
| < Previous | Next > |