Server Setup Woes (Please be kind; assume I'm a blank slate)
Moderator: Project members
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Server Setup Woes (Please be kind; assume I'm a blank slate)
I have read and re-read posts on this forum and others to no avail. I've watched tutorials presented by "experts" with varying accents. I am pulling out what little remains of my hair.
I'm trying to set up an FTP server on a Win 10 PC at my house so I can upload files from a work computer.
Here's what I've done so far:
• Installed the latest version of FileZilla Server on Windows 10 PC (Pentium CPU G4400 @ 3.30GHz 3.31 GHz 8GB RAM)
• Installed and set up No-IP Dynamic Update Client (DUC) so I will have a static address (for the sake of illustration, we'll call the address "wxxx.ddns.xyz"
• Logged into router and forwarded proper port to PC's local IP address (example: 192.168.0.200)
• Set up FileZilla Server; configured Group (Main) and User with Virtual Path (/) and Native Path (c:\folder); password required to login
• Set up FileZilla Server with Server Listeners that shows local PC's IP address (as above)
• Cleared FileZilla Server on Windows Firewall
I've tried different ports, different protocols and I can almost connect, but...the connection aborts.
Here's how things look on the client side (with necessary edits):
Status: Resolving address of wxxx.ddns.xyz
Status: Connecting to XX.XXX.108.2:2121... (external IP)
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Command: USER SPL
Response: 331 Please, specify the password.
Command: PASS **************
Response: 530 Login incorrect.
Error: Critical error: Could not connect to server
Here's how things look on the server side (with edits):
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220-FileZilla Server 1.8.0
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220-Please visit https://filezilla-project.org/
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220 Welcome to the WXXX Automation Backup
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] AUTH TLS
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 234 Using authentication type TLS.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] USER SPL
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 331 Please, specify the password.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] PASS ****
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 530 Login incorrect.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Status] Client did not properly shut down TLS connection
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Error] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.
Please understand, I'm a radio dude trying to make my way through a swamp I don't understand using maps written in an alien language. If you have thoughts or suggestions, assume I'm your less-than-brilliant brother-in-law who needs everything repeated twice. Thanks!
I'm trying to set up an FTP server on a Win 10 PC at my house so I can upload files from a work computer.
Here's what I've done so far:
• Installed the latest version of FileZilla Server on Windows 10 PC (Pentium CPU G4400 @ 3.30GHz 3.31 GHz 8GB RAM)
• Installed and set up No-IP Dynamic Update Client (DUC) so I will have a static address (for the sake of illustration, we'll call the address "wxxx.ddns.xyz"
• Logged into router and forwarded proper port to PC's local IP address (example: 192.168.0.200)
• Set up FileZilla Server; configured Group (Main) and User with Virtual Path (/) and Native Path (c:\folder); password required to login
• Set up FileZilla Server with Server Listeners that shows local PC's IP address (as above)
• Cleared FileZilla Server on Windows Firewall
I've tried different ports, different protocols and I can almost connect, but...the connection aborts.
Here's how things look on the client side (with necessary edits):
Status: Resolving address of wxxx.ddns.xyz
Status: Connecting to XX.XXX.108.2:2121... (external IP)
Status: Connection established, waiting for welcome message...
Status: Initializing TLS...
Status: TLS connection established.
Command: USER SPL
Response: 331 Please, specify the password.
Command: PASS **************
Response: 530 Login incorrect.
Error: Critical error: Could not connect to server
Here's how things look on the server side (with edits):
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220-FileZilla Server 1.8.0
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220-Please visit https://filezilla-project.org/
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 220 Welcome to the WXXX Automation Backup
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] AUTH TLS
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 234 Using authentication type TLS.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] USER SPL
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 331 Please, specify the password.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Command] PASS ****
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Response] 530 Login incorrect.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Error] GnuTLS error -110 in gnutls_record_recv: The TLS connection was non-properly terminated.
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Status] Client did not properly shut down TLS connection
<12/20/2023 6:48:26 PM> FTP Session 100 70.171.108.2 [Error] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.
Please understand, I'm a radio dude trying to make my way through a swamp I don't understand using maps written in an alien language. If you have thoughts or suggestions, assume I'm your less-than-brilliant brother-in-law who needs everything repeated twice. Thanks!
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
It's the authentication that is failing.
Is user SPL enabled? If so, make sure you are inputing the password correctly.
If the problem persists, set the server logging level to "5 - Debug" and paste here the server log again.
Is user SPL enabled? If so, make sure you are inputing the password correctly.
If the problem persists, set the server logging level to "5 - Debug" and paste here the server log again.
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
oilbaf.
Success! For some reason, the server did not like the user SPL, so I created a new user called Admin which worked perfectly.
I was able to upload files from one PC to another on my local network; now to try and log in from the remote computer.
Many thanks! Happy Holidays!
Success! For some reason, the server did not like the user SPL, so I created a new user called Admin which worked perfectly.
I was able to upload files from one PC to another on my local network; now to try and log in from the remote computer.
Many thanks! Happy Holidays!
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
May have spoken too soon...
While I can connect across the LAN, attempts to reach the server from a remote PC timed out:
Status: Resolving address of ftp.wxxx.ddns.xyz
Status: Connecting to XXX.XX.112.55:2121...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.wxxx.ddns.xyz
Status: Connecting to XXX.XX.112.55:2121...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
I was able to ping both the DNS "alias" and the actual IP address, but can't establish connection to the server. The server log shows nothing re: connection attempts.
While I can connect across the LAN, attempts to reach the server from a remote PC timed out:
Status: Resolving address of ftp.wxxx.ddns.xyz
Status: Connecting to XXX.XX.112.55:2121...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Resolving address of ftp.wxxx.ddns.xyz
Status: Connecting to XXX.XX.112.55:2121...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
I was able to ping both the DNS "alias" and the actual IP address, but can't establish connection to the server. The server log shows nothing re: connection attempts.
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
Here are the results from the Online FTP Server test site (https://ftptest.net/):
Status: Resolving address of wxxx.ddns.xyz
Status: Connecting to XX.XXX.108.2
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 1.8.0
Reply: 220-Please visit https://filezilla-project.org/
Reply: 220 Welcome to the WXXX Automation Backup
Command: CLNT https://ftptest.net on behalf of XXX.62.88.87
Reply: 200 Don't care.
Command: AUTH TLS
Reply: 234 Using authentication type TLS.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Command: USER Admin
Reply: 331 Please, specify the password.
Command: PASS **************
Reply: 230 Login successful.
Command: SYST
Reply: 215 UNIX emulated by FileZilla.
Command: FEAT
Reply: 211-Features:
Reply: MDTM
Reply: REST STREAM
Reply: SIZE
Reply: MLST type*;size*;modify*;perm*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: TVFS
Reply: EPSV
Reply: EPRT
Reply: MFMT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (XX,XXX,108,2,228,77)
Command: MLSD
Reply: 150 About to start data transfer.
Error: Connection timed out
Status: Resolving address of wxxx.ddns.xyz
Status: Connecting to XX.XXX.108.2
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 1.8.0
Reply: 220-Please visit https://filezilla-project.org/
Reply: 220 Welcome to the WXXX Automation Backup
Command: CLNT https://ftptest.net on behalf of XXX.62.88.87
Reply: 200 Don't care.
Command: AUTH TLS
Reply: 234 Using authentication type TLS.
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='CN=filezilla-server self signed certificate' issuer='CN=filezilla-server self signed certificate'
Command: USER Admin
Reply: 331 Please, specify the password.
Command: PASS **************
Reply: 230 Login successful.
Command: SYST
Reply: 215 UNIX emulated by FileZilla.
Command: FEAT
Reply: 211-Features:
Reply: MDTM
Reply: REST STREAM
Reply: SIZE
Reply: MLST type*;size*;modify*;perm*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: TVFS
Reply: EPSV
Reply: EPRT
Reply: MFMT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (XX,XXX,108,2,228,77)
Command: MLSD
Reply: 150 About to start data transfer.
Error: Connection timed out
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
Either a firewall is blocking the configured passive mode port range (which could be _all_ ports if no range has been configured), or similarly, some NAT router isn't forwarding the configured passive mode port range.
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
Thanks, Tim!
I have been struggling with my TP-Link AX11000 router since a recent firmware "update." I just had to reset it to factory values yet again (great fun while my wife is watching television) and am seemingly back at square one. I know just enough to be dangerous re: port forwarding, etc., but will keep plowing ahead in hopes of resolving this matter. FWIW, I'm attempting to set up a backup radio station automation at my house for when the studio system fails.
Now, unless I can stumble into some success, I guess I'll join my wife in front of the TV (assuming I have properly set up the router again)!
I have been struggling with my TP-Link AX11000 router since a recent firmware "update." I just had to reset it to factory values yet again (great fun while my wife is watching television) and am seemingly back at square one. I know just enough to be dangerous re: port forwarding, etc., but will keep plowing ahead in hopes of resolving this matter. FWIW, I'm attempting to set up a backup radio station automation at my house for when the studio system fails.
Now, unless I can stumble into some success, I guess I'll join my wife in front of the TV (assuming I have properly set up the router again)!
-
- 504 Command not implemented
- Posts: 6
- Joined: 2023-12-20 23:14
- First name: Bob
- Last name: Dunn
Re: Server Setup Woes (Please be kind; assume I'm a blank slate)
I have taken several steps backward in my quest and now am utterly lost.
I no longer seem to be able to get through Port 21 (ISP issue or router problem?)
My router (TP-Link AX11000) in addition to Port Forwarding, has additional settings for "Static Routing" and "Routing Table"; do these apply?
I have an Icecast server set up on yet another PC on my network using Port 8000, and it works without issue. I am, however, using the router's native Dynamic DNS function for this rather than the Dynamic User Client (DUC) software I have set up on the FTP computer.
Any help will be greatly appreciated!
I no longer seem to be able to get through Port 21 (ISP issue or router problem?)
My router (TP-Link AX11000) in addition to Port Forwarding, has additional settings for "Static Routing" and "Routing Table"; do these apply?
I have an Icecast server set up on yet another PC on my network using Port 8000, and it works without issue. I am, however, using the router's native Dynamic DNS function for this rather than the Dynamic User Client (DUC) software I have set up on the FTP computer.
Any help will be greatly appreciated!