Single Interface Win2003 VPN

I am having trouble setting up Win2003 VPN using one
interface. With 2 interfaces, everything works fine. I
want to use my current router to do NAT, therefore I would
want get the single interface VPN working. The client is
able to communicate with the VPN server, (gets up to the
point of "Verifying username and password").
The "IPROUTERManager.log" tracing file shows an error
adding route:

Error adding route, Stack bit == 0
ProcessDefaultRouteChanges: Not default route (public ip
of the vpn client)

Any idea how I can get this to work, or is there a
documentation on how to set up a single interface MS2003
VPN?

Please cc responses to e-mail just in case I miss your
response.

Thanks in advance.

Jason

One more piece of information, with single interface set up, I am able to
connect to the VPN server from the LAN using the server's internal IP. Just
not from external host trying to connect to the public address.

Thanks


"Jason" <(E-Mail Removed)> wrote in message
news:1926001c41c32$d4a6f2f0$(E-Mail Removed)...
> I am having trouble setting up Win2003 VPN using one
> interface. With 2 interfaces, everything works fine. I
> want to use my current router to do NAT, therefore I would
> want get the single interface VPN working. The client is
> able to communicate with the VPN server, (gets up to the
> point of "Verifying username and password").
> The "IPROUTERManager.log" tracing file shows an error
> adding route:
>
> Error adding route, Stack bit == 0
> ProcessDefaultRouteChanges: Not default route (public ip
> of the vpn client)
>
> Any idea how I can get this to work, or is there a
> documentation on how to set up a single interface MS2003
> VPN?
>
> Please cc responses to e-mail just in case I miss your
> response.
>
> Thanks in advance.
>
> Jason

Hi Jason,

This sounds like an issue with the Router not allowing Protocol 47 (GRE)
thru to the server. I would confirm that the router is setup to allow this
traffic.

-Matt

[This posting is provided AS IS
with no warranties, and confers
no rights.]

"Jason" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> One more piece of information, with single interface set up, I am able to
> connect to the VPN server from the LAN using the server's internal IP.
Just
> not from external host trying to connect to the public address.
>
> Thanks
>
>
> "Jason" <(E-Mail Removed)> wrote in message
> news:1926001c41c32$d4a6f2f0$(E-Mail Removed)...
> > I am having trouble setting up Win2003 VPN using one
> > interface. With 2 interfaces, everything works fine. I
> > want to use my current router to do NAT, therefore I would
> > want get the single interface VPN working. The client is
> > able to communicate with the VPN server, (gets up to the
> > point of "Verifying username and password").
> > The "IPROUTERManager.log" tracing file shows an error
> > adding route:
> >
> > Error adding route, Stack bit == 0
> > ProcessDefaultRouteChanges: Not default route (public ip
> > of the vpn client)
> >
> > Any idea how I can get this to work, or is there a
> > documentation on how to set up a single interface MS2003
> > VPN?
> >
> > Please cc responses to e-mail just in case I miss your
> > response.
> >
> > Thanks in advance.
> >
> > Jason
>
>

Thanks Matthew. I actually placed a support call to MS (should have waited
for your answer ^_^) It was a firewall issue. We did a packet capture and
found that the Fortigate 400 was modifying the keycall ID. Contacted the
Fortinet and confirmed that there is an issue with PPTP pass through for the
current firmware.

Thanks again.

"Matthew [MSFT]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Jason,
>
> This sounds like an issue with the Router not allowing Protocol 47 (GRE)
> thru to the server. I would confirm that the router is setup to allow
this
> traffic.
>
> -Matt
>
> [This posting is provided AS IS
> with no warranties, and confers
> no rights.]
>
> "Jason" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > One more piece of information, with single interface set up, I am able
to
> > connect to the VPN server from the LAN using the server's internal IP.
> Just
> > not from external host trying to connect to the public address.
> >
> > Thanks
> >
> >
> > "Jason" <(E-Mail Removed)> wrote in message
> > news:1926001c41c32$d4a6f2f0$(E-Mail Removed)...
> > > I am having trouble setting up Win2003 VPN using one
> > > interface. With 2 interfaces, everything works fine. I
> > > want to use my current router to do NAT, therefore I would
> > > want get the single interface VPN working. The client is
> > > able to communicate with the VPN server, (gets up to the
> > > point of "Verifying username and password").
> > > The "IPROUTERManager.log" tracing file shows an error
> > > adding route:
> > >
> > > Error adding route, Stack bit == 0
> > > ProcessDefaultRouteChanges: Not default route (public ip
> > > of the vpn client)
> > >
> > > Any idea how I can get this to work, or is there a
> > > documentation on how to set up a single interface MS2003
> > > VPN?
> > >
> > > Please cc responses to e-mail just in case I miss your
> > > response.
> > >
> > > Thanks in advance.
> > >
> > > Jason
> >
> >
>
>