Log file entries from local PC - strange

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
jsbsmd
500 Command not understood
Posts: 1
Joined: 2020-02-14 20:13
First name: John
Last name: Beaudoin

Log file entries from local PC - strange

#1 Post by jsbsmd » 2020-02-15 19:16

I'm running the ftp server only allowing 4 outside ip's to contact it via ftptls

the host is 192.168.0.103 and it look like its trying to access itself. Not too worried about hack attempts but i'd like to know whats happening.

Here is a snippet of the log

Connected on port 21, sending welcome message...
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 220-FileZilla Server 0.9.60 beta
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 220 Please visit https://filezilla-project.org/
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> i
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> eU§ärandom1random2random3random4
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> /
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 9
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 0
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> ,
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> *
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)>
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> 500 Syntax error, command unrecognized.
(002723) 2/12/2020 11:47:03 AM - (not logged in) (192.168.0.103)> disconnected.
Attachments
fzs-2020-02-12.log
(11.19 KiB) Downloaded 29 times

User avatar
botg
Site Admin
Posts: 33171
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Log file entries from local PC - strange

#2 Post by botg » 2020-02-16 19:22

You have malware installed on your own computer that does this.

Photekz
500 Command not understood
Posts: 1
Joined: 2020-07-09 10:25

Re: Log file entries from local PC - strange

#3 Post by Photekz » 2020-07-09 10:47

I know this post is quite a few months old but I'm having the same exact issue with 2 computers on my network doing exactly this. Did you manage to fix it?


edit: ok I'm stupid I just realized what it is. Its just Advanced IP Scanner trying out what ports/protocols are open when launching the scan proccess.

Post Reply