Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
I have the NAT Rules set-up as suggested - one for TCP and one for
GRE, but I still get Error 721.
I am now somewhat confused about the IP addresses. Both machines (VPN
server and client) had IP addresses in the 192.168.7.x range, with a
SubNet of 255.255.255.0 I have now changed the client to be
192.168.0.1 - Please note that although the 2 PC's are currently
side-by-side for set-up purposes, they are NOT connected via a LAN.
However, my confusion stems from which component do the IP addresses
relate to in a VPN connection? On the XP server side is it the NIC
that the router is connected to, or is it Incoming Connections - they
both have TCP/IP Properties. On the W2K client side, is it the VPN
connection or the resident NIC (which is theoretically unused in this
scenario, as I am dialling-in).
Is it better to specify the IP addresses, or to have them assigned
automatically by DHCP? The VPN server has an option in Incoming
Connections to assign TCP/IP Addresses automatically, and similarly on
the VPN client you can opt to "Obtain an IP address automatically".
I feel that I now need to get this part right before worrying any
further about the router.
Many thanks.
Geoff Pigott
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote in message news:<o4ktp0hbrbvjugsd5q9ink45814h76mj1g@4ax.com>...
> Make two seperate rules.. One like the one you show below, but with
> TCP instead of GRE. Then make a second rule that has IP Protocol 47,
> but leave the Destination and Local Ports blank (or 0 if it won't take
> it).
> ---
> Jeffrey Randow (Windows Networking MVP)
> jeffreyr-support@remotenetworktechnology.com
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
>
http://www.remotenetworktechnology.com
> Windows Network Technology Community -
>
http://www.microsoft.com/windowsserver2003/community/centers/networking/default.mspx
> Windows Home Networking Community -
>
http://www.microsoft.com/windowsxp/expertzone/communities/wireless.mspx
>
> On 18 Nov 2004 04:45:26 -0800, geoff@lybreeze.plus.com (Geoff Pigott)
> wrote:
>
> >I looked in the SetUp guide for the SAR110, but find very little
> >relating to PPPTP Passthrough.
> >So I phoned Solwise Tech.Support who were helpful - they said that the
> >SAR110 does support PPTP Passthrough - you need to set up the GRE
> >protocol on port 1723.
> >However, they feel that the global ip address should be 0.0.0.0,
> >whereas I had entered the static ip address assigned by PlusNet. Even
> >so, regardless of which IP address I enter, I still get "Error 721 -
> >the remote computer is not responding". The connection icon on the XP
> >server's taskbar flashes during the connection attempt, so something
> >is getting through.
> >
> >The GRE NAT Rule in the router is as follows :-
> >Rule flavor RDR
> >Interface name ppp-0
> >Protocol GRE
> >Local address from 192.168.7.2
> >Local address to 192.168.7.2
> >Global address from 0.0.0.0 (or 84.92.64.155)
> >Global address to 0.0.0.0 (or 84.92.64.155)
> >Destination port from 1723
> >Destination port to 1723
> >Local port 1723
> >
> >I will also post this on the Solwise forum, but if I can't solve this
> >problem, can anyone recommend a reasonably priced router that does
> >support PPPTP Passthrough on incoming traffic?
> >
> >I am grateful for your help.
> >Geoff Pigott
> >
> >
> >
> >"Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message news:<O#XyWdKzEHA.3360@TK2MSFTNGP10.phx.gbl>...
> >> I would...
> >>
> >> Look at the section starting on page 63, which deals with NAT, in the Quick Start Guide...
> >>
> >>
http://www.solwise.co.uk/downloads/adsl.htm
> >>
> >> Apparently you can manually add a Protocol number in the Protocol field. See page 72 to start the
> >> process.
> >>
> >> Otherwise you might post to the Solwise support forums...
> >>
> >> http://www.solwiseforum.co.uk/
> >>
> >> Its very possible, as Robin mentioned, the device does not support PPTP VPN at all inbound...
> >>
> >> --
> >> Al Jarvi (MS-MVP Windows Networking)
> >>
> >> Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
> >> The MS-MVP Program -
http://mvp.support.microsoft.com
> >> This posting is provided "AS IS" with no warranties, and confers no rights...
> >>
> >> "Geoff Pigott" <geoff@lybreeze.plus.com> wrote in message
> >> news:12ffcbc4.0411170352.2637b51a@posting.google.com...
> >> > That is a good question, because I have searched in the router's
> >> > configuration for the PPTP Passthrough, to no avail - probably because
> >> > I don't know what ports/protocols/interfaces etc. it might be
> >> > masquerading as!
> >> >
> >> > The router is a Solwise SAR110, which overall I am very pleased with -
> >> > fairly easy to configure, and copious help pages.
> >> >
> >> > Do you know what I should be looking for re PPTP Passthrough?
> >> >
> >> > Thank you for your help.
> >> > Geoff Pigott
> >> >
> >> >
> >> > "Robin Walker" <rdhw@cam.ac.uk> wrote in message news:<cndahf$i2e$1@gemini.csx.cam.ac.uk>...
> >> >> Geoff Pigott <geoff@lybreeze.plus.com> wrote:
> >> >>
> >> >> > This is what I get when I type netstat -an on the XP Pro VPN Host :-
> >> >> >
> >> >> > Does this tell you anything?
> >> >>
> >> >> It tells us that this PC has both PPTP and L2TP VPN servers waiting for
> >> >> incoming connections, but there are no incoming connections.
> >> >>
> >> >> >>> The router has been configured to allow TCP and GRE
> >> >> >>> (protocol 47) on port 1723 - for the local IP address I have used
> >> >> >>> the private IP address of the NIC that is connected to the router,
> >> >>
> >> >> Does your router actually support PPTP pass-through? (for the GRE protocol).
> >> >>
> >> >> What brand and model is the router?
Facebook
Twitter
Instagram