What Happens When a Secure FTP Port Changes?
Like almost all services, the Secure FTP (SFTP) service in an operating system is designed to be able to listen on other ports than the default one. Not all services listen on their default ports and there are many reasons why a person would change it.
Other People Are Reading
-
Effects
-
When an SFTP port changes, you will notice that you will not be able to connect to the server through that port. If there is another service running on that port in place of SFTP, your SFTP session will not work as you expect it to.
What to Do as Server
-
If you are running a server and decided to change the listening port for SFTP, you have to inform the clients that connect to that port that it changed. Otherwise, they will continue to attempt to establish a session without success.
-
What to Do as Client
-
If you are a client that notices that the SFTP service is not working correctly on a server you are trying to connect to, email the person responsible for the server and ask what is wrong. Someone might respond telling you that there is a problem with the service or the port changed.
Signs
-
You cannot know for sure as a client if the port for a service changed unless you have access to the server. The signs of a port change are a timeout or a refusal of connection to the port.
Misconceptions
-
You will not be able to find out the new SFTP port in any way, so do not allow anyone to lead you into thinking that you can simply download some software to find out what the new SFTP port on a server is. You can only make a list of open ports on a server, but not find out which one in particular leads to its SFTP service.
-
