Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Unable to connect to a server from our AIX server via FTP Post 303044394 by Neo on Thursday 20th of February 2020 08:25:07 AM
Old 02-20-2020
Quote:
Originally Posted by Bruno2020

Can you tell me how to open port 20? Do i need to modify anything in the /etc/services file ?
Bruno,

You do not need to worry about port 20 (yet). That line of thinking is leading you off track (sorry Rudi) because you need to establish you have a working route (network connection) between your private IP address space and the Internet. What you are describing (so far) is just a simple network configuration issue.

You cannot ping your ftp host. ping does not use ports. The ping protocol works at the transport layer.

Quote:
There is no TCP or UDP port number associated with ICMP packets as these numbers are associated with the transport layer above.
So, if you cannot ping, you can do nothing (unless ping is blocked by a firewall rule, but then you have other problems, and you are not ready for that yet) .... on any of the ports from 1 to over 65,000 (65,535 TCP and 65,535 UDP ports, to be exact), open or not, LOL. You can open port 20 as wide as a truck and you will still not be able to connect to it; because you have described basic networking issues. You cannot ping at the transport layer (yet).

Since you can ping your own interface (that is good news, at least) , you need to try to ping the next hop on your network (normally your router, but you have not provided a diagram. Please upload a sketch as I mentioned, using the attachment feature of the site, not an external img hosting link).

Do you know what the IP address of your router is?

Also, can you run the arp command on your computer?

Try:

Code:
$ arp -a

That is the next step.... you need to see if you can or cannot connect (ping) the next hop in your network.

You are getting "ahead of yourself" if you try to work / troubleshoot at the TCP or UDP layer before you make sure you are good to go lower in the stack (at the transport layer).

That is why we need to establish you can ping first.

Understand yet? To troubleshoot networking issues, it is best to start at the bottom and work your way up the protocol stack (not the other way around). If you learn to troubleshoot like this, you will find it much easier and much faster to solve problems, I promise.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ftp script not able to connect to ftp server.

I have the following ftp script to get files from a remote location. However, on running the script I find that I am not even able to connect to ftp server. I am able to connect to ftp server using other GUI ftp tools like WS_FTP using the same IP. IP used here is a dummy IP. What can go... (3 Replies)
Discussion started by: gram77
3 Replies

2. AIX

Unable to connect to AIX server through xmanager

Hi, I have xmanager installed on my windows PC. But I am not able to connect to AIX server. It's giving the error as follows: The X11 forwarding request was rejected. Graphics mode is not coming up in AIX server. Please help as I have to install oracle patchset urgently. (1 Reply)
Discussion started by: dwiravi
1 Replies

3. HP-UX

[Solved] Unable to rename file in ftp server .Net:FTP perl

Hello All, I am trying to connect to ftp server and get the files. Also i need to rename the file in other ftp dir. rename method is not allowing me to rename the file in other dir. When i tried copy command by using net::FTP:FILE then perl says it is not installed. Can some body help me to... (2 Replies)
Discussion started by: krsnadasa
2 Replies

4. UNIX for Advanced & Expert Users

Unable to use FTP command to connect from one server to another

Hi, I have two unix servers A and B. from A i am trying to use the ftp command to connect to B but I am getting the "ftp: connect: A remote host refused an attempted connect operation." I checked the following things : 1.) Unix Server details for A and B after running the command uname -a... (3 Replies)
Discussion started by: mick_000
3 Replies

5. Red Hat

unable to connect remote server using ssh

hi all i am unable to connect remote server using ssh but i am able to ping the server ssh service is running. (5 Replies)
Discussion started by: nikhil kasar
5 Replies

6. Linux

Generate public key to connect from one ftp server to other server

How to generate public key to connect from one ftp server to other server to use in scripting. (0 Replies)
Discussion started by: sridhardwh
0 Replies

7. UNIX for Advanced & Expert Users

Public key to connect from one ftp server to other server

How to generate public key to connect from one ftp server to other server to use in scripting. (1 Reply)
Discussion started by: sridhardwh
1 Replies

8. Linux

Unable to connect to Server machine from a client machine using ftp service

Hi, Could you please help me with the below issue.. I'm running RHEL6 OS on both server (192.168.0.10) and client machines (192.168.0.1). I'm trying to connect to server from the client machine using ftp service. I have installed vsftpd daemon on both the machines. I'm getting... (4 Replies)
Discussion started by: raosr020
4 Replies

9. Solaris

Unable to connect sun server.

Hi, I am unable to connect sun server, server model is sun fire v440 on server 2 ports are there. serial management, and network management. I would like to know how to connect serial port if I dont have com port on my system? and on Network Management no ip address is configured. ... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

10. Shell Programming and Scripting

Not able to connect to new FTP server

Hi All, We have done new FTB setup. I am not able to to connect to this new target server. Here is the new setup to send files to the FTB : - Login : FTB-TAN-DEV-SAP - Protocol : SFTP - Port : 54322 - Hostname : ftb-dev.apj.hp - Env : DEV - Target ID : 3225 I tried connecting to the... (5 Replies)
Discussion started by: ROCK_PLSQL
5 Replies
TRACEROUTE6(8)						    BSD System Manager's Manual 					    TRACEROUTE6(8)

NAME
traceroute6 -- print the route IPv6 packets will take to a network node SYNOPSIS
traceroute6 [-adIlnNrvU] [-f firsthop] [-g gateway] [-m hoplimit] [-p port] [-q probes] [-s src] [-w waittime] [-A as_server] target [datalen] DESCRIPTION
The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to some host. The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addi- tion to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name. Other options are: -a Turn on AS# lookups for each hop encountered. -A as_server Turn on AS# lookups and use the given server instead of the default. -d Debug mode. -f firsthop Specify how many hops to skip in trace. -g gateway Specify intermediate gateway (traceroute6 uses routing header). -I Use ICMP6 ECHO instead of UDP datagrams. -l Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric addresses if -n is specified. -m hoplimit Specify maximum hoplimit, up to 255. The default is 30 hops. -n Do not resolve numeric address to hostname. -N Use a packet with no upper layer header for the probes, instead of UDP datagrams. -p port Set UDP port number to port. -q probes Set the number of probe per hop count to probes. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected net- work, an error is returned. This option corresponds to the SO_DONTROUTE socket option; it can be used to ping a local host through an interface that has no route through it (e.g., after the interface was dropped by a routing daemon). -s src Src specifies the source IPv6 address to be used. -U Use UDP datagrams for the probes. This is the default. -v Be verbose. -w waittime Specify the delay time between probes. This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute. Here is a list of possible annotations after the round-trip time for each gateway: !N Destination Unreachable - No Route to Host. !P Destination Unreachable - Administratively Prohibited. !S Destination Unreachable - Not a Neighbour. !A Destination Unreachable - Address Unreachable. ! This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was more interesting in the IPv4 case, where some IP stack bugs could be identified by this behaviour. EXIT STATUS
The traceroute6 utility will exit with 0 on success, and non-zero on errors. SEE ALSO
ping(8), ping6(8), traceroute(8) HISTORY
The traceroute6 utility first appeared in WIDE hydrangea IPv6 protocol stack kit. BSD
August 24, 2009 BSD
All times are GMT -4. The time now is 07:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy