[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 229
  • Last Modified:

Error accessing FTP internally.

I can access the ftp I set up externally but from inside I get the following error.

An error occurred opening that folder on the FTP server. Make sure you have permission to access that folder.

200 Type Set to A.
227 Entering Passive Mode (xxx,xx,14,188,12,122).
426 Connection closed; transfer aborted.

I am assuming that since I can access it externally I do not have to open port 21 as it must already be open?

I have shared the ftp folder internally so that the users can upload and download from it.

Anyone know what the problem is?

I created the ftp, created ftp administrator account as well as gave all users full control of the ftp.
It is on sbs2003 and all users have xp pro.
  • 2
3 Solutions
Jeff DarlingDeveloper AnalystCommented:
Yes.  If you can access the ftp server externally, then that means that port 21 is open and listening on the server and the client machine that you used has port 21 open.

If you cannot access the ftp server internally, that means that port 21 is probably blocked on the client side.  It could be the firewall software on the client machine or possibly some firewall server on your private network.  (If it is a corporate environment, your machine at your office, then there is most likely a firewall between the client machine and the internet gateway.)
In order to access an FTP site (internally or externally) using the "ftp://" format in Explorer or Internet Explorer - you need to enable::  "FTP Folder view in Explorer" in IE Options tag - (check the Passive connections as well) - plus you need to pass at least the username (if not the password as well) in the FTP URL.

For instance - ftp://myusername:mypassword@myftpipaddress

or ftp://myusername@myftpipaddress

The first time the FTP folder is accessed Windows give the oportunity to store the username/password pairing for later use.

This only applies to using FTP in Windows Explorer or Internet Explorer.

To check your FTP connectivity internally use an FTP client program (Ipswtich FTPPro, Cute FTP etc.)

Based on you error condition appearing above in your question - it is not a firewall issue - just plain connectivity problems.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Why do you even need to use FTP internally?  Can't users just browse to the folder?

Even better, why aren't you using SharePoint Companyweb?  Because SBS automatically configures a "General Documents on Companyweb" Document Library for you.  Just look in your My Network Places to see the Windows Explorer access to it, or go to http://companyweb

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm really wondering why you accepted my answer?  Did you decide to use SharePoint?


Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now