asked on

425 Failed to establish connection

I get this error:
"425 Failed to establish connection"
when I try to go:
ftp://mydomain.com/pub

Using winscp with root user is ok.

giltjr

Is the host mydomain.com running a real FTP server?

Although winscp support ftp, typically it is used for scp or sftp, which both use ssh under the covers.

ASKER CERTIFIED SOLUTION

Gerwin Jansen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Nusrat Nuriyev

ASKER

Is the host mydomain.com running a real FTP server?

YES

How are you going to that site? Using which application? A web browser?

Web browser

Looks like a firewall issue where ports 21 and 20 are not open on the FTP server.

Nope, they are opened: 20/TCP 21/TCP 20/UDP 21/UDP.

Fedora - firewall-cmd

SOLUTION

Gerwin Jansen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

giltjr

FTP does not use UDP, so you can close ports 20/21 UPD.

If you are running the server can you post the output from the command:

netstat -an | grep tcp | grep LISTEN

Nusrat Nuriyev

ASKER

425 occurs when the server cannot open a socket for data transfer, try ftp from command line, do you get a prompt from your FTP server?

ftp.exe
open mydomain.com
responds something like
mydomain.com unknown host

Nusrat Nuriyev

ASKER

netstat -an | grep tcp | grep LISTEN

tcp 0 0 0.0.0.0:5910 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6010 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:40770 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5903 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6003 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 8.2.9.9:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9333 0.0.0.0:* LISTEN
tcp6 0 0 ::1:953 :::* LISTEN
tcp6 0 0 :::6010 :::* LISTEN
tcp6 0 0 :::443 :::* LISTEN
tcp6 0 0 :::6881 :::* LISTEN
tcp6 0 0 :::111 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::6001 :::* LISTEN
tcp6 0 0 :::6003 :::* LISTEN
tcp6 0 0 ::1:53 :::* LISTEN
tcp6 0 0 :::39125 :::* LISTEN
tcp6 0 0 :::9333 :::* LISTEN

SOLUTION

Gerwin Jansen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

giltjr

You may want to do a packet capture on the Linux server and the Windows client at the same time. This will allow you to see what is going on.

You can use Wireshark on both platforms to do the packet capture.

giltjr

You do have a DNS record for mydomain.com?

Since you got back unknown host that implies there is no dns record for mydomain.com.

Nusrat Nuriyev

ASKER

giltjr, Reverse lookup?

giltjr

No forward. What happens when you enter:

nslookup mydomain.com

Where mydomain.com is whatever name you really enter.

Gerwin Jansen

Did you already try the IP address instead of the server name as I suggested above? What were the results?