LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   "Name resolution failure"-- but already using IP address, there is no name to resolve (https://www.linuxquestions.org/questions/linux-networking-3/name-resolution-failure-but-already-using-ip-address-there-is-no-name-to-resolve-4175605893/)

firejuggler86 05-13-2017 10:17 PM

"Name resolution failure"-- but already using IP address, there is no name to resolve
 
Hello,

I am trying to connect to an FTP server that I am running from another device on my local network. This server is configured to listen for connections on port 2221 instead of the default 21. Trying to connect with

produces the following output:

Quote:

ftp: ftp://192.168.1.2:2221: Temporary failure in name resolution
(note: i get the same result if i omit the "ftp://")

If I try to ping 192.168.1.2:2221 I get the output "ping: unknown host 192.168.1.2:2221"

I'm fairly sure I have the syntax wrong, somehow, but the ftp manpages contain no examples whatsoever of the proper syntax.

Any help would be much appreciated..thanks!

Please note....I acknowledge I may not be correct regarding this issue being caused by incorrect syntax, but I strongly suspect that it is, and I am not going to post logs for an issue having to do with typing the wrong syntax for a command. If that is not the case, we'll go from there. Thanks.

Ser Olmy 05-14-2017 02:12 AM

The ftp command doesn't accept the ":<number>" syntax for specifying an alternative port number, so it thinks the address might be a hostname instead. The connect syntax is ftp <hostname> [<port>] (the port number should simply be the next parameter following the hostname or IP address).

As for the ping command, specifying a port name makes no sense at all as no ports are involved when sending or receiving ICMP packets.


All times are GMT -5. The time now is 07:40 PM.