Filezilla timeout after 20 seconds of inactivity

After changing my dlink router with a Netgear d6000 I'm no longer able to connect to ftps via filezilla. The settings for ftp connections remained the same but after connecting to the server, Filezilla timeouts after 20 seconds of reading folders(nothing appears in the directory tree). Same problems with different ftps. I don't know if it's router related.

Edit: It's not a timeout issue. Changing the timeout value doesn't change the problem. It blocks when reading folders.

1

12 Answers

1. Open Site manager
2. Click on “New site” button
3. You need to change the Encryption to “Only use plain FTP (insecure)” and Logon type to Normal
4. Enter host address, user name and password and click “Connect”
5. Proceed as per the messages, you may need to enter the passwords again , enter it.

Click here to see the details with screenshots

5

In my case

1. Click Edit on Menu
2. Click Settings
3. Set Time Out to '0'

That's it. It worked in my case. Tried all the above mentioned methods but it wont make any change in my problem.

By just disabling the time out it worked.

0

1. Open FileZilla client application on your desktop. A new window will open for FileZilla.

2. Click Edit on menu bar and select Settings option.

3. Click Settings and a new small Settings window will open. In the left side of the Settings window there is a subsection called Select page, select the top option called Connection (by default it is selected when you open Settings window if it is not then select it manually). When you click on the connection link you will get an option to set timeout on the right side. In that Timeout section you will get an option to set timeout value from 0-599 seconds. Set this according to your need or you can disable this Timeout settings by settings its value to 0.

1

I had the same problem when I switched from a D-Link router to a Asus RT-AC68U.

My problems where solved by disabling the NAT Acceleration. This description is for a Asus router but look for NAT Acceleration/Hardware acceleration or something like that, if you have another router.

1. Login to the router
2. In the left menu, under Advanced Settings, click the LAN button.
3. Then click the Switch Control tab.
4. Set NAT Acceleration to Disable.

2

This is how I fixed it:

Advanced -> NAT -> RIP CONFIG LIST -> Enable FTP

1. Open Site manager
2. Click on “New site” button
3. You need to change the Encryption to “Only use plain FTP (insecure)” and Logon type to Normal
4. Enter host address(using ip is better ), user name and password and click “Connect”
5. Open transfer settings tab
6. Change transfer mode from default to active
7. Proceed as per the messages, you may need to enter the passwords again , enter it.

2

I know this is an old question, but thought I would post my solution for others who come across this post.

1. Login to your Netgear D6000 router
2. Click on the Advanced tab
3. Click on Setup from the left hand menu
4. Click on WAN Setup
5. Tick the check box to Disable Port Scan and DoS Protection
6. Click on Apply

In my case, I had some commands in my .bashrc file which printed some general information (e.g. gcc --version) to the console whenever I logged in. These kind of outputs confused the FileZilla. I suppressed the commands and FileZilla worked immediately.

I was having the same problem, but I solved it by using IP adress in the host field

2

I managed to solve this problem by setting up Port Mapping and Port Trigger on the Router Modem :

Port Mapping and Port Trigger

Yes, its bcos of NAT ALG on my Skyworth Router. I disabled it and it fixed the issue instantly.

It was enabled by default, I unchecked it. Now Filezilla is working perfect. You guys might find some similar options, so this is working solution. Thanks to fwilhelmsson for the idea.

I had the same issue when changing to a new AX5400 Wi-Fi 6 Router. I setup the NAT port forwarding like I had with my previous router and made sure my FTP server nic had a static IP assigned that was the same as what I used in port forwarding settings (192.168.1.161) but it would not allow remote connections. I was finally able to get a successful connection when I went to "Advanced" tab, selected "network", and finally clicked on "Routing". From there I added a new route to my Static Routing table. I set the local IP of my FTP (192.168.1.161) server as the "Network Destination", Local network IP (255.255.255.0) as "Subnet Mask", my routers local IP (192.168.1.1) as "Default Gateway", set LAN as "Interface", and used FTP as my "Description". After adding this static routing I tested and was finally able to connect.

1

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy