Re: VPN Basic Question

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Well,

That was way, way too simple.

Basically, you need to make sure that your router (if applicable) has port
number 1723 open and natted to your VPN server on the inside of your
network.

Then, configure routing and remote access on your server to accept
connections. Make sure you enable it, configuret it. . . oh just play with
it. Now try to connect from a client to your outside IP address.

Pooft, thats it.

Now, turn OFF your routing and remote access server and read up on locking
down the same with some type of encryption on both sides.

The basic is accomplished, that is to say, you can connect from a VPN client
to the VPN server accross the web. Now, just figure out how to change the
default port number for security if you can, lock down the security of the
tunnels and figure out the whole point to point (network to network)
connectivity issue. Remember, if you have two domains you are going to need
to set up trusts, etc. Needless to say, there may very well be some issues
in terms of security for the actual account that you are going to use to
connect the two networks, but now that you have the basics down, you should
be able to play with the rest.

Responding to yourself is fun. . .eh?

Doc Wally

"Doc Wally" <this@xxxxxxxxxxxxxx> wrote in message
news:jK2Qf.16746$d87.12211@xxxxxxxxxxx
Dear Colleagues,

I have a rather simple question and am basically looking for pointers
towards guides and tips so that I can set things up accordingly.

To begin with, my last experiences with VPNs were back in the Windows NT
days so please forgive my rather rusty memory.

The basic issue is this:

Both of my networks are behind routers. Lets just say for arguments sake
that they both have static IP addresses but that the ISP blocks certain
ports.

What I want to be able to do is to set up VPN on a server inside of each
network, change the default port for VPN and then NAT that port to the
back of the particular server.

I have looked at some papers via Microsoft but have gotten lost in the
whole encryption part which I realize is important, but which I would
rather deal with after I have the basics nailed down. . . that is to say,
to get the thing working to begin with!

Thanks for all the advice in advance.

Doc Wally



.



Relevant Pages

  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... > and make sure this software does not interfere with SBS Server. ... > clients, please disable it and try again. ... Create a local printer and redirect the port to the network server. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)