How to download a file over a cisco vpn

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared default configuration. If your network is live, make sure that you understand the potential impact of any command. For more information on document conventions, refer to the Cisco Technical Tips Conventions. Project Gallery. New Community Member Guide. Related support document topics. Recognize Your Peers. Spotlight Award Nomination.

Which of these topics should we host an event in the Community? Hide Results. ISE posture. ISE Demo. Content for Community-Ad. Step 1. Enter a value in seconds for the Idle Timeout ranging from 60 to Step 2.

Enter a value in seconds in the Session Timeout field. The range is from 60 to Enter a value in seconds in the Keep Alive field ranging from 0 to This feature ensures that your router is always connected to the Internet. It will attempt to re-establish the VPN connection if it is dropped. Enter a value in seconds for the duration of the tunnel to be connected in the Lease Duration field.

The range is from to Step 7. Enter the packet size in bytes that can be sent over the network. Enter the relay interval time in the Rekey Interval field. Could be there is a device that's either not generating or not passing Path MTU discovery packets correctly.

There is nothing in the signature related to FTP. Generally when you have FTP issues like this, that start and then stop, it's usually related to active vs. What ftp client are you using? Try changing it from active to passive on your FTP client and see if that helps. In active FTP, the place that you're FTPing to, initiates the data transfer on a different port then the incoming request In passive FTP, YOU initiate the data transfer to the different port and it works because most firewall allow everything outbound to occur.

Edited to add: The signatures are cumulative. While the update doesn't show anything related to FTP, every other update from 95 days ago till now, could have something. I'm not going to research every update to find out for you though ;.

I also have to ask because of your other questions about this If you are, you really don't need to. The fact that it begins the transfer at all indicates that it has no problem establishing the data part of the FTP session, which rules out an ACL blocking the connection in or out. The VPN session itself dropping during the large file transfer does seem to point to an IPS taking action on the connection although you would think it would just terminate the FTP session, but the actions are configurable so who knows?

As far as I know, it can't drop traffic if it is in promiscuous mode since it only receives a copy of the traffic. Since it has been working with no changes on your end thus far other than a signature update , I would ask the customer if they changed anything on their end disallowing large file transfers over a certain size; especially since you said you FTP to other sites with no problem.

If it is just with this one customer, you can bet the problem is on their end. That way you are only dealing with a single pinhole. Connect to it using Tunnelier client. Its very hard to explain but I would try editing the client side protocol VPN type Thats not the way.