Date: 06/12/08 (IT Professionals) Keywords: no keywords A few weeks back I set up an IIS FTP server for a client and it worked right out of the box. The client started using it to move heavy files to clients and it was quickly adopted by the staff. Today it stopped working. Here are the details: Static NAT on their Cisco 1841 with ACL’s allowing ports 20 & 21 (data & control) to the server. Clients were instructed to use active connections, as IIS is renown for failing on passive. After learning way more that I ever wanted to know about the two connection modes I discovered that in IIS 6 you can hack static ports for passive mode. I tried that (edited the metabase and set up another ACL on the router) and got the same result. The initial issue was that clients could authenticate but not list the contents of the root directory. After ripping out IIS, rebooting, and re-installing IIS that resolved. The problem now is that while you get a directory listing from a “DIR” or an “LS”, when you try to transfer a file in either direction you get the first five or so kb and then the session times out and disconnects. The FiIeZilla client I used auto-retries a few times, downloads another five kb, then the connection times out permanently. Native Windows FTP client just hangs & dies. This thing just worked until this morning. And nothing’s changed. It’s late and this is probably not my most coherent message. But if anybody has run into this sort of thing and can point me in the right direction I’ll buy ya a beer.
Source: http://community.livejournal.com/itprofessionals/76471.html
|