FTP Troubleshooting

This video explains how to set up and debug connecting to your BYU domain through FTP.

Connection to FTP fails

You might see the following error messages: “Connection failed.” “No connection could be made because the target machine actively refused it. Connection failed.”

To get rid of this error, follow these steps:

  • Connect using the native client
  • PC: File Explorer (not Internet Explorer). Type directly in the file path bar.
  • Mac: From Finder press Command + K
  • There are two possible addresses that might work:

Use your default FTP account. The admin root access FTP/SSH account credentials are different than your Net ID and password. They are the ones you received when you first signed up for BYU Domains. Look for the email titled “New Account Information.” It will look something like this:

  • Server Information
  • IP Address: 64.237.63.27
  • FTP Username: xxxxx
  • FTP Password: examplepassword

If the native client works but a downloaded client does not there may be a firewall issue.

  • If you were using Filezilla, try the FTP with Cyberduck to see if you get the same error (https://cyberduck.io/?l=en).
  • Filezilla has settings for Active versus Passive connections in the settings of the program and sometimes switching between them will work.
  • The Active Mode IP Address option in Filezilla may also need to be changed if the program is reading an incorrect IP address.
  • For some reason, switching to Cyberduck seems to immediately fix these types of issues.
  • There may be some browser compatibility issues, so you may need to try various browsers. It seems like Chrome’s support of Java plugins is poor.

Make Simultaneous FTP connections through a Subnet

The max number of FTP connections per IP/Subnet is 50.

Well the max FTP connections on the server is 100.

FTP Firewall Access

If your native FTP client is working but their non-native program is not working, they will need to give the FTP client appropriate access through their computer's firewall. Non-native FTP clients include, but are not limited to, FileZilla, Cyberduck, and CoreFTP.

For MAC OSX:

  1. Click “System Preferences” (gear icon) (or if it's not there, click the apple in the top left corner and click on “System Preferences.”
  2. Click “Security and Privacy”.
  3. Under “Allow apps downloaded from,” a button should appear (because they tried to download something) that says “Open anyway” to allow you to make an exception for your FTP Client. If there is not, then allow applications from all developers:
  • Click the lock icon in the bottom-left corner of the “Security and Privacy” screen.
  • Under “Allow apps downloaded from” select “Anywhere.”
  • Then try opening your FTP program again.

For Windows OS:

  1. Open Windows Firewall by clicking the Start button, and then clicking Control Panel (You may need to use the Windows search feature depending on which version of Windows the you have). In the search box, type Firewall, and then click Windows Firewall.
  2. In the left pane, click (Allow a program or feature) through Windows Firewall.
  3. Click (Change settings). If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
  4. Select the check box next to the program you want to allow, select the network locations you want to allow communication on, and then click (OK).