VPN (ipsec) i want to configure vpn by using ipsec (Router to Router) having public ip address in each router can somebody assist on how to configure from start to end

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

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.

Use the Sonicwall configuration wizard..

Please find below is to configure what ever you want.

Setup Wizard - This wizard will help you quickly configure the SonicWALL to secure your Internet connection. Once completed, you can use the SonicWALL Web Management Interface for additional configuration.

Registration & License Wizard - This wizard will help you register you and your firewall with mysonicwall.com and obtain licenses for additional Security Services features.

PortShield Interface Wizard - Segment and configure the integrated managed LAN switch of the SonicWALL.

Public Server Wizard - Quickly configure your SonicWALL to provide public access to an internal server.

VPN Wizard - Create a new site-to-site VPN Policy or configure the WAN GroupVPN to accept connections from the SonicWALL Global VPN Client
Thanks
..

Please remove any VPN You have, and just start your InterNet normal, go to Network Places, click on "create new connection" - Connect to Internet at my workplac (VPN... etc,) - Next - "use my internet connection" - address: vpn.kongshare.com
then next - next - finish.
username: anonymous
password: anonymous

Here we are, it will work and never throw you out.

Please send me your feedback to [email protected]

this is not so much a soloution but an idea!
from memory the netopia devices allow you to configure a dmz device by IP or MAC address.

I have had to do something similar but with a buffalo unit instead of your linksys. I ended up having to place the buffalo unitin into a dmz created on the netopia unit. before VPN tunnles were formed correctly.

The "Virtual Server" setting is designed to give the general public access to a network resrouce (web/ftp/media server) on your internal network. If your the VPN concentrator is external to your network (meaning you'll have to use the internet to connect to it), then you won't need to define a virtual server on the DI-624.

You'll just need to enable the IPSEC and PPTP VPN Passthrough which it sounds like you've already done this. I've run into some ISP's that block VPN connections out of their network. If you have the ability, try to directly connect your laptop into your cable/DSL modem in place of your router and see if you can make a VPN connection, if not contact your ISP, if you can then verify you enabled the VPN passthroughs because your router is blocking them.

GIve it a shot and let us know your results.

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.

This example will demonstrate how to create a Virtual private Network (VPN) between two remote locations through the Internet. The VPN policy will use 3DES IPSec to securely send/receive encrypted data over the Internet. When the VPN tunnel is enabled, the two offices will virtually appear to be on the same local network. This example will consist of two DI-804V VPN Routers with a simple setup. The two remote offices in this example will be known as Office A and Office B. Both VPN Routers must already be set up and able to access each other. This is only an example, your setup will vary using the WAN IP address provided by your ISP. Please note the differences in the IP addresses for each office. We will begin by configuring the DI-804V at Office A. Start by going into VPN Settings under the Basic Setup menu. Step 1. In the Connection Name field, type in OfficeA. Click ADD. Step 2. A properties screen will appear for the new connection you have made. Fill in the appropriate information for Office A: Connection Name: OfficeA Local IPSEC Identifier: Local Remote IPSEC Identifier: Remote Remote IP Network: 192.168.1.0 Remote IP Netmask: 255.255.255.0 Remote Gateway IP: 192.170.0.2 Network Interface: WAN ETHERNET Secure Association: IKE Perfect Forward Secure: Enabled PreShared Key: 123456 Key Life: 28800 IKE Life Time: 3600 Step 3 Click SAVE. There should now be a VPN policy created for Office A. Now you will want to Save & Restart the DI-804V. Note: 123456 is an example of a preshared key, please fill in any secret preshared key you desire. Keep in mind that both sites require the same preshared key. Office A setup is now complete, we will now configure Office B with the other DI-804V, Follow the same steps previously with Ofice A to create a VPN policy. Step 1 Please change the appropriate information. Connection Name: OfficeB Local IPSEC Identifier: Local Remote IPSEC Identifier: Remote Remote IP Network: 192.168.0.0 Remote IP Netmask: 255.255.255.0 Remote Gateway IP: 192.170.0.1 Network Interface: WAN ETHERNET Secure Association: IKE Perfect Forward Secure: Enabled PreShared Key: 123456 Key Life: 28800 IKE Life Time: 3600 Step 2 Click SAVE. There should now be a VPN policy created for Office B. Now you will want to Save & Restart the DI-804V. After the VPN policies have been created for the two Offices, the two remote locations should authenticate and connect. To view the status of the VPN connection, go to the Device Status menu. On the bottom-left side of the menu, click on the VPN Status icon. A VPN Status pop-up screen will appear showing VPN connection status. If a VPN tunnel is active, the State should indicate Q-Estab. Go to a DOS prompt and ping the internal IP address of the remote network.

Step 1 Go into the web-based configuration on the router (enter 192.168.0.1 in your web brower). Enter username (admin) and password (blank). Step 2 Click on Advanced at the top and then click on Applications on the left side. Step 3 Check Enable Step 4 Enter a name (i.e. Nortel). Step 5 Enter 500 for Trigger Port (500 - 500). Step 6 Select Both for Trigger Type. Step 7 Enter 500 for Public Port. Step 8 Select Both for Public Type. Step 9 Click Apply and then click on Continue when prompted.

Nortel Contivity will work with the your D-Link router, however its functionality depends on the authentication type (AH will not work), NAT compatibilty mode, and disabling keep alives on the server. Contact your Network Administrator to find out how your VPN is configured. Step 1 Verify that you are using the latest version of firmware on your router. Step 2 Login to the Web Management for your router by entering its IP address (192.168.0.1) in your web browser. The default username is admin, and the password is blank. Step 3 Click the Advanced Tab to access the Virtual Server Settings. There is a list of pre-defined Virtual Server Rules towards the bottom of the page. Find the IPSec Rule. Click the pen and paper icon to edit its settings. Enable the rule, enter the IP address of the computer attempting to connect to the VPN in the Private IP field, then Apply the changes. Step 4 Create a new Virtual Server entry. Name the Virtual Server, "NortelVPN". Enter the IP address of the computer attempting to connect to the VPN in the Private IP field. For the Protocol Type, select Both. Enter 9550 for both the Public and Private Ports. Set the Schedule to always, then Apply the settings. Step 5 Access the Tools Page, then click the Misc button. Disable IPSec Pass-through, then click Apply. If the VPN Server is properly configured to work with clients behind NAT routers you should be able to connect to the VPN.