NOOP command doesn't work

[d**k]

Hi. I am using FlashFXP 2.1 and when I set it to NOOP I will always get disconnected. I know that some servers don't support NOOP but I had used a different FTP program for the same server and it did work.

Anyone else have this problem?
Thanks

[d**k]

No one else has ever had this problem or know what the solution is?? .:confused:

Please reply if you do.

[MxxCon]

please read forum posting RULES
http://forum.flashfxp.com/showthread.php?s=&threadid=3078

[d**k]

build is 924
windows xp professional

The rest probably isn't relevant because I was using cuteftp with the same settings and it worked fine. And also I am not sure about the proxy or the nat. I am using a netgear router which has a firewall.
And it is all sites. I was using cuteftp with the same sites and it was fine so I don't think it is the sites.
I would have bought cuteftp but it was too expensive.
here is a picture of the status log.

Thank you.

[d**k]

the file I attached didn't go through

[d**k]

Okay, I just read some of the rules so here it is.
it is the registered version 2.1 build 924
Windows xp pro
netgear router model rp 114 and it is firewalled
Running Symantic anti virus
and I am using cable internet.
One of the sites are upload.comcast.net
Here is the FlashFXP timestamp:

NOOP
200 NOOP command successful.
NOOP
200 NOOP command successful.
NOOP
200 NOOP command successful.
NOOP
200 NOOP command successful.
NOOP
421 No Transfer Timeout (300 seconds): closing control connection.
Connection lost:

[Linkster]

Sounds like the server is set to ignore noops...nothing can be done about that.

[d**k]

Originally posted by Linkster
Sounds like the server is set to ignore noops...nothing can be done about that.

I had said that while using a trail of another FTP program it DID work with the same server.

[d**k]

Originally posted by d**k
I had said that while using a trail of another FTP program it DID work with the same server.

Trial I meant to say.

[MxxCon]

don't use "NOOP" to anti-idle, use another command.
cuteftp is prolly using combination of noop and another command.
if you don't like that noop timeout, complain to administrator of that site to increase idle timeout

[MidKnight]

as stated, ftpd might ignore noop command, if this is the case, then your probably not welcome to use anti-idle commands. some sysops dont like it, im actually one of them. check with your sysop as you could be facing a permanant ban otherrwise

[d**k]

Why would one ftp program work with a site while another won't work with the Same site?

[MidKnight]

most likely something like mx said

cuteftp is prolly using combination of noop and another command.

have you tried another keep-alive command in ffxp instead of the noop?

[DYN_DaTa]

Originally posted by MidKnight

have you tried another keep-alive command in ffxp instead of the noop?


As MidKnight said try to use other keep-alive command. I used to have a similar problem with a server that was ignoring 'NOOP' commands, i changed to 'LIST' command and problem solved.

Actually (with build 922) you can use 'NOOP', 'LIST', 'PWD', 'CWD' or 'refresh' as keep-alive commands.

[d**k]

I have tried them all except list which is what I am trying now. Hopefully it works.

[d**k]

List works!
Thank you all for the help