Re: 1 Way VPN ??

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

From: Sixstringr1981 (Sixstringr1981_at_discussions.microsoft.com)
Date: 11/23/04 

Date: Mon, 22 Nov 2004 20:45:02 -0800

Thanks for the help Robin. I looked for what you were talking about in my
DLink 624 router, all I found was the entry I already enabled ... under
Virtual Servers tab... PPTP - 1723. It's a pretty new router but I didn't
find anything but that. I'll just have to contact DLink and see what they
say about it. Thanks again,

~ Jonathan

"Robin Walker" wrote:

> Sixstringr1981 <Sixstringr1981@discussions.microsoft.com> wrote:
>
> > We both
> > forwarded ports 3389, our personal port number specified for Remote
> > Desktop, UDP 500, and 1723.
>
> TCP 1723 is for PPTP VPNs (OK), but UDP 500 is for IPSec, which you do not
> require. For PPTP, you also need to forward the GRE protocol: some domestic
> routers cannot do this. You need to look for options in the routers which
> say something like "PPTP pass-though" and enable them. IF your routers do
> not support PPTP pass-though, you might need to upgrade your routers.
>
> > the "full version" located in
> > communications folder in the start menu didn't connect
>
> What addresses were you trying to use in the connection dialog?
>
> > Once the VPN was connected
> > however, we were BOTH able to use the "full version" of Remote
> > Desktop to access each other's computer.
>
> Again, what address were you using in the Remote Desktop conenction dialog
> when it worked this time?
>
> > As far as IP ranges should be
> > 192.168.0.x x = 15 and higher.
>
> This is an error. If you are creating VPNs between two LANs, the IP subnet
> ranges MUST NOT be the same in both LANs. You must reconfigure one of your
> routers so that the LAN addresses are in a different range to 192.168.0.xxx
>
> When you have corrected the IP range clash, please post back with a full
> "ipconfig /all" print-out from both PCs taken while you have a VPN connected
> in the one direction that works.
>
> --
> Robin Walker
> rdhw@cam.ac.uk
>
>
>

Relevant Pages

  • Re: Why you have hardware firewalls
    ... >> blocking IP Ranges of countries that you don't need to allow inbound to ... > That can usually be done with many models of routers from various vendors. ...
    (comp.security.firewalls)
  • Re: How hard would it be...
    ... >...to simply install Carnivore on the routers instead of an ISP's ... >various IP ranges, ensnaring all traffic, right? ... Most high-performance routers do not provide any way for end users to ...
    (comp.security.misc)
  • Re: we have private IP address on WAN port, no connection through Router?
    ... The border routers on any private network will not route traffic for these ranges off the private network. ...
    (comp.dcom.modems.cable)
  • Re: A simple port blocking firewall?
    ... ranges so that only 80, 443, and DNS (59, IIRC) go through? ... I can do that on all three of my routers. ... On the Dlink its ridiculously easy - select IP Filters, ...
    (uk.telecom.broadband)
  • Re: Linksys - sucks?
    ... my main experience these days has been using dlink. ... what i've found tho in the case of the dlink di-614+ is that the US firmware ... with respect to wireless. ... > US Robotics - Not too bad, had problems with routers need to be restarted ...
    (microsoft.public.windows.server.sbs)