Cisco vpn sever set up

Your Internet gateway <--- primary router

Port #1 on primary router <---> VPN server
Port #2 on primary router <--> Load Balancer
Load Balancer <--> web-server #1
Load Balancer <--> web-server #2
Load Balancer <--> web-server #3

VPN traffic enters your network, through the router to the VPN server, and then VPN-server back through the router to your internal servers. Web-traffic goes through the Load Balancer, for distribution to the collection of servers.

All configuration can be done with the router GUI.
Firewalls: Server Side Having a server side firewall is the typical configuration on many systems. There is only one method for doing this, whether you use telnet or ssh: map a port to be forwarded to the server in the firewall router. It is not advised that you use telnet from the Internet for security reasons; that is usually why you have a firewall.Decide which method of connectivity will be allowed, and determine what port you will use to forward to this service. If there is only one server involved, you can use port 22 for ssh or 23 for telnet and forward them straight through to the server. But if there are several servers involved and they do not have public IP addresses, you will need to pick different ports on the firewall router and let the router forward those ports to the different internal servers.

The devices appear to be in functioning order. However, the connection network requires another computer on which signals are directed towards. The computer server on which network resources are acquirable is unavailable. For example, your devices can provide sevices to another computer if any were avialble. Usually an internet provider would allow acess to several computer with subscription. Consult an internet service provider, examples, at & t, T- mobile, Verizon, boost mobile, or consult any available at your local area. www.at&t.com, www.t-mobile.com, www.verizon.com, Goodluck

open these VPN ports for the client machine ip in the router interface...

TCP&UDP 50

TCP&UDP 51

TCP&UDP 500

TCP&UDP 10000

TCP 1723

UDP 1701

It could be a missing route... are the file server and email server on the same subnet? If they are then it is possibly not a routing issue.

Also it would be worth checking the tunneling settings for the VPNs... if you have specifed either only the fileserver subnet or specifically the file server address, then this could be the reason they can get to nothing else.

Hope that this has helped a little :)

increase your proxy time out or remove the proxy setting from your VPN.

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.

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.

I am not real versed on VPN connections but the only way I was able to connect to my company's Cisco VPN using my Ipaq was with this program. http://www.apani.com/vpnclients.html The whole thing went very easily.