DLink DI-624s - can't get Cisco VPN Client to connect.

Cisco VPN
Upgrade your router to the latest firmware. You can download firmware at http://www.dlink.com.au/tech/ .
Disable all Firewall Software (ZoneAlarm, Windows XP Firewall, etc.).
Configuring PC running VPN Client Software:
Step 1 Disable all Firewall Software (ZoneAlarm, Windows XP Firewall, etc.).
Step 2 Change IP Address to be outside of the routers DHCP Pool (i.e. 192.168.0.99). By default the DHCP pool is 192.168.0.100 - 192.168.0.199.
Step 3 Configure Cisco VPN Client - Connection Properties.
Step 4 Check Enable Transparent Tunneling.
Step 5 Allow IPSec over UDP ( NAT/PAT).
Configuring Router using the Web-based configuration:
Step 1 Open the Web Configuration Page by entering 192.168.0.1 into your web browser. Enter username (admin) and your password (blank by default).
Step 2 Check the Status tab and make sure that you are running the latest version of firmware. If not, upgrade firmware before proceeding.
Step 3 Click on the Miscellaneous button on the Tools tab. Enable both PPTP and IPSec.
Step 4 Click Apply.
Step 5 Click on the Virtual Servers button on the Advanced tab.
Step 6 Enable IPSec from the list and configure as follows:
Private IP: IP Address of the PC running Cisco VPN Client
Protocol: UDP
Private Port: 500
Public Port: 500
Schedule: Always.
Step 7 Click Apply and then Continue.
Step 8 Enable PPTP from the list and configure as follows:
Private IP: IP Address of the PC running Cisco VPN Client
Protocol: TCP
Private Port: 1723
Public Port: 1723
Schedule: Always.
Step 9 Click Apply and then Continue.


http://www.dlink.com.au/tech/default.asp?model=DI-524UP

Peer to peer tunneling protocal is what pptp is if its connecting a limited connectivity that means some of the ports are stull being blocked thus needing for you to use your machine in a demilierized zone so this will open all avilable ports to your VPN software. Also keep in mind not all ISP's will support PPTP so you may have to use a softvpn software. Thanks i hope this helps

Btw, I’m available to help over the phone in case u need at https://www.6ya.com/expert/edwy_1a56970cf1ea4620

you need to create an IPSec tunnel between the router and windows server 2003 (run secpol.msc). From the dlink router, you need to set the IP address of the VoIP gateway as part of the LAN that is included on the VPN tunnel. Since it is the server 2003 that has a static IP, you need to initiate the connection from the Dlink router.

Here's a real simple problem to your remote access problems.
Go to: http://www.logmein.com
Sign up for a free acct, download/install their free software on your Server.
Now go over to your laptop, login to your new logmein acct.
In the next page, you'll see your Server listed. Click on it - follow instructions to connect.
This will tunnel through whatever stuff you have on your network!
Trust me - esp. in your scenario, this is *by far* the *simplest remote connect you'll ever perform! And it just .... works! Everytime.

gurutim

I am guessing this VPN is something work related and not a VPN you setup yourself?? If that is the case your company's VPN access will not allow you to pass from there network back to yours which is why you are unable to print to your local home printer when connected to VPN. You might could run it by your IT staff and see if they will allow connection and help you set it up. If not then simply email the docs to yourself and then print them out after you are finished using VPN connection.

Hope this Helps
TankMurdock

Update your firmware to the latest. I had the same issue and the issue is gone after the upgrade.

I'll need to know what router you're using, make and model, for more specific help, but sometimes there is an option for IPSec passthrough. For example, on my Linksys Wireless Router WRT54G, there is a set of buttons under Security/VPN that are entitled IPSec Passthrough, PPTP Passthrough, and L2TP Passthrough. Since I don't know what router you're using, I can't tell you wether or not your router supports such functions or not, but if it does, you need to enable them.

You'll want to enable the VPN transparency. In the router's administrative web interface, click the Security Tab, then the VPN Passthrough sub-tab. Cisco VPN's usually use IPSEC, so enable the IPSEC Pass-through and click "Save Settings". If this doesn't work enable the PPTP Pass-through as well and give that a shot.

login to the router and check these things
IPSec Passthrough: Enable Disable               PPTP Passthrough: Enable Disable               L2TP Passthrough: Enable Disable

the following is from a nice guide i found on the net, see if it works for you: First thing to check is whether your router has any settings for PPTP or IPsec "pass through". These are commonly found in Linksys routers but you may have to hunt around for them on other makes. All you need to do is enable the setting for the VPN protocol that you're using, reboot your router and, if you're lucky, the VPN connection will come right up. Note: Not all routers have these enables and the lack of them doesn't necessarily mean that you can't get VPN working. Open up that Firewall Still no connection? The next step is to try opening some ports in your router's firewall to get your VPN connection made. In each case, you'll need to open the specific ports (and protocol) to the IP address of the computer that you're running the VPN client on. NOTE that port mappings work with only one computer at a time. If you have multiple VPN clients that you need to connect, your router will have to support the VPN protocol that you're using without requiring ports opened. If you're using Microsoft's PPTP protocol, TCP port 1723 is the port you'll need to forward to allow PPTP control traffic to pass. Figure 2 shows the Forwarding screen on a Linksys BEFSR41 set to forward this port to a client with IP address 192.168.5.100. PPTP also needs IP protocol 47 (Generic Routing Encapsulation) for the VPN data traffic itself, but note that this is a required protocol, not a port. The ability to handle this protocol must be built into the router's NAT "engine"?which is true of most present-generation routers. IPsec-based VPN's need UDP port 500 opened for ISAKMP key negotiations, IP protocol 51 for Authentication Header traffic (not always used), and IP protocol 50 for the "encapsulated data itself. Again, the only "forwardable" item here is UDP port 500, which is also shown programmed in Figure 2 to the same LAN client machine?protocols 50 and 51 must be built into your router. Tip: Not all routers are created equal! Some allow only one VPN tunnel to be opened and used by a single client. Others support multiple tunnels, but with one client per tunnel. Unfortunately, most vendors don't make the VPN pass through capabilities of their products clear in their documentation, nor do they have support staff properly trained to provide this information either. In most cases, your only option is to try a router in your specific application, and make sure you can return it and get your money back if you can't get it working. Still not Working? Getting many IPsec-based VPN setups working can be a black art due to the wide variation in techniques used by various vendors. Although IPsec products have become more uniform as the technology matures, your company may use older, more proprietary products that may not be configured with NAT in mind, or require additional ports to be opened in your firewall.