no luck following ftp setup instructions

[depasseg]

Which FTP setup instructions did you follow, and what settings did you apply?

 

[Ptera]

To be clear I can establish an ftp session -
I can not authenticate a local user
Also the Mikrotik office router and the freeNAS on on the same subnet

PC 192.168.1.23 <-> 192.168.1.1 <-> Mikotik <->69.28.32.x <-> 69.28.32.x FreeNAS

Status: Connecting to ...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.3.4d Server (FTP Server) <<< ftp connection established - welcome message received.
Command: USER root <<< attempt to auth user
Error: Connection timed out <<< No auth - No response
Error: Could not connect to server <<< No auth - No response

 

[Noctris]

What i mean by subnet is putting the pc behind the router, in the 69.28.32.x range. I am still suspecting issues with the mikotik not handeling the passive port range correctly and thus triggering a timeout.

Have you tried tailing the proftpd log ?

 

[depasseg]

Put a computer on the same network space as the FreeNas. You are using NAT. Did you configure the ftp passive setting as described in the freebase documentation?

There is no authentication occurring, hence the no response error message. This is because the two machines are not able to communicate properly.






Sent from my Nexus 6 using Tapatalk

 

[depasseg]

And again, as you stated in the subject line, what ftp setup instructions did you follow?

Sent from my Nexus 6 using Tapatalk

 

[Ptera]

There is no proftpd log - the folder /var/log/proftpd/ is empty

OK so now I went to a linux box directly connected on the same subnet and here are the results.

ftp> open 69.28.32.xx
Connected to 69.28.32.xx (69.28.32.xx).
220 ProFTPD 1.3.4d Server ( FTP Server) [::ffff:69.28.32.xx]
Name (69.28.32.xx:root): user=root
421 Service not available, remote server has closed connection
Login failed.
No control connection for command: Success

 

[Ptera]

The instructions were from freenas docs and other references using google serach.

 

[depasseg]

And what settings did you enable? Enabling Root on the wide open internet is a bad idea BTW.

It took me a minute to enable FTP, run a test using root (which failed), go into the FTP settings and enable Root login, retry, and it worked.

 

[Noctris]

You should check /var/log/messages as well to see if any log is made concerning the 421 error ( google it, you will notice it could have several causes )

 

[Ptera]

Double checked that allow root was enabled...

/var/log/messages
Jun 9 15:57:35 nas notifier: Starting proftpd.
Jun 9 15:57:35 nas proftpd[77738]: 127.0.0.1 - ProFTPD 1.3.4d (maint) (built Mon Sep 29 2014 06:37:55 UTC) standalone mode STARTUP

went to the linux machine and started ftp session again.

Nothing in the log yet.... after waiting for a long while

Jun 9 16:04:08 nas proftpd[77806]: 127.0.0.1 (69.28.32.[69.28.32.]) - Login timeout exceeded, disconnected
Jun 9 16:04:08 nas proftpd[77806]: 127.0.0.1 (69.28.32.[69.28.32.]) - Session timed out, disconnected

 

[pirateghost]

You opened up your FreeNAS ftp to the interwebs?

I don't understand using your public IP from the LAN?

 

[jgreco]

Name (xx.xx.xx.xx:root): user=root
421 Service not available, remote server has closed connection

If you actually typed in "user=root", that's a problem. You just put in the username, in this case, the poorly-chosen "root".

 

[Ptera]

OK no more root attempts to access ftp.
Created a new user and tred again from machine on the same subnet as the freeNAS server.
No luck...
After this we can close this thread
Will use sftp instead.

 

[depasseg]

I didn't think FreeNAS supported SFTP (only FTPS, which will give you the same problems).

You have a network related problem. And you won't provide any details, so it really makes it hard to help.

 

[pirateghost]

I didn't think FreeNAS supported SFTP (only FTPS, which will give you the same problems).

You have a network related problem. And you won't provide any details, so it really makes it hard to help.

Sftp=file transfer over ssh. As long as ssh is enabled, sftp works great.