|
Home > Archive > VPN > September 2004 > VPN at home
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Telenet news 2004-09-15, 8:46 pm |
| Hi,
I have a WinXP Prof server at home with 2 NICs.
1 NIC receives an ISP IP address via a cable modem (internet connection)
The other one has a static IP for my private network (192.168.0.1)
I have DYNDNS sw running on te server.
How can I setup this server as a VPN server so that I can access shares on
my home server from anywhere via the internet?
many thanks,
Wim
| |
| Geoffrey Welsh 2004-09-15, 8:46 pm |
| Telenet news wrote:
> I have a WinXP Prof server at home with 2 NICs.
> 1 NIC receives an ISP IP address via a cable modem (internet
> connection) The other one has a static IP for my private network
> (192.168.0.1)
> I have DYNDNS sw running on te server.
>
> How can I setup this server as a VPN server so that I can access
> shares on my home server from anywhere via the internet?
I would guess that you can't with XP, at least not using Microsoft VPN
components, because Microsoft meant it as a desktop OS and not a network
server. With 2003, it would be as easy as firing up the Configure Your
Server Wizard and adding the "Remote Access Server / VPN Server" role.
You may be able to install third-party VPN tools such as OpenVPN
(http://openvpn.sourceforge.net/; DISCLAIMER: I've never used this product
and am not specifically recommending it!) but you may need to install
software on the client as well as the server.
Sadly, the best advantage of using Microsoft's VPN server is that every OS
since Windows 95 has the client built in, at least as an option.
--
Geoffrey Welsh <Geoffrey [dot] Welsh [at] bigfoot [dot] com>
[This space for rent]
| |
|
| Actually, that's not true. You CAN use Windows client
Operating systems, from Windows 2000 and up, as a
minimal VPN server.
Just go to Network and Dialup Connections, and
double-click on Make New Connection. Then, choose
"Accept Incoming Connections" and go on from there
to choose your connection type. Make sure when you
set up the client at the other end, that your settings
match.
I''ve done this dozens of times, and have found it
to work quite well. I believe you're limited to 2 connections
at a time, but I can't recall exactly.
Dave
On Wed, 7 Jul 2004 17:07:53 -0400, "Geoffrey Welsh"
<reply@newsgroup.please> wrote:
>Telenet news wrote:
>
>I would guess that you can't with XP, at least not using Microsoft VPN
>components, because Microsoft meant it as a desktop OS and not a network
>server. With 2003, it would be as easy as firing up the Configure Your
>Server Wizard and adding the "Remote Access Server / VPN Server" role.
>
>You may be able to install third-party VPN tools such as OpenVPN
>(http://openvpn.sourceforge.net/; DISCLAIMER: I've never used this product
>and am not specifically recommending it!) but you may need to install
>software on the client as well as the server.
>
>Sadly, the best advantage of using Microsoft's VPN server is that every OS
>since Windows 95 has the client built in, at least as an option.
| |
| Geoffrey Welsh 2004-09-15, 8:46 pm |
| Dave wrote:
> Actually, that's not true. You CAN use Windows client
> Operating systems, from Windows 2000 and up, as a
> minimal VPN server.
>
> Just go to Network and Dialup Connections, and
> double-click on Make New Connection. Then, choose
> "Accept Incoming Connections" and go on from there
> to choose your connection type. Make sure when you
> set up the client at the other end, that your settings
> match.
Ah, I just didn't know where to look. That's good to know. Thanks.
--
Geoffrey Welsh <Geoffrey [dot] Welsh [at] bigfoot [dot] com>
[This space for rent]
| |
| T. Sean Weintz 2004-09-15, 8:46 pm |
| Dave wrote:
> Actually, that's not true. You CAN use Windows client
> Operating systems, from Windows 2000 and up, as a
> minimal VPN server.
Actually, that is not QUITE true either. I know you can do it with NT
3.51 and NT 4.0 as well, probabaly ALL versions of NT workstation.
--
T. Sean Weintz - T. Sean Weintz - T. Sean Weintz - T. Sean Weintz
May be copied freely without the express permission of T. Sean Weintz.
T. Sean Weintz could care less. T. Sean Weintz does reserve all rights.
T. Sean Weintz - T. Sean Weintz - T. Sean Weintz - T. Sean Weintz
| |
| Greet Van Reeth 2004-09-15, 8:47 pm |
| cut
Do you allways need to use a router to make a VPN-connection, can you do it
without one?
| |
| INVALID@google.com 2004-09-15, 8:47 pm |
| "Greet Van Reeth" <nospam:gret@groene-links.be> wrote:
>Do you allways need to use a router to make a VPN-connection, can you do it
>without one?
>
Geez. This is such a vague question. Let me give it a try.
Routers dont play VPN role gererally. The reason why you have such mixed
thinking is because you see lots of consumer grade boxes boasting
routing and vpn roles for marketing purpose. Most consumer grade routers
only support IPsec pass-through (udp 500 and protocol 50) and extremely
limited sessions (less than 5~10 concurrent) and limited throughput.
To make a VPN connection, you only need two or more nodes running the
same VPN, e.g., IPsec, protocols.
------------------------------------------------
The leader in Green VPN solutions
http://strongsolutions.addr.com/
------------------------------------------------
|
|
|
|
|