FTP

  • Thread starter Thread starter Lev
  • Start date Start date
L

Lev

Hello,
Ran into an interesting problem here.
For troubleshooting purposes I am trying to connect to an FTP site using
the windows command line. Using a test computer (same system model and
network using the same routes) I can connect fine to any FTP site and
everything works. Using the problem computer I can connect but cannot get a
directory listing. I can change directories but I cannot get a directory
using dir or ls. I have turned off the windows firewall and it still does
not give me a directory list. I have also tried to connect to an FTP site
internally and I get the same results so it cannot be a firewall that is
interfering. This has to be something on the Windows box itself. I have
looked for any other applications like firewalls or anything else that might
effect the FTP but cannot find anything. Using the test system (that FTP
works on) I have stepped through the task manager on the problem system and
stopped any tasks that the working system doesn't have running. Still no
joy. I have run a sniffer and can see the directory command go out and can
see a response being returned. I also have another user with the same
problem. The actuall error is

ftp>dir
200 PORT command successful
425 cannot open data connection

If I do a cd command after this it works. Provided of course that I know
what the directory name is that I want to change to.

Thoughts??


Thanks guys
 
Hello,
Ran into an interesting problem here.
For troubleshooting purposes I am trying to connect to an FTP
site using
the windows command line. Using a test computer (same system model
and network using the same routes) I can connect fine to any FTP
site and everything works. Using the problem computer I can
connect but cannot get a directory listing. I can change
directories but I cannot get a directory using dir or ls. I have
turned off the windows firewall and it still does not give me a
directory list. I have also tried to connect to an FTP site
internally and I get the same results so it cannot be a firewall
that is interfering. This has to be something on the Windows box
itself. I have looked for any other applications like firewalls or
anything else that might effect the FTP but cannot find anything.
Using the test system (that FTP works on) I have stepped through
the task manager on the problem system and stopped any tasks that
the working system doesn't have running. Still no joy. I have run
a sniffer and can see the directory command go out and can see a
response being returned. I also have another user with the same
problem. The actuall error is

ftp>dir
200 PORT command successful
425 cannot open data connection

If I do a cd command after this it works. Provided of course that
I know what the directory name is that I want to change to.

Thoughts??
Click to expand...

This sounds like a firewall problem.
Windows command line FTP understands only active-mode FTP.
All things that are working (commands) normally are port-21.
The things that don't work (data/directory transfers) are port-20
transfers.

Assuming you don't have any firewalls on your computer except Windows
Firewall, try going to the Windows Firewall control panel and make sure
that on the "exceptions" tab, there are exceptions enabled for ports 20
and 21 (Usually under the name "FTP").

HTH,
John
 
Sorry to interrupt, could you please explain me the difference between
http and ftp in plain language, i.e. their function and development?
 
Google , and look for Wiki headliner




Sorry to interrupt, could you please explain me the difference between
http and ftp in plain language, i.e. their function and development?
Click to expand...
 
John said:
This sounds like a firewall problem.
Windows command line FTP understands only active-mode FTP.
All things that are working (commands) normally are port-21.
The things that don't work (data/directory transfers) are port-20
transfers.

Assuming you don't have any firewalls on your computer except Windows
Firewall, try going to the Windows Firewall control panel and make sure
that on the "exceptions" tab, there are exceptions enabled for ports 20
and 21 (Usually under the name "FTP").
Click to expand...
Port 21 is outgoing (client to server). Port 20 is incoming (server to
client). Many firewalls (both 'proper' firewalls and 'local' firewalls
on a computer block incoming connections.

Cheers,

Cliff
 
Back
Top