CuteFTP & G6 FTP SERVER

[TBob]

Hello,

I am running a G6FTP server and when i try and connect to it through CuteFTP, i get the following error message:

STATUS:> Connecting to ***********
STATUS:> Connecting to *********** (ip = **.**.**.**)
STATUS:> Socket connected. Waiting for welcome message...
220 FTP Server
STATUS:> Connected. Authenticating...
COMMAND:> USER r
331 Password required for r.
COMMAND:> PASS ********
230 User r logged in.
STATUS:> Login successful
COMMAND:> TYPE I
200 Type set to I.
COMMAND:> REST 100
350 REST supported. Ready to resume at byte offset 100.
COMMAND:> REST 0
350 REST supported. Ready to resume at byte offset 0.
STATUS:> This site can resume broken downloads
COMMAND:> PWD
257 "/" is current directory.
COMMAND:> TYPE A
200 Type set to A.
STATUS:> Retrieving directory listing...
COMMAND:> PASV
227 Entering Passive Mode (192,168,0,2,241,195).
STATUS:> Connecting data socket...
ERROR:> Failed to establish data socket

Is there something im missing ... iv heard somethin about passv or something that may be the problem but im not sure ... any help would be greatly appreciated!

[brembo]

Cute often has problems with G6, I dunno why, but I've problems myself. I prefer WS_FTP myself.

[64bit]

Are you connecting to a private LAN address or your WAN ip Address. Do you have a router?

[TBob]

Yes i have a router... both computer im connecting to and from are behind routers.

[64bit]

When u use port instead of passive can u connect no problem?

[TBob]

I can connect using port or passive. The only problem comes when it goes to list the directory.

[64bit]

Originally posted by TBob
I can connect using port or passive. The only problem comes when it goes to list the directory.

Well i was gonna suggest that the ports to allow pasv operation were either not set up on the FTP server or not forwarded to the router or both but since you said you can't get a directory listing using PORT either well then I don't know.....

[64bit]

1 more question are both the server and the client connecting on the same LAN behind the same router and are you trying to use the outside either DNS name or ip address to connect?

[TBob]

Originally posted by 64bit
1 more question are both the server and the client connecting on the same LAN behind the same router and are you trying to use the outside either DNS name or ip address to connect?

Its 2 different computers. Im accessing a friends computer thats on a different ISP then me. And its using dns to resolve his ip.

[TBob]

I setup the FTP server ... and i didnt change anything to do with passv. I just added the accounts and forwared the one port through his router.

[64bit]

Well I would do like brembo said try another client. Also is a default / directory setup and access rights granted(just coverin all bases)? What router are both he and u using?

[TBob]

I tried WS_FTP ... and i still get the same thing. I have setup an account for me and he has an account for his C:\ drive. Both with full read/write/list/everything!

I am using a lynksys router, and he is using a netgear.

[ghost]

Originally posted by TBob
I setup the FTP server ... and i didnt change anything to do with passv. I just added the accounts and forwared the one port through his router.

I think this is your problem.

This quoted text can explain it better than I:



In order to resolve the issue of the server initiating the connection to the client a different method for FTP connections was developed. This was known as passive mode, or PASV, after the command used by the client to tell the server it is in passive mode.

In passive mode FTP the client initiates both connections to the server, solving the problem of firewalls filtering the incoming data port connection to the client from the server. When opening an FTP connection, the client opens two random unprivileged ports locally (N > 1024 and N+1). The first port contacts the server on port 21, but instead of then issuing a PORT command and allowing the server to connect back to its data port, the client will issue the PASV command. The result of this is that the server then opens a random unprivileged port (P > 1024) and sends the PORT P command back to the client. The client then initiates the connection from port N+1 to port P on the server to transfer data.

From the server-side firewall's standpoint, to support passive mode FTP the following communication channels need to be opened:

FTP server's port 21 from anywhere (Client initiates connection)
FTP server's port 21 to ports > 1024 (Server responds to client's control port)
FTP server's ports > 1024 from anywhere (Client initiates data connection to random port specified by server)
FTP server's ports > 1024 to remote ports > 1024 (Server sends ACKs (and data) to client's data port)

[TonyT]

Use a better FTP Client. CuteFTP is SPYWARE that will wreak havoc w/ the TCP\IP stack in windows.