Titel: Verbindungsabbruch bei Passive Mode Beitrag von: Chaos_Lord am 11. Januar 2005, 16:19:36 Hallo Leute,
ich habe hier mal wieder ein Problem mit dem Verbindungsabbruch beim Umschalten auf den Passive Mode. Das Problem ist nur, das der Rechner nicht hinter einer Firewall/Router hängt, sondern direkt eine eigene IP-Adresse hat. Dennoch wird die Verbindung abgebrochen. Woran kann das denn noch liegen? Verwendete Config siehe unten, ist aber im Großen und Ganzen zum testen erstmal die Original. Danke schoon mal für alle Ideen und Hinweise C L # This is a basic ProFTPD configuration file (rename it to # 'proftpd.conf' for actual use. It establishes a single server # and a single anonymous login. It assumes that you have a user/group # "nobody/nogroup" and "ftp" for normal operation and anon. ServerName "Debian" ServerType standalone DeferWelcome off DefaultRoot ~ MultilineRFC2228 on DefaultServer on ShowSymlinks on AllowOverwrite on TimeoutNoTransfer 600 TimeoutStalled 600 TimeoutIdle 1200 DisplayLogin welcome.msg DisplayFirstChdir .message ListOptions "-l" DenyFilter \*.*/ # Uncomment this if you are using NIS or LDAP to retrieve passwords: #PersistentPasswd off # Uncomment this if you would use TLS module: #TLSEngine on # Uncomment this if you would use quota module: #Quotas on # Uncomment this if you would use ratio module: #Ratios on # Port 21 is the standard FTP port. Port 21 # To prevent DoS attacks, set the maximum number of child processes # to 30. If you need to allow more than 30 concurrent connections # at once, simply increase this value. Note that this ONLY works # in standalone mode, in inetd mode you should use an inetd server # that allows you to limit maximum number of processes per service # (such as xinetd) MaxInstances 30 # Set the user and group that the server normally runs at. User nobody Group nogroup <Directory /*> # Umask 022 is a good standard umask to prevent new files and dirs # (second parm) from being group and world writable. Umask 022 # Normally, we want files to be overwriteable. AllowOverwrite on </Directory> # A basic anonymous configuration, no upload directories. # <Anonymous ~ftp> # User ftp # Group nogroup # # We want clients to be able to login with "anonymous" as well as "ftp" # UserAlias anonymous ftp # # Cosmetic changes, all files belongs to ftp user # DirFakeUser on ftp # DirFakeGroup on ftp # # RequireValidShell off # # # # Limit the maximum number of anonymous logins # MaxClients 10 # # # We want 'welcome.msg' displayed at login, and '.message' displayed # # in each newly chdired directory. # DisplayLogin welcome.msg # DisplayFirstChdir .message # # # Limit WRITE everywhere in the anonymous chroot # <Directory *> # <Limit WRITE> # DenyAll # </Limit> # </Directory> # # # Uncomment this if you're brave. # # <Directory incoming> # # # Umask 022 is a good standard umask to prevent new files and dirs # # # (second parm) from being group and world writable. # # Umask 022 022 # # <Limit READ WRITE> # # DenyAll # # </Limit> # # <Limit STOR> # # AllowAll # # </Limit> # # </Directory> # # </Anonymous> Titel: Re: Verbindungsabbruch bei Passive Mode Beitrag von: stonki am 11. Januar 2005, 16:35:44 keine Firewall aktiv ?
Titel: Verbindungsabbruch bei Passive Mode Beitrag von: Chaos_Lord am 11. Januar 2005, 16:53:18 ja und nein, also mit firewall aktive gehts genausowenig (wen wunderts :D ) als wenn ich die Firewall deaktiviere.
Sprich nein :P |