Discussion Locked

VPN Issue

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
okay, clients outside network get an Error 721 when trying to connect oto Windows 2000 Adv Server. Server has Remote Access installed, with VPN enabled. Two NIC cards...Linksys router in front of it. Port forwarding for 1723 and 47 on to the IP address of one of the static nic cards...and pptp passthrough enabled. We can connect internally just fine, of course. Ideas?? Need fixed oh so fast.

8 replies

by ann777

The article refers to a firewall (specifically Checkpoint'S fIREwALL 1 version 3 or 4), but your LinkSys acts as a firewall in your situation. Call LinkSys for confirmation...

by shmaltz

Anna adds in his comment that you should call Lynksys. You don't have to since most Lynksys Routers will allow you to do port forwarding.
First for trouble shooting:
To make sure that the problem is the firewall, type the following command at a computer that you get the error 721 (open a command prompt by typing cmd in the run box on win2k machines, and command on win9x machines):
telnet serveripaddress 1723
(Where serveripaddress is the public IP address to the VPN Server)
if you get a blank screen the problem is NOT with the router/firewall, if you get can't connect then the problem is with the router/fireall.
On most routers you can use port forwarding which means that you can open your firewalls IP address to receive packets for a specific TCP port number (in your case port # 1723) and forward it to any internal IP address. In your case this is what you have to do, you have to configure your firewall to allow TCP Port 1723 to your VPN Server, and make sure that it gets forwarded to your Server, then you use the IP address of the firewall to connect from clients.
BTW, it is not TCP Port # 47 that you have to open, it is Protocol 47 and TCP port 1723 (TCP is Protocol # 6). In most cheap firewalls you can't configure the protocols, which leaves you just to open TCP port 1723.

This discussion is closed to new replies.