General discussion

Locked

VPN CONFIG

By shibu_06 ·
HOW CAN I CONFIGURE A VPN WORKSTATION IN A WINDOWS2000 SERVER?

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

VPN CONFIG

by kenalmoore In reply to VPN CONFIG

Please download and read the micorsoft whitepaper, this will explain very thoroughly.
www.microsoft.com/ISN/whitepapers/configur_vpn.solution.asp?A=0

You leave this question open!!! Do you have Active Directory, how many member servers?
How many clients will connect and what operating systems will connect?
This is detailed and contains pictures.
It will help.

Collapse -

VPN CONFIG

by kenalmoore In reply to VPN CONFIG
Collapse -

VPN CONFIG

by shibu_06 In reply to VPN CONFIG

The question was auto-closed by TechRepublic

Collapse -

VPN CONFIG

by ins413 In reply to VPN CONFIG

Go to start->settings->network and dialup. Then double click make new connection. Follow the wizard. It's that easy. Have fun.

Collapse -

VPN CONFIG

by ins413 In reply to VPN CONFIG

I am assuming that you want to make a client connection from a W2K server to a vpn server. May have sounded too easy!

Collapse -

VPN CONFIG

by shibu_06 In reply to VPN CONFIG

Poster rated this answer

Collapse -

VPN CONFIG

by estebandelatorre In reply to VPN CONFIG

You have to "ADD windows software", select the "VPN client" and just install it.
You must have at least either a nic card or a dialup (modem) line to the server (across or not the internet)

Collapse -

VPN CONFIG

by shibu_06 In reply to VPN CONFIG

Poster rated this answer

Collapse -

VPN CONFIG

by maxwell edison In reply to VPN CONFIG

Building the VPN

Windows 2000 offers robust tools for building VPNs. Fortunately, the same Microsoft Management Console (MMC) is used on Windows 2000 Professional and all versions of Windows 2000 Server. The heart of the configuration lies in theIPsec policies on the local machine. Several predefined security policies are available when Windows 2000 is installed, but none are activated. Security policies can be applied to all IP traffic or limited by a number of options. For example, you can have all traffic between the desktop and a specific Web server encrypted, while all other traffic passes in the clear. Likewise, you can have traffic encrypted at the peer's request. Although you can have multiple security policies defined, only one security policy can be active at any given time.

Configuring IPsec for each end point can be complex if you don't have a plan or much experience with VPN. As shown in "Flexible IPsec" (below), I configured policies on the end-user computer and the two servers. Obviously, you can't configure or dictate security on public Web servers. A simpler method is to configure the end-user computer to respond to IPsec if requested by the other end. When the end-user computer initiates a connection, the server requiring security responds with a security-negotiation request. If the negotiation is successful, the connections will complete successfully.

See this link for the entire article, illustrations and related links:

http://www.networkcomputing.com/1116/1116ws2.html

(REMOVE SPACES from the pasted URL.)

Maxwell

Collapse -

VPN CONFIG

by shibu_06 In reply to VPN CONFIG

The question was auto-closed by TechRepublic

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums