VPN error 721

Ok, this is weird.

I can VPN into work - no problem

At home, running Win 2003 Ent with RAS.
When vpn from work to home I get 721 error.
Ran pptpclnt.exe on workstation at work and pptpsvr.exe on server at home
(via remote desktop) and shows that GRE is getting through just fine. . .

I go to the server at work (Win 2003 basic server) that is running the RAS
services that I can VPN into, and I can successfully VPN to my home.

VPN from my work to home on any other machine fails.
VPN from a local machine at home, ie inside my router works too.

Any ideas???

PPTP also uses TCP port 1723. Is that open to your home VPN server?
Regards Wendel.

"joe mamma" wrote:

> Ok, this is weird.
>
> I can VPN into work - no problem
>
> At home, running Win 2003 Ent with RAS.
> When vpn from work to home I get 721 error.
> Ran pptpclnt.exe on workstation at work and pptpsvr.exe on server at home
> (via remote desktop) and shows that GRE is getting through just fine. . .
>
> I go to the server at work (Win 2003 basic server) that is running the RAS
> services that I can VPN into, and I can successfully VPN to my home.
>
> VPN from my work to home on any other machine fails.
> VPN from a local machine at home, ie inside my router works too.
>
> Any ideas???

yes it is. . . as I said I can vpn in from the machine that runs ras form the
office but not from any other machine.


again, I can vpn from home to work on the work ras service.
from work I can vpn to the home ras service on the machine that hosts the
work ras service. something has to be messed up on the router settings. that
it wont let out bound except from the ip address associated with the ras
machine.



"Wendel Hamilton" wrote:

> PPTP also uses TCP port 1723. Is that open to your home VPN server?
> Regards Wendel.
>
> "joe mamma" wrote:
>
> > Ok, this is weird.
> >
> > I can VPN into work - no problem
> >
> > At home, running Win 2003 Ent with RAS.
> > When vpn from work to home I get 721 error.
> > Ran pptpclnt.exe on workstation at work and pptpsvr.exe on server at home
> > (via remote desktop) and shows that GRE is getting through just fine. . .
> >
> > I go to the server at work (Win 2003 basic server) that is running the RAS
> > services that I can VPN into, and I can successfully VPN to my home.
> >
> > VPN from my work to home on any other machine fails.
> > VPN from a local machine at home, ie inside my router works too.
> >
> > Any ideas???

Joe,
Sorry misunderstood.
So how does the server connect to the internet?
How does it differ from the workstations?
Can your workstations at work VPN to the local VPN server?
Does your home network use the same IP range as your work network?

"joe mamma" wrote:

> yes it is. . . as I said I can vpn in from the machine that runs ras form the
> office but not from any other machine.
>
>
> again, I can vpn from home to work on the work ras service.
> from work I can vpn to the home ras service on the machine that hosts the
> work ras service. something has to be messed up on the router settings. that
> it wont let out bound except from the ip address associated with the ras
> machine.
>
>
>
> "Wendel Hamilton" wrote:
>
> > PPTP also uses TCP port 1723. Is that open to your home VPN server?
> > Regards Wendel.
> >
> > "joe mamma" wrote:
> >
> > > Ok, this is weird.
> > >
> > > I can VPN into work - no problem
> > >
> > > At home, running Win 2003 Ent with RAS.
> > > When vpn from work to home I get 721 error.
> > > Ran pptpclnt.exe on workstation at work and pptpsvr.exe on server at home
> > > (via remote desktop) and shows that GRE is getting through just fine. . .
> > >
> > > I go to the server at work (Win 2003 basic server) that is running the RAS
> > > services that I can VPN into, and I can successfully VPN to my home.
> > >
> > > VPN from my work to home on any other machine fails.
> > > VPN from a local machine at home, ie inside my router works too.
> > >
> > > Any ideas???

Thanks for the help. . .

Your questions led me to triple check my config. . .

As it turned out, the server's RAS nic was registered in DNS. I dont think
this was a problem, but it shouldnt have been there.

What did seem to be a problem. . .

The incompetent sysop we fired earlier this month had opened up ports/static
routes on the router for e-mule.

I wish I could post his name just to protect the rest of the world!