Opened 16 years ago

Last modified 16 years ago

#301 closed Bug report

"Can't open data connection" on public IP

Reported by: mgturland Owned by: Tim Kosse
Priority: normal Component: Other
Keywords: Cc: mgturland, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Trying to run FileZilla Server on a WinXP machine, and I
keep getting this error message in the interface:

FileZilla Server version 0.8.3a beta
Copyright 2001 by Tim Kosse (Tim.Kosse@…)
Connecting to server...
Connected, waiting for authentication
Protocol error: Unknown protocol identifier (0x50 0x50
0x48).
Connection to server closed.

Wasn't able to get anywhere in terms of configuration. I
tried starting the server and connecting to it using WS-
FTP with my e-mail address and a password as the
login, and get this:

WINSOCK.DLL: WinSock 2.0
WS_FTP LE 5.08 2000.01.13, Copyright © 1992-2000
Ipswitch, Inc.

  • -

connecting to xxx.xxx.xxx.xxx:21
Connected to xxx.xxx.xxx.xxx port 21
220-FileZilla Server version 0.8.3 beta test release 1
220-written by Tim Kosse (Tim.Kosse@…)
220 Please visit http://sourceforge.net/projects/filezilla/
USER mgturland@…
331 Password required for mgturland@…
PASS (hidden)
530 Login or password incorrect!
! Logon failure, so quitting

Not sure if it's a bug, but I'm not sure how to proceed.
Suggestions?

Change History (5)

comment:1 Changed 16 years ago by Tim Kosse

Please connect to the admin port of the server, not to the
FTP port with the admin interface. The admin port is the one
you've set during setup of FileZilla Server.

comment:2 Changed 16 years ago by mgturland

OK, your suggestion worked to fix the original problem, but
now I'm stuck in the situation described in the following forum
thread:

http://sourceforge.net/forum/forum.php?
thread_id=818820&forum_id=68109

Any suggestions on this one?

comment:3 Changed 16 years ago by Tim Kosse

Can you please describe the server environment? Are you
using firewalls, is the server behina a router/proxy/NAT
machine?
Please also post the log files both from the server and the
client.

comment:4 Changed 16 years ago by anonymous

Logged In: NO

Windows XP server
Using ZoneAlarm (doesn't seem to make any difference if it's
on or not in relation to the problem)
Server is behind a LinkSys router, which forwards requests for
ports 20 and 21 to the local server IP.

Server Log:
(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

Connected, sending welcome message...

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

220-FileZilla Server version 0.8.3 beta test release 1

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

220-written by Tim Kosse (Tim.Kosse@…)

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

220 Please visit http://sourceforge.net/projects/filezilla/

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

USER mgturland

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

331 Password required for mgturland

(000018) 4/17/2003 6:44:05 AM - (not logged in) (192.168.1.1)

PASS *

(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
230 Logged on
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
PWD
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
257 "/" is current directory.
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
SYST
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
215 UNIX emulated by FileZilla
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
PASV
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
421 Can't create socket
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
PORT 192,168,1,1,9,202
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
200 Port command successful
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
LIST
(000018) 4/17/2003 6:44:05 AM - mgturland (192.168.1.1)>
150 Opening data channel for directory list.
(000018) 4/17/2003 6:44:26 AM - mgturland (192.168.1.1)>
425 Can't open data connection

Client Log:
WINSOCK.DLL: WinSock 2.0
WS_FTP LE 5.08 2000.01.13, Copyright © 1992-2000
Ipswitch, Inc.

  • -

connecting to xxx.xxx.xxx.xxx:21
Connected to xxx.xxx.xxx.xxx port 21
220-FileZilla Server version 0.8.3 beta test release 1
220-written by Tim Kosse (Tim.Kosse@…)
220 Please visit http://sourceforge.net/projects/filezilla/
USER mgturland
331 Password required for mgturland
PASS (hidden)
230 Logged on
PWD
257 "/" is current directory.
SYST
215 UNIX emulated by FileZilla
Host type (S): UNIX (standard)
PASV
421 Can't create socket
PORT 192,168,1,128,9,202
200 Port command successful
LIST
150 Opening data channel for directory list.
! Timer cancelled blocking call
! Accept error: Blocking call cancelled
! Retrieve of folder listing failed (0)

comment:5 Changed 16 years ago by Tim Kosse

Since the server is behind a router, you may also have to
forward the ports used for data transfers.
The portrange FZS should use can be set in the interface.

Also, connecting to the server from inside your network using
the external IP might not work with firewalls and/or routers.

Note: See TracTickets for help on using tickets.