Quantcast
Channel: Adobe Community: Message List
Viewing all articles
Browse latest Browse all 87158

Re: Waiting for server

$
0
0

I have resolved my - Dreamweaver FTP problems with long waits and time outs.  My DW FTP problem is related to my Verizon FIOS router from Action Tec  MI424WR-GEN3I  - Action Tec blocks ports by default in the router (they did not say which ones).

I used port forwarding in the router to specify that my workstations IP had permission to use FTP Port 21 and ports 60,000 - 65000.  Ports 60k-65k are defined on my web-server as the FTP passive ports).  FTP uses  command port 21 to communicate and other ports to transmit files.  Since multiple files transmit simultaneously multiple data ports are used.  If some data ports are block, which appears to be my case, when the server selects a random port and it happens to be blocked - the results are waiting on server and then a disconnect.   What is unclear is why Filezilla worked and DW timeout on the same protocols.


As I read more about the latency and port problems, I found some gamers with the same complaints and one mentioned the Action Tec.  Action Tech said the manufacture their Verizon routers to Verizon's specs and some ports are blocked. It looks like Verizon throttles FTP via the Action Tech router. 


I also changed the PC's IP from DHCP to a static IP as the router provides permissions by device IP address.

The PUTS & GETS are running very fast, no timeouts. Switching from one web to another are almost instant - this would hang when the FTP failed but did not disconnect on the previous site.


I also use Filezilla (passive is the default) Filezilla had no issues with FTP - DW under the same protocols. 

The last entry in the image is the port forward settings I used.

 

If you have the timeouts and long waits -and do not have Verizon - check the modem / router for port blocks.  ActionTec-Router.png


Viewing all articles
Browse latest Browse all 87158

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>