The next possible issue is a client-side firewall. To be able to connect, outgoing TCP connections to the bol server need to be allowed on port 21, as well as 60000 through 60200.

Below are some steps you can follow to see if the firewall is the issue. Bol cannot help with this configuration. You will have to do this yourself or talk to your IT department/contact. 

Checking your firewall

To verify that the firewall allows outgoing connections, you can try one of the following tests, depending on the operating system: 

Windows

• Open a Command Prompt
• Execute the following: 
  • telnet supplier.unftp.bol.com 21
• If the firewall has been configured correctly, you should see something similar to:
  • Trying 79.170.100.0…·
  • Connected to supplier.unftp.bol.com.
  • Escape character is ‘^]’.
  • 220 Welcome to unFTP

If this test is not successful, it is almost certainly an issue with your firewall. Triple check with suppliermanagement@bol.com that your IP address has been allowed and, if that is the case, contact your own their IT department. There is nothing we can do from the bol side to diagnose this issue. 

502-Auth command

Some firewalls, will additionally inspect and block outgoing traffic based on certain content. In such cases you will be able to connect, but the FTP connection fails with an error similar to:

502-Auth command is not supported

If this is the case, please check the documentation of your firewall. A firewall that is known to block this is Fortigate.