Member Avatar for jto

i have a winxp system . i am using ftp to get files from unix server ,on other system it is working , but in this system when i am using the command 'ls ' to see the list of files ia m gettimg the following massage
"200 port command successful
150 opening ASCII mode data conection for file list
226 transfer complete "
and i am not getting the list and also same massage is geting when i am using mget command to get files from unix server . why it is happening pls help me.

  • 3 Contributors
  • 2 Replies
  • 127 Views
  • 2 Years Discussion Span
  • Latest Post Latest Post by bsjang

Dani AI

Generated

This kind of symptom — the FTP control session completes but you never see the directory or file data — usually means the control channel is fine but the data channel is not arriving at the client. That makes a server problem less likely when a different workstation can list files; the issue is usually on the client side, the local host/network, or the router/NAT between them. was right to look at client differences, and ’s pointer to network filtering is also on the right track.

Practical way to narrow it down:

  • Reproduce the problem while capturing traffic (Wireshark/tcpdump). Watch the FTP control stream and then look for a second TCP flow that carries the data (the directory listing or file bytes). If the second flow never completes a TCP handshake toward the client, something is blocking the incoming data connection.
  • If that second TCP connection does complete but you still don’t see listing text, check for character-set/newline translation or an intermediate device mangling the payload.

Fixes to try (in order):

  • Try a different FTP client on the same PC and toggle the client’s transfer-mode option (active vs passive). If one mode works and the other fails, that tells you whether the server is trying to connect back to the client (active) or the client must open the data connection (passive).
  • Temporarily disable any local personal-firewall/AV network filtering and retest to isolate whether the client host is blocking the data connection.
  • If the machine is behind NAT, inspect whether the IP/port the client advertised to the server is reachable from the server. If it is not, either use the client’s passive mode or adjust the NAT/router FTP helper/forwarding policy.

If further help is needed, include: a short control-channel transcript, the client’s mode (active/passive), and a brief packet-capture showing the failed data attempt — those make root-cause diagnosis straightforward.

Recommended Answers

All 2 Replies

Member Avatar for Pimp Daddy

Normally I would have said the server was at fault, but if it's working with another system then it's clearly not the case. Try stuff like restarting the system and/or stopping the ftp connection and then restarting it.

If these suggestions don't work then please reply to this post.

I should point out that there are alternatives to the Command Prompt in Windows. If you are a UNIX fan, you should definitely try Cygwin - I use this instead of the command prompt now as it has a much wider range of features (well, it is an implementation of Red Hat Linux. You'll get things like sftp). There's also MSH - the Microsoft Shell, otherwise known as 'Monad'. It's in beta, but is better than the existing command prompt.

Member Avatar for bsjang

firewall port open
21
20

sorry~ i am little english

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.