Computer Hope
Internet & Networking => Networking => Topic started by: Geek-9pm on October 05, 2017, 10:04:56 PM
-
The might be important. for years I have used FTP for some kind of tool to upload files onto a server. Sometimes FTP, other times a web page editor.
ow I have come onto a problem that might be a web host vendor that bends the rules. Granted, FTP is a real security thing. But he said I can FTP and never said it was turned off. No, he did not warm me it does not work, instead he said to turn off TLS. I was stumped. Never heard of that before. :o
So I did turn it off using Filezilla. The Filezilla documentation covers that.
OK. But it still does not work.
Now then, I am thinking I sometimes do very dumb blunders . You people here and a broad experience wish to tap. Can you help me verify the FTP to these two sites?
ophir.pw
IP 104.206.226.173 in Las Vegas
and
ophir.xyz
IP 155.94.224.140 in Los Angles
There is a directory named test on both sites. I have put information there as to how you might test the FTP service. Just let me know if you can get into the site with FTP. That is all I need to know.
Later I will change details to make the sites secure again.
If just two people get in, then I know it works.
If just two people run into a 'connection refused' then I know the vendor is messing up the FTP and not telling his clients.
(If h does not want FTP he could offer another way to upload files.)
Thanks in advance.
EDIT: Both sites are mine. No content of value. The is nothing bad there. It is just a very simple test of the FTP service the vendor claims works. :)
-
Both the addresses give an "authentication required" prompt when attempting to connect via FTP.
-
Thank you for giving it a try. :)
Do this:
Open the site in a browser.
Try to get into a directory names 'test'
Like this
http://ophir.pw
then
http://ophir.pw/test
There you will see a readme.txt file that hast he user name and password for FTP.
What happens to me is that it all goes well until it gets to the place where the client gives a command to show the directory of the public folder. The Filezilla ti mes out and quirts. Filezilla documentations says this is due to some kind of protocol issue.
However, one site does work, the other does not.
I want to know if others see that same behavior.
-
Works fine for me with FileZilla.
Status: Connecting to 104.206.226.173:21...
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: Verifying certificate...
Status: TLS connection established.
Status: Logged in
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
-
Thank you BC.
Now I know that 104.206.226.173:21 is usable by others.
I want to resell that site to others, maybe not the same domain. Now I know that oother people will be able to use it.
The other sites has an IP of 155.94.224.140 for LA.
Are you able to get the same resultants? For me the directory command would fail when using Filezilla.
I suspect the owner of the server either does not know what he is doing or maybe he does not care. That could explain why he sells his web space at a big discount. ut if I can not some form of FTP or maybe SMTP then is is almost unusable.
Thank you for you help. :)